• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 379 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.

[SC-MCSDK] u-boot hangs during startup

Wang Nan
Intellectual 635 points

Hi all,

    I'm working on TCI6614EVM, with MCSDK 2.0.0.8 to start up the A8 of 6614.

    At first the board has u-boot on it and it can start up successfully from NAND.
    But after my testing, some private configuration, u-boot can not start up now.

    CCS can success to connect to EVM, and load u-boot image into RAM.
    But after PC is set to the corresponding address in RAM, u-boot can NOT start up sucessfully.
    HyperTerminal has the following trace:

U-Boot 2011.06 (May 05 2012 - 14:56:19)
I2C:   ready
DRAM:  3 GiB

     And sometimes it is as below:

U-Boot 2011.06 (May 05 2012 - 14:56:19)
I2C:   ready
DRAM:  512 MiB

    Then u-boot is hang. There is no output in HyperTerminal, the input can not either.
    From the CCS, the PC register is stopped at 0x00020030. 

    Is there anybody can help me? Thanks in advance!

Best Regards,
Nan

  • 0
    TI__Mastermind 30825 points

    Nan,

    The TCI66x devices are supported through your local Texas Instruments Field Applications Engineer (FAE.)  TCI66xx devices are not supported on the E2E forums.  Please contact your local FAE for support.  If you do not know who your local FAE is, then please contact your local TI Technical Sales representative and they can point you to your local FAE for support.

    Best Regards,

    Chad

  • 0 in reply to Chad Courtney
    Intellectual 635 points

    Hi Chad,

    Thanks for your reply!

    Currently I think I found something about the issue.
    The version of our SC-MCSDK is 2.0.0.8P1.

    From the release note of it, I found that for u-boot-tci6614-evm.bin and u-boot_hdr_tlr.bin, it is needed that “Replace the original file at <release-install-path>/ti/sc_mcsdk_linux_2_00_00_08/images/ with this version”.

    For the past tests, I used the old version bin files to download.
    So the u-boot start up issue should be the known issue as “SDOCM00092727 DDR corruption found on Beta-2 boards” which is fixed in 2.0.0.8p1 in my guess.

    Anyway I've pass this issue

    Thank you all the same!