• State Answer Suggested
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 923 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.

EK-TM4C123GXL: USB DFU device interface of ICDI USB port

Dashi Cao
Prodigy 110 points
Part Number: EK-TM4C123GXL


The uploaded contents from the ICDI USB port through USB DFU is 8+256000 bytes. With the 8 bytes at the head "01 00 06 00 00 e8 03 00". It is a DFU_CMD_PROG record, according to "Stellaris® Application Update Using the USB DFU Class". So this image is starting from block 6 and extends to the end (256KiB).

Using the lmtool on Windows, I got the image 256KiB.

But the contents disagree, as I compared the 256KiB image from 6k with the 8+256000 bytes image from 8.

It seems the contents I got using ICDI USB DFU interface is not correct! Why?

 

Dashi Cao

  • 0
    TI__Guru 72500 points
    Are you trying to upload the code from the ICDI device? This port is acting as a debug interface and not a USB DFU device. I think you want to use the device USB port (the one on the side).
  • 0 in reply to Bob Crosby
    Prodigy 110 points

    Hi Bob,

    There is the interface (3) of the ICDI that is a DFU device. This is the runtime DFU, which can be set into the DFU mode interface and then the contents can be uploaded.

    I think what I am doing may be just uploading the flash contents of the ICDI, which seems also being implemented by an TM4C.

    Thanks,

    Dashi Cao