[News]

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

[mmenti]

mmenti

mmenti

Show mmenti's last posts.

Show general stats for mmenti.

• 
• Super Hero
• Posts: 20

Hi

I've tried to flash my GESBC-9260 (64M RAM, 266M Flash) using files from

http://www.glomationinc.com/Support/9260/9260Files.zip

and sam-ba_cdc 2.10 (Win)

The board boots up - but as soon as I try to install new kernel, the board seems to hang (I guess due to changed flash-name). The same happens if I try to write changed uboot environment parameters (CRC error after reboot). Further, the board now shows 128M insted of 64M RAM...

Can you please provide us actual (current production) "9260Files" (uboot, kernel and parameters) for sam-ba flashing?

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

Please post the U-boot setting and commands you used to update the kernel.

[mmenti]

mmenti

mmenti

Show mmenti's last posts.

Show general stats for mmenti.

• 
• Super Hero
• Posts: 20

Please post the U-boot setting and commands you used to update the kernel.

It seems that the uboot settings aren't written correctly. After flashing using sam-ba_cdc 2.10 (Win) there will be the following error message:

Code:

U-Boot 1.3.3 (Dec 21 2008 - 10:06:28)

DRAM:  128 MB
NAND:  256 MiB
*** Warning - bad CRC or NAND, using default environment

After entering u-boot and issuing "saveenv", the board will boot up just fine. Here the list of environment variables:

Code:

U-Boot> printenv
bootargs=console=ttyS0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2 mtdparts=at91_nand:1M(bootloader),3M(kernel),-(rootfs)
bootcmd=nand read 0x22000000 0x100000 0x200000; bootm
bootdelay=1
baudrate=115200
ethaddr=00:0c:20:02:0a:5b
ipaddr=192.168.0.200
serverip=192.168.0.102
netmask=255.255.255.0
stdin=serial
stdout=serial
stderr=serial
ethact=macb0

Environment size: 353/131067 bytes
U-Boot> setenv bootargs mem=64M console=ttyS0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2 mtdparts=atmel_nand:1M(bootloader),3M(kernel),-(rootfs)
U-Boot> printenv
bootcmd=nand read 0x22000000 0x100000 0x200000; bootm
bootdelay=1
baudrate=115200
ethaddr=00:0c:20:02:0a:5b
ipaddr=192.168.0.200
serverip=192.168.0.102
netmask=255.255.255.0
stdin=serial
stdout=serial
stderr=serial
ethact=macb0
bootargs=mem=64M console=ttyS0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2 mtdparts=atmel_nand:1M(bootloader),3M(kernel),-(rootfs)

Environment size: 362/131067 bytes

But I'm still irritated by the u-boot Message saying that there will be 128MB RAM available. Linux shows the correct 64MB:

Code:

# free
              total         used         free       shared      buffers
  Mem:        62084         5648        56436            0            0
 Swap:            0            0            0
Total:        62084         5648        56436

[brady]

brady

brady

Show brady's last posts.

Show general stats for brady.

• 
• Super Hero
• Posts: 12

mmenti,

I think this topic may be of interest: http://glomation.net/smf/index.php/topic,149.0.html .  It seems there was a missing null terminator in the sam-ba script that causes the board to not see the u-boot environment variables.

-b.

[admin]

admin

admin

Show admin's last posts.

Show general stats for admin.

• 
• Administrator
• Super Hero
• Posts: 342

The memory size is defined as a constant and is compiled in for U-boot.  Therefore different U-boot version must be used when the boards are configured with different size of SDRAM.   It appears that you are using a version for the 128MB SDRAM.  Please change the U-boot to 64MB version if your board only has 64MB of SDRAM.  The link here is the 64MB version, http://www.glomationinc.com/Support/9260/u-boot.bin.

[mmenti]

mmenti

mmenti

Show mmenti's last posts.

Show general stats for mmenti.

• 
• Super Hero
• Posts: 20

[one]

Thanks brady and admin. The board now works as it should.

It seems that the uboot environment variable settings are still broken by using sam-ba, so I needed to edit these manually after flashing...

@admin: isn't it possible to provide one site with current updated and working uboot/rootfs/sam-ba/kernel files including target informations (memory size etc.)?
Because it's not very comfortable to read dozens of threads to find a possible working combination.