• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 398 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.

Original question:

TMS320F28069: Issue with DFU mode on F28069U models - device reverts back into DFU mode from Normal mode in Runtime

TMS320F28069: DFU prog unable to program properly the chip while in DFU mode

John
Prodigy 240 points

Part Number: TMS320F28069
Other Parts Discussed in Thread: UNIFLASH

Hello all,

I've been asking some questions on the following thread, but somehow it got locked probably since it took me a while to come back, I still have my issue presented and today when I compared the memory of my DSP after using DFU prog to put the run time code I realized all the sectors are programmed at Zero, this means either the DFU prog is unable to put my code into the DSP or the boot loader somehow fails to store the values on the Flash once called, please advise how to solve the issue.

Previous thread: e2e.ti.com/.../4525894

Thanks

John

  • 0
    Prodigy 240 points

    Ok there's a new update:

    I've just changed a bit my linker command file assigning a bit different RAM, however now I can program the Hex code on the device using DFU prog where I can see that the memory read from the Flash through UniFlash has non-zero content, however on the last line there is a mismatch:

    Exported Hex from the Flash on the Right and The Hex file used for Dfuprog on the Left

    Why this is happening and what's the indication?

    Now I also see that DFU prog throws the following Error after downloading the code within the DSP:

    Error DFU_ERR_UNKNOWN (-4) reported during file download

    Please let me know your thoughts on this.

    Regards

  • 0 in reply to John
    Prodigy 240 points

    Ok, now I found where the problem is exactly happening, and it's within the CRC check inside the boot loader, once I comment on this segment my application code runs, so now it seems the CRC generated for my application code is some howe corrupted, how can I fix that issue?

    Thanks.

    John

  • 0 in reply to John
    TI__Mastermind 37195 points

    John,

    How are you calculating CRC for the application code? Can you share details for it?

    Best Regards

    Siddharth