Problem with SAM-BA on at91sam9g20

Hi

i am using AT91SAM9G20 CU-B rev MCU and SAM-BA 2.9V.
I Open the SAM-BA , with SAM-ICE connected between Host PC and the board.
Burn the bootstrap and the u-boot image.
Now the board is up with the u-boot. If i want to reburn the images on the
nand , i could not open the SAM-BA, SAM-BA gives
"NO valid Processor ID found" error message.

Can some one know how to solve this problem.

Thanks Start a New Thread

On Sat, 22 Aug 2009 18:44:22 +0530
V...@Lntemsys.com wrote:
> Now the board is up with the u-boot. If i want to reburn the images
> on the nand , i could not open the SAM-BA, SAM-BA gives
> "NO valid Processor ID found" error message.

I don't know about specifics on the 9G20-EK, but it sounds like you've
got something running that the SAM-ICE can't interrupt.

There's probably a jumper that disables the NAND flash so that you boot
into the RomBOOT prompt, which will let the SAM-ICE connect. I don't
know what it is on that board, though.

Dan
Start a New Thread

This is the expected behaviour....
You need to use the u-boot command to load/flash the image. I will describe one example here.

1. Download/build the kernel image(Uimage)
2. Erase the nand flash using the command "nand erase clean"
3. download the kernel Uimage using the tftp client (running in U-boot)
tftp 0x20000000 uImage
this will down load the image to RAM address 0x20000000

4. Write this image to flash using
nand write 0x20000000 0x00200000 uImage_size_bytes
here we are writing the image at 0x00200000 of size uImage_size_bytes in bytes
5. Download/build the valid root file system image (Jffs2). Download the same to RAM using the tftp client commands
tftp 0x20000000 rootfs.arm_nofpu.jffs2
6.write this to flash using the command

nand write 0x20000000 0x00400000 rootfs_size_bytes
here we are writing the image at 0x00400000 of size uImage_size_bytes in bytes
7. Now you need to change environment variables such that, the boot command will read the image from 0x00200000 into the ram and will boot.

setenv bootcmd=nand read 0x22200000 0x00200000 size_uImage_bytes

savenv

the setenv command will set the boot command such that the image present int he flash (0x00200000) will be loaded into the 0x22200000 (RAM address).

now give the command

bootm 0x22200000

now board will boot from the Uimage at 0x22200000.

To set up the TFTP client you need to set the following environment variables

serverip and ipaddr. The TFTP server need to be setup in the same network. The server should be reachable(ping should work)from the board.

You also need to set the bootargs environament variable like
setenv bootargs memdM console=ttyS0,115200 root=/dev/mtdblock1 rw rootfstype=jffs2
saveenv

I hope the above steps will help you. You're always welcome if you have any doubts

Regards
Mahendra.K



--- On Sat, 22/8/09, V...@Lntemsys.com wrote:

From: V...@Lntemsys.com
Subject: [AT91SAM] Problem with SAM-BA on at91sam9g20
To: A...
Date: Saturday, 22 August, 2009, 6:44 PM


Hi

i am using AT91SAM9G20 CU-B rev MCU
and SAM-BA 2.9V.

I Open the SAM-BA , with SAM-ICE connected
between Host PC and the board. Burn the bootstrap and the u-boot image.

Now the board is up with the u-boot.
If i want to reburn the images on the nand , i could not open the SAM-BA,
SAM-BA gives

"NO valid Processor ID found"
error message.

Can some one know how to solve this
problem.

Thanks
See the Web's breaking stories, chosen by people like you. Check out Yahoo! Buzz. http://in.buzz.yahoo.com/ Start a New Thread

On Sun, 2009-08-23 at 18:04 -0700, Dan Lyke wrote:
> On Sat, 22 Aug 2009 18:44:22 +0530
> V...@Lntemsys.com wrote:
> > Now the board is up with the u-boot. If i want to reburn the images
> > on the nand , i could not open the SAM-BA, SAM-BA gives
> > "NO valid Processor ID found" error message.
>
> I don't know about specifics on the 9G20-EK, but it sounds like you've
> got something running that the SAM-ICE can't interrupt.
>
> There's probably a jumper that disables the NAND flash so that you boot
> into the RomBOOT prompt, which will let the SAM-ICE connect. I don't
> know what it is on that board, though.
>
> Dan
> Start a New Thread