Flashing GESBC-9260S

Show HeXagon's last posts.

Super Hero
Posts: 7

Flashing GESBC-9260S

Dear Friends,

I have GESBC-9260S board and I tryed to reflash the U-boot and Linux image.
I am using the procedure described here: http://glomation.net/smf/index.php/topic,11.0.html.

After bat-file execution I receive the attached log.

It looks the SAM-BA cannot find the board. In the same time I can see the board in my PC's system try as connected USB device.

Please, advise.

Thanks in advance.

logfile.log (0.82 KB - downloaded 74 times.)

November 26, 2009, 10:19:06 AM

#1

HeXagon

HeXagon

Show general stats for HeXagon.

Hero
Posts: 4

Re: Flashing GESBC-9260S

I had this same problem. When you go to Amtel's website, download the v1.12 package for one of thier boards that includes the SAM-BA tools. It should be the 4th or 5th link down, use that.

November 27, 2009, 01:38:05 AM

#2

alzerr

alzerr

Super Hero
Posts: 7

Re: Flashing GESBC-9260S

Hi HeXagon,

Thanks for the answer. You are right about the incompatibility of SAM-BA tools 1.13. I change my instalation to 1.12 and there is a progress in the flashing process. Now the SAM-BA recognize the GESBC-9260S board and I tried to programm even Linux kernel and file system changing the root file system and kernel file names in accordance to tcl-file. The process pass successfulsy, but after reboot I received the follwing information on the HypperTerminal window. Find it attached.
It looks the image and/or file system are improper. I downloaded them from: http://www.glomationinc.com/support.html

Thanks in advance

HT-log.rtf (5.7 KB - downloaded 53 times.)

November 27, 2009, 03:07:51 AM

#3

alzerr

alzerr

Super Hero
Posts: 7

Re: Flashing GESBC-9260S

Hi everybody,

I flash the board with old image (2.6.25) and file system and everything is OK now. It means there is an incompatybility in new releases of cernal and may be file system.
For now we'll stay at old version of Linux cernel waiting for fix of the problem.

November 27, 2009, 07:39:33 AM

#4

admin

admin

Administrator
Super Hero
Posts: 342

Re: Flashing GESBC-9260S

The NAND FLASH name has changed from at91_nand to atmel_nand in 2.6.27 and up. So you need to change the U-boot environment variable bootargs when using kernel 2.6.27 and up.

December 07, 2009, 03:56:58 AM

#5

alzerr

alzerr

Super Hero
Posts: 7

Re: Flashing GESBC-9260S

Dear Friends,

Sorry for late reply. I did the procedure in accordance to the admin suggestion, but there still are some problems.
I receive two CRC error notices.
You can find them into the attached Hypper terminal screen log.

Waiting for new suggestions.

Thanks.

HT-log.rtf (6.67 KB - downloaded 58 times.)

December 08, 2009, 08:41:58 AM

#6

admin

admin

Show jstrother123's last posts.

Administrator
Super Hero
Posts: 342

Re: Flashing GESBC-9260S

Those error messages are JFFS2 warnings. It can happen if the board was not shut down properly but the JFFS2 file system should be able to self heal.

January 07, 2010, 05:48:54 PM

#7

jstrother123

jstrother123

Show general stats for jstrother123.

Hero
Posts: 4

Re: Flashing GESBC-9260S

How about those of us that are Linux only? I don't see a v1.12 except for windows. Is there a patch or work-around for v1.13 Linux? Thanks.

Jim

January 29, 2010, 09:43:42 AM

#8

Maturity

Maturity

Show Maturity's last posts.

Show general stats for Maturity.

Super Hero
Posts: 19

Re: Flashing GESBC-9260S

Hello,

I have been trying to get the 2.6.30 kernal running on a GESBC-9260 following the instructions in the 9260 manual. I can reliably get the system into a running state with SAM-BA and the files in the zip http://www.glomationinc.com/Support/9260/9260Files.zip. However any attempt to replace the 2.6.25 kernel with another, for example, 2.6.30, it results in this:

Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
List of all partitions:
1f00 256 mtdblock0 (driver?)15:15:41 EDT)
1f01 261888 mtdblock1 (driver?)
No filesystem could mount root, tried: jffs2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

With the 2.6.27.4 kernel I see

Kernel panic - not syncing: No init found. Try passing init= option to kernel.

If I specify the uImage of the 2.6.25 kernel it boots just fine (following the instructions in the GESBC-9260 manual)

I did read that there was a change in the uboot nand name from at91_nand to atmel_nand that could cause this so I made the change in the uboot parms of the .tcl file but this did not change the outcome.

Using the uboot instructions at the back of the 9260 manual to replace the kernel or the rootfs does not result in any improved joy.

Trying different combinations of the 25, 30 and 27.4 kernels and the 9260rootfs.img and rootfs-emdebian.img for the 9260 only results in a bootable system with the old 2.6.25 kernel and the emdebian rootfs. To get the full GPIO support apparently I need a 2.6.27 or later kernel.

Is there a zip that contains a complete set of files to restore the 2.6.30 kernel and emdebian fs with SAM-BA as that seems to be the most reliable way of restoring the system?

m

P.S. I have seen comments about looking at the u-boot manual but there are a few different versions when I look on the Web. Which one is the recommended version?

« Last Edit: January 29, 2010, 09:46:17 AM by Maturity »

January 29, 2010, 10:02:17 AM

#9

admin

admin

Show Maturity's last posts.

Administrator
Super Hero
Posts: 342

Re: Flashing GESBC-9260S

The MTD partition parameter must be changed if you upgrade from 2.6.25. The NAND FLASH name has been changed from at91_nand to atmel_nand. Please modify your U-boot environment variable bootargs.

January 29, 2010, 10:28:52 AM

#10

Maturity

Maturity

Show general stats for Maturity.

Super Hero
Posts: 19

Re: Flashing GESBC-9260S

I made the following changes (flagged with red) to the file AT91SAM9260_demo_linux_NandFlash.tcl

starting a line 90...

array set nf_mapping {
bootstrapFileName "nandflash_at91sam9260ek.bin"
kernelFileName "uImage-2.6.30"
diskFileName "rootfs-emdebian.img"
ubootEnvFileName "tmp.bin"

bootstrapOff 0x00000000
ubootOff 0x00020000
ubootEnvOff 0x00060000
kernelOff 0x00100000
diskOff 0x00400000

kernelSdram 0x22000000
diskSdram 0x21000000
}

starting at line 129 ...

lappend u_boot_variables \
"ethaddr=3a:1f:34:08:54:54" \
"bootdelay=3" \
"baudrate=115200" \
"stdin=serial" \
"stdout=serial" \
"stderr=serial" \
"bootargs=mem=64M console=ttyS0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2 mtdparts=atmel_nand:1M(bootloader),3M(kernel),-(rootfs)" \
"bootcmd=\
nand read $nf_mapping(kernelSdram) $nf_mapping(kernelOff) $kernelSize;\
nand read $nf_mapping(diskSdram) $nf_mapping(diskOff) $diskSize;\
bootm $nf_mapping(kernelSdram)"

My thought was that this should be sufficient to give me the 2.6.30 kernel with the emdebian filesystem. Is there something else that would need to be updated?

m

January 29, 2010, 10:36:17 AM

#11

admin

admin