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.

Linux/AM3352: Custom board is hanging during booting u-boot -2014.07 and kernel version 3.14-NOR flash and DDR

Part Number: AM3352

Tool/software: Linux

Hi,

My device is hanging at boot level after porting u-boot.bin to device.

I2C: ready
DRAM: 128 MiB

Hangs at this stage

My DDR2 is 128MB

NOR Flash 32MB

We are booting from NOR flash.

Following steps followed

1) Flashed recovery image using X-modem u-boot-spl.bin

2) Flashed recovery image using Y-modem u-boot_uartboot.img

u-boot#

3) setenv ipaddr <<IP>

4) setenv serverip <IP>

5) ftp 0x82000000 u-boot.bin

6) erase 0x8000000 0x807ffff

7) cp.b 0x82000000 0x8000000 0xXXXX

8) tftp 0x82000000 device.dtb

9) erase 0x80a0000 0x80fffff

10) cp.b 0x82000000 0x80a0000 0xXXXX

11) re

At this stage device is hanging at 

I2C: ready 
DRAM: 128 MiB

Please let me know how to debug

Regards

Subramanya

  • Hi,

    U-boot version 2014.07 and kernel version 3.14 are obsolete for several years now, and no longer supported by TI. Please move to the new Processor SDK: www.ti.com/.../PROCESSOR-SDK-AM335X
  • Hi,

    But previously i used same u-boot and kernel image for previous project. It was working fine.
    But for new project with little change in hardware it is not working and also getting errors with different cpu board as below. But daughter board is same for both.

    Ymodem sectors/kbytes sent: 602/75kRetry 0: NAK on sector
    Ymodem sectors/kbytes sent: 0/ 0k |
    Transfer complete

    How to solve this problem and above problem.

    Two cpu boards are same.

    Regards
    Subramanya N M
  • Subramanya N M,

    As Biser pointed out, this software is beyond our support window.

    As for how to debug, we can only provide some advice and that will be limited as we don't know your system. For example, I really can't tell what you mean by processor board and daughter board above.

    From what I can tell, it looks like something is not working reliably in the transfer to either DDR or the NOR. I would break down and validate each step to find where it is going wrong. If any hardware has changed, even slightly, I would look closely at that.

    I hope this helps.