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

TMDXIDK5718: Is there a way to initialize TMDXIDK5718?

TOSHIMITU UCHIYAMA
Prodigy 10 points
Part Number: TMDXIDK5718

Tool/software:

While checking the UBOOT command, it suddenly hung up and the TMDXIDK5718 stopped working.

Pressing the RESET SW did not restore it, and neither did unplugging and plugging in the 5V power.

U-BOOT will not start.

The INDSTRILAL LED/STATUS LED stays on.

The U-BOOT commands used were read/write to U33 (CAT24C256W) via i2c mw/i2c md, and md.

Is there a way to initialize TMDXIDK5718?

  • 0
    TI__Mastermind 31645 points

    Hello UCHIYAMA-san,

    Can you upload any logs of how far this device gets in the boot sequence?

    What registers did you write/read?

    If you accidentally wrote one of the addresses that holds the board name and or revision, then the SW might not work. If you accidentally changed this, then you will have to also alter the u-boot code that deals with board detection.

    -Josue

  • 0 in reply to Josue Zamitiz-Ayala
    Prodigy 10 points

    Hello Josue
    Thank you for your quick reply.

    >Can you upload any logs of how far this device gets in the boot sequence?

    It seems that u-boot is not starting at all.

    Even if I press the Power on/Reset switch on the evaluation board, nothing is displayed in the terminal software (TeraTerm).

    >What registers did you write/read?

    1. I executed the following command.
    i2c mw 0x50 0x80.2 0x55 0x1
    i2c mw 0x50 0x81.2 0x43 0x1
    i2c mw 0x50 0x82.2 0x48 0x1
    i2c mw 0x50 0x83.2 0x49 0x1
    i2c mw 0x50 0x84.2 0x59 0x1
    i2c mw 0x50 0x85.2 0x41 0x1
    i2c mw 0x50 0x86.2 0x4D 0x1
    i2c mw 0x50 0x87.2 0x41 0x1
    (I wrote my name at 0x80)

    (Maybe I wrote something at another address by mistake...)
    (All data before writing was "ff")

    2. I confirmed that it was written correctly with the following command
    i2c md 0x50 0x80.2

    3. I typed the following md command to display the memory
    md 48070000

    4. I pressed the return key repeatedly to read the memory (I think I pressed it about 20 times)

    5. It hung up and no longer accepted any key input.

    6. It did not recover even when I pressed the Power on button, Hard reset button, or Warm reset button

    7. I turned the power off and on but it did not recover (it is in the state shown in the photo. The gpio LED was constantly lit)

    8. I replaced the boot SD card but it did not improve

    Thank you for your cooperation.

  • 0 in reply to TOSHIMITU UCHIYAMA
    TI__Mastermind 31645 points

    Uchiyama-san,

    Are you able to connect to JTAG and look at the program counter?

    Thank you for sharing your procedure. I have yet to confirm whether the way you wrote to the EEPROM was correct. Ill have to take a note to check.

    -Josue

  • 0 in reply to Josue Zamitiz-Ayala
    Prodigy 10 points

    Dear Josue

    Thank You for your kindly advise.
    I afraid i don't have JTAG evaluation.
    I'm asking to software team how I can boot without EEPROM.

    I appreciate your continued support.

  • 0 in reply to TOSHIMITU UCHIYAMA
    Prodigy 10 points

    Dear Josue

    I will report a good information.
    Our software team made a new u-boot that ignore EEPROM.
    New u-boot runs correctly and I can use u-boot commands now.

    This issue was solved.

    I appreciate your kind assistance.
    Thank you very much.

  • +1 in reply to TOSHIMITU UCHIYAMA
    TI__Mastermind 31645 points

    Uchiyama-san,

    I am glad your team was able to resolve this. For anyone else, this is a good case of being extremely cautious when writing to EEPROM, If you inadvertently write to the memory with board info, you might accidentally corrupt the boot flow established by the out-of-box SW.

    Thank you for your posts.

    -Josue