• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 101 subscribers
  • Views 982 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

66AK2E05: uBoot hangs at DDR3 0-bytes

Tarang Jindal68
Intellectual 820 points
Part Number: 66AK2E05

Hello,

We are facing an issue that, for the first power up, uBoot stops at DDR3 0-bytes. 

Prints are - 

U-Boot 2017.01 (Oct 05 2017 - 19:52:37 +0530)

CPU: 66AK2Ex SR1.0
Model: Texas Instruments Keystone 2 Edison EVM
I2C:   ready
DRAM: 
Clear entire DDR3 memory to enable ECC
0 Bytes

After power cycle the board, the board boot properly with prints - 

CPU: 66AK2Ex SR1.0
Model: Texas Instruments Keystone 2 Edison EVM
I2C:   ready
DRAM: 
Clear entire DDR3 memory to enable ECC
2 GiB
NAND:  512 MiB

Net:   Could not get PHY for ethernet-mdio: addr 0

Warning: netcp@24000000 using MAC address from ROM
eth0: netcp@24000000Could not get PHY for ethernet-mdio: addr 1

Warning: netcp@slave-1 (eth1) using random MAC address - 66:b9:4b:02:27:25
, eth1: netcp@slave-1
Warning: netcp@slave-2 (eth2) using random MAC address - a6:8e:bf:19:e4:c1
, eth2: netcp@slave-2
Warning: netcp@slave-3 (eth3) using random MAC address - 82:3d:58:d6:ed:49
, eth3: netcp@slave-3
Warning: netcp@slave-4 (eth4) using random MAC address - 86:46:f4:04:c8:69
, eth4: netcp@slave-4
Warning: netcp@slave-5 (eth5) using random MAC address - 26:31:75:40:81:13
, eth5: netcp@slave-5
Warning: netcp@slave-6 (eth6) using random MAC address - 5a:fc:97:02:06:f2
, eth6: netcp@slave-6
Warning: netcp@slave-7 (eth7) using random MAC address - d6:1f:8b:42:ef:73
, eth7: netcp@slave-7
Hit any key to stop autoboot: 3

sometimes we need to power cycle the board multiple times, sometime for the first time itself board boot properly.

can any tell me that what are the possible reasons behind this behavior. 

Thanks and Regards

Tarang Jindal

 

 

  • 0
    TI__Guru**** 161600 points
    Which software are you using RTOS or Linux? Which version?

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    TI__Guru**** 161600 points
    Hi,

    I haven't heard back. I consider you've solved your problem. I am closing this thread for now.
    If you didn't resolve your problem, feel free post here.

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Intellectual 820 points
    Hello,

    Sorry for late reply, I was on leave.

    We are using "u-boot-2017.01+gitAUTOINC+9fd60700db-g9fd60700db" .

    ~/nib-ti/k2e-down/board-support/evm/u-boot-2017.01+gitAUTOINC+9fd60700db-g9fd60700db (processor-sdk-local)# git show
    commit 0e59a7639df250920e82f01407c028838f22ccca
    Author: Texas Instruments SDK Builder <>
    Date: Wed Jun 28 16:51:23 2017 -0400

    Create local branch

    The below commit is used for this local branch and is the one used by
    this sdk:
    9fd60700db4562ffac00317a9a44761b8c3255f1.

    diff --git a/TISDK-README b/TISDK-README
    new file mode 100644
    index 0000000..657ec19
    --- /dev/null
    +++ b/TISDK-README
    @@ -0,0 +1,5 @@
    +Create local branch
    +
    +The below commit is used for this local branch and is the one used by
    +this sdk:
    +9fd60700db4562ffac00317a9a44761b8c3255f1

    Thanks and Regards
    Tarang Jindal
  • 0 in reply to Tarang Jindal68
    TI__Guru**** 161600 points
    Ok, this is the latest u-boot.
    Can you share is this a custom board? If yes, please check review your hardware.

    If this is an EVM, try connecting it to CCS with Jtag & load the gel file to verify your hardware is alive.

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Intellectual 820 points

    Hello,

    This is our custom board with 66AK2E05 SoC. 

    I have tried loading gel file using CCS with JTAG. That is working fine, 

    Thanks and Regards

    Tarang Jindal

  • 0 in reply to Tarang Jindal68
    TI__Guru**** 161600 points
    Then, if the ddr tests in GEL file works, you should modify the DDR settings in u-boot. That is the bellow files:
    ~/ti-processor-sdk-linux-k2e-evm-04.01.00.06/board-support/u-boot-2017.01+gitAUTOINC+590c7d7fe1-g590c7d7fe1/board/ti/ks2_evm/board_k2e.c
    ~/ti-processor-sdk-linux-k2e-evm-04.01.00.06/board-support/u-boot-2017.01+gitAUTOINC+590c7d7fe1-g590c7d7fe1/board/ti/ks2_evm/ddr3_cfg.c
    ~//ti-processor-sdk-linux-k2e-evm-04.01.00.06/board-support/u-boot-2017.01+gitAUTOINC+590c7d7fe1-g590c7d7fe1/board/ti/ks2_evm/ddr3_k2e.c

    and the files in:
    ~/ti-processor-sdk-linux-k2e-evm-04.01.00.06/board-support/u-boot-2017.01+gitAUTOINC+590c7d7fe1-g590c7d7fe1/arch/arm/mach-keystone/

    Best Regards,
    Yordan