[News]

News: Glomation introduces new GECM-9G25 SODIMM system on module

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

[ONLY]

The SAM-BA re-FLASHing should ONLY be used when the board is no longer booting.  Please check the user's manual on how to use U-boot to update kernel and file system.

The CRC JFFS2 error can happen if the system was not shutdown properly but can self heal.

[Maturity]

Maturity

Maturity

Show Maturity's last posts.

Show general stats for Maturity.

• 
• Super Hero
• Posts: 19

Thanks for the reply.  Is there a reason why the SAM-BA reflashing is bad?  I attempted to use the U-boot method as described but it did not seem to result in a viable outcome.

m

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

Both SAM-BA and U-boot methods are risky operation that can corrupt the NAND FLASH and put the board in a non-bootable state.  The U-boot approach is just slightly safer than the SAM-BA method.

[mauro]

mauro

mauro

Show mauro's last posts.

Show general stats for mauro.

• 
• Full Member
• Posts: 1

After receiving a new 9260 from Glomation, I tried powering it, but the board won't boot.
(The serial console only displays: RomBOOT >)

I then followed the procedure given on this forum, i.e. using sam-ba.
From a linux pc, after getting the 9260 properly recognized as /dev/ttyUSB0 (you have to load the usbserial module as described in sam-ba documentation: modprobe usbserial vendor=0x03eb product=0x6124), I launched sam-ba with the following:

../sam-ba_cdc_2.9.linux_cdc_linux/sam-ba /dev/ttyUSB0 AT91SAM9260-EK AT91SAM9260_demo_linux_NandFlash.tcl

But this is what I got:

-I- Waiting ...
-I- TCL platform : Linux
-I- SAM-BA CDC 2.9 rc6 on : linux
-I- Retrieved arguments from command line :
-I- argv 0 : /dev/ttyUSB0
-I- argv 1 : AT91SAM9260-EK
-I- argv 2 : AT91SAM9260_demo_linux_NandFlash.tcl
-I- Connection : /dev/ttyUSB0 (target(comType) = 1)
-I- Board : at91sam9260-ek
-I- Traces Level : 4
-I- target(handle) : file5
Read device Chip ID at 0xfffff240 --- get 0x019803a2
-I- Found processor : at91sam9260 (Chip ID : 0x019803a2)
-I- External RAM Settings :  extRamVdd=1, extRamType=0, extRamDataBusWidth=32, extDDRamModel=0
-I- Loading applet isp-extram-at91sam9260.bin at address 0x200000
-E- Error during external RAM initialization.
-E- External RAM access is required to run applets.

Does this mean the board is broken?

Thanks in advance.
Mauro.

[Lorena]

Lorena

Lorena

Show Lorena's last posts.

Show general stats for Lorena.

• 
• Super Hero
• Posts: 8

[ONLY]

The SAM-BA re-FLASHing should ONLY be used when the board is no longer booting.  Please check the user's manual on how to use U-boot to update kernel and file system.

The CRC JFFS2 error can happen if the system was not shutdown properly but can self heal.

Hello,

I am flashing GESBC-9260 and updating kernel and file system to a 2.6.30 version. I am following the steps given in GESBC-9260 User`s Manual in "Loading Linux Kernel and root File System".The kernel was right updated but I am not sure how to update the root File System. What are the values of the parameters [available_nand_flash_memory_size] and &(filesize) for this comands:
nand erase 0x400000 [available_nand_flash_memory_size]
t 0x21000000 rootfs.img
nand write.jffs2 0x21000000 0x400000 &(filesize)

Thank you in advance!

[Demon]

Demon

Demon

Show Demon's last posts.

Show general stats for Demon.

• 
• Hero
• Posts: 4

• 3)   Connect a USB cable from the USB device port of GESBC-9260(S) to desktop PC and place a jumper on S1 on the GESBC-9260(S) board.   Power up and power down the board to prepare NAND FLASH for SAM-BA download.  Remove the jumper on S1.
• 4)   Power up GESBC-9260(S) the “>ROM boot” message should be displayed on the serial console and a new USB device icon should appear in Windows status bar.  Execute the batch file in the downloaded factory image folder, a DOS command window should appear and a notepad window will appear in a few minutes with detailed log information.

Hi, I've tried the method described above but get the following errors logged after running the AT91SAM9260_linux_NandFlash batch file

-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.9  on : windows
-I- Retrieved arguments from command line :
-I- argv 0 : \usb\ARM0
-I- argv 1 : AT91SAM9260-EK
-I- argv 2 : AT91SAM9260_demo_linux_NandFlash.tcl
-E- Connection \usb\ARM0 not found
-E- Connection list : COM3

I think this is beacuase my laptop is not seeing the USB connection. I've tried a male-to-male cable with one of the USB host ports on the GESBC-9260. The instructions above say to use the USB device port, is this the one on the top side of the board at the SD card side? If so, where can I get a cable to fit this? If not, am I missing the plot?

The board won't boot, the serial console only displays: RomBOOT >

Thanks

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

On the GESBC-9260 the USB device port in on a 5 pin header.  On the GESBC-9260S the device port is the standard USB device port.  Please try close the jumper S1 and recycle the power a couple of times.  You should see the Windows detect the hardware icon on the status line if the NAND FLASH was successfully cleared.

[Demon]

Demon

Demon

Show Demon's last posts.

Show general stats for Demon.

• 
• Hero
• Posts: 4

On the GESBC-9260 the USB device port in on a 5 pin header.  On the GESBC-9260S the device port is the standard USB device port.  Please try close the jumper S1 and recycle the power a couple of times.  You should see the Windows detect the hardware icon on the status line if the NAND FLASH was successfully cleared.

Thanks I've made a suitable cable and have followed the recommended steps and all seems to work fine.

However SAM-BA keeps running as a process, using 50% of my laptop CPU, after outputting the log file. I left the process running for over half an hour but nothing changed.

Logfile.log:
-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.9  on : windows
-I- Retrieved arguments from command line :
-I- argv 0 : \usb\ARM0
-I- argv 1 : AT91SAM9260-EK
-I- argv 2 : AT91SAM9260_demo_linux_NandFlash.tcl
-I- Connection : \usb\ARM0 (target(comType) = 0)
-I- Board : at91sam9260-ek
-I- Traces Level : 4
-I- target(handle) : 19734544
Read device Chip ID at 0xfffff240 --- get 0x019803a2
-I- Found processor : at91sam9260 (Chip ID : 0x019803a2)
-I- External RAM Settings :  extRamVdd=1, extRamType=0, extRamDataBusWidth=32, extDDRamModel=0
-I- Loading applet isp-extram-at91sam9260.bin at address 0x200000
-I- Memory Size : 0x4000000 bytes
-I- Buffer address : 0x20049C
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- External RAM initialized
-I- Command line mode : Execute script file : AT91SAM9260_demo_linux_NandFlash.tcl
u-boot file: u-boot.bin
diskSize: 0x00900000
-I- === Performs sanity checks===
-I- === Initialize the NAND access ===
-I- NANDFLASH::Init (trace level : 4)
-I- Loading applet isp-nandflash-at91sam9260.bin at address 0x20000000
-I- Memory Size : 0x8000000 bytes
-I- Buffer address : 0x20003BE8
-I- Buffer size: 0x20000 bytes
-I- Applet initialization done
-I- === Erase all the NAND flash blocs and test the erasing ===
-I- GENERIC::EraseAll
-I- === Load the bootstrap: nandflash_at91sam9260ek in the first sector ===
-I- Send File ./nandflash_at91sam9260ek.bin at address 0x00000000
GENERIC::SendFile ./nandflash_at91sam9260ek.bin at address 0x0
-I- File size : 0x1060 byte(s)
-I-    Writing: 0x1060 bytes at 0x0 (buffer addr : 0x20003BE8)


Serial terminal:
>RomBOOT
>-I- -- NandFlash ISP applet 2.9 --
-I- -- AT91SAM9260-EK
-I- -- Compiled: Oct 29 2009 10:04:29 --
-I- INIT command
-I- Nandflash ID is 0x9500F1EC
-I-     Nandflash driver initialized
-I-      pageSize : 0x800 blockSize : 0x20000 blockNb : 0x400 bus width : 8
-I-      bufferAddr : 0x20003be8
-I-     End of applet (command : 0 --- status : 0)
-I- FULL ERASE command
-I-     Force erase flag: 0x0
-I- SkipBlockNandFlash_EraseBlock: Block is BAD
-I- Found block #49 BAD, skip it
-I- SkipBlockNandFlash_EraseBlock: Block is BAD
-I- Found block #372 BAD, skip it
-I- SkipBlockNandFlash_EraseBlock: Block is BAD
-I- Found block #427 BAD, skip it
-I- Full Erase achieved
-I-     End of applet (command : 1 --- status : 0)
-I- WRITE arguments : offset 0x0, buffer at 0x20003be8, of 0x1060 Bytes
-I- WRITE at block 0x0, page 0x0, offset in page 0x0
-I-     End of applet (command : 2 --- status : 0)


Has the process worked sucessfully? After safely removing the board from the laptop and recycling the power I still only get the non-responsive >RomBOOT displayed on startup.

Many thanks

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

If the board is GESBC-9260S then the boot strap code is wrong.  The GESBC-9260S uses only 16bit memory bus.  The Atmel EK board uses 32 bit.  Please download the files for the GESBC-9260S and use that for your board.

[Demon]

Demon

Demon

Show Demon's last posts.

Show general stats for Demon.

• 
• Hero
• Posts: 4

If the board is GESBC-9260S then the boot strap code is wrong.  The GESBC-9260S uses only 16bit memory bus.  The Atmel EK board uses 32 bit.  Please download the files for the GESBC-9260S and use that for your board.

I'm pretty certain the borad is not GESBC-9260S but the GESBC-9260. Could there be any other explanation? Thanks very much for your help.

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

The USB loading is finished as soon as the notepad pops up with the output log.  According to your log file it only wrote the bootstrap code,

-I- Send File ./nandflash_at91sam9260ek.bin at address 0x00000000
GENERIC::SendFile ./nandflash_at91sam9260ek.bin at address 0x0

Please check the TCL file to make sure it at least loads the U-boot.  The Atmel version should also load the kernel and file system.

[Demon]

Demon

Demon

Show Demon's last posts.

Show general stats for Demon.

• 
• Hero
• Posts: 4

The USB loading is finished as soon as the notepad pops up with the output log.  According to your log file it only wrote the bootstrap code,

-I- Send File ./nandflash_at91sam9260ek.bin at address 0x00000000
GENERIC::SendFile ./nandflash_at91sam9260ek.bin at address 0x0

Please check the TCL file to make sure it at least loads the U-boot.  The Atmel version should also load the kernel and file system.

Thanks I re-downloded the batch file and it worked fine. Thanks for all your help!

[sbc]

sbc

sbc

Show sbc's last posts.

Show general stats for sbc.

• 
• Full Member
• Posts: 1

I'm trying to flash GESBC-9260S. Got the following in log:

-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.9  on : windows
-I- Retrieved arguments from command line :
-I- argv 0 : \usb\ARM0
-I- argv 1 : GESBC-9260S
-I- argv 2 : GESBC-9260S.tcl
-E- Board gesbc-9260s not found
-E- Supported boards : at91sam7a3-ek at91sam9263-ek at91sam7s64-ek at91sam7sl32-stk at91sam7l64-ek at91sam7l128-ek no_board at91sam9m10-ek at91sam7xc256-ek at91sam7sl16-stk at91sam7s256-ek at91sam9260-ek at91sam7xc512-ek at91sam7s512-ek at91sam9xe256-ek at91sam7x256-ek at91sam3u4-ek at91sam7se32-ek at91sam7se256-ek at91cap9-dk-mem33 at91sam7xc128-ek at91sam7s128-ek at91cap9-stk at91sam9xe512-ek at91sam7x512-ek at91sam7se512-ek at91sam7s32-ek at91cap9-dk-mem18 at91sam7s321-ek at91sam9xe128-ek at91sam9rl64-ek at91sam9g45-ek at91sam9g10-ek at91sam9g20-ek at91sam9261-ek at91sam7x128-ek at91sam7sl64-stk

Just curious how it searches for boards? Where does that list come from?
I updated C:\Program Files\ATMEL Corporation\AT91-ISP v1.13\sam-ba 2.9
by files from SAM-BA-Files.zip

The board was registered as USB device in Windows XP.

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

The SAM-BA patch for the GESBC-9260S only works on SAM-BA 2.8.  Attached is the Atmel AT91-ISP 1.12.