• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 453 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Booting problem [AM3703]

santosh vastrad
Expert 2060 points

Other Parts Discussed in Thread: AM3703, FLASHTOOL

Hi all,

we got new boards, AM3703!

Need to test flashing!

Trying with flashtool for x-load.bin.ift, u-boot.bin, uImage, ubi.img!

Boot the problem is:

serial_init


U-Boot 2010.06-rc1 (Jan 23 2012 - 09:49:09)

OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C:   ready
size of cs_mcfg=  35880
size1 = 10000000
offset of cs_cfg =1
offset of cs_cfg 1 =8000000
size of cs_mcfg=  35880
size1 = 10000000
size of cs_mcfg=  0
size1 = 0
offset of cs_cfg =2
offset of cs_cfg 1 =10000000
DRAM:  256 MiB
NAND:  512 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Beagle Rev C4
Die ID #650c00029e380000016830c50201001e
Hit any key to stop autoboot:  0
OMAP3 beagleboard.org # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs rw rootwait nohz=off init=/sbin/init
OMAP3 beagleboard.org # setenv bootcmd "nand read 0x80000000 280000 400000 ; bootm 0x80000000"
OMAP3 beagleboard.org # saveenv
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x260000 -- 100% complete.
Writing to Nand... done
OMAP3 beagleboard.org # boot

NAND read: device 0 offset 0x280000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 80000000 ...
   Image Name:   Linux-2.6.32
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3572240 Bytes = 3.4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!

Can anyone help me?

Regards,

santosh vastrad

  • 0
    TI__Expert 6735 points

    Santosh:

    Copying from NAND to 0x8000 0000 may not be a good idea.  Try 0x8200 0000.

    Regards,

    Michael T

     

  • 0 in reply to Michael T
    Expert 2060 points

    Hi Micheal,

    The thing is that, I did before same thing to our old boards, it is booting fine,

    But got recently new boards, I got this problem,

    According to you, I even tried with your address suggestion by setting in boot arguments! but still the same problem.

    But when with same images i'm able to successfully boot from sd card!!!!!!!!

    x-loader.bin.ift = 0x0 offset = hwecc!

    u-boot.bin  = 0x80000 offset = swecc!

    uImage = 0x280000 offset = swecc!

    ubi.img = 0x680000 offset = swecc!

    Bootarguments before;

    setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs rw rootwait nohz=off init=/sbin/init

    setenv bootcmd "nand read 0x80000000 280000 400000 ; bootm 0x80000000"

    above argument i changed with 0x82000000!

    what else i need to check !!!!!!!!!!!

    Do you think any hardware stuffs!!!!!!!! or Nand issue!!!!!!!!!!!

    Regards,

    santosh vastrad

  • 0 in reply to santosh vastrad
    TI__Expert 6735 points

    Are you using an EZSDK?

    We have one for Beagleboard-xM:

    http://www.ti.com/tool/linuxezsdk-sitara

    Not sure how this applies to beagleboard Rev C

    With the 2.6.32 kernel you are using x-loader has to be built for

    a specific ECC format (for storing u-boot).

    http://processors.wiki.ti.com/index.php/Error_Correction_User_Guide 

    Can you use 1/4/8-bit HWECC?

    Regards,

    Michael T