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

F28069U - problem starting USB bootloader from application

Felix Deichmann
Prodigy 150 points
Other Parts Discussed in Thread: CONTROLSUITE

Hi,

we use the (modified by Trey German) USB bootloader for F28069U and also call it from our application using AppUpdaterUSB(). This has been working well so far, but we added a larger portion of code recently and problems started:

When we call the bootloader from the app now, the bootloader is entered/running as before (we indicate this by a LED), but the device gets reset within 500 ms or so. I could debug this a bit and found out that in the bootloader, HandleReset() in bl_usb.c is called, probably from a USB reset condition on the bus. Now I modified this function to not reset the device and the bootloader keeps running, but it is unusable/slow/... Sporadically it can be enumerated by "dfuprog -e", but only a single time and then the values printed out by dfuprog look really strange.

This is not a watchdog issue, as we disable the WD (verified) before we enter AppUpdaterUSB().

The code modifications we added in contrast to the working state before do not touch the bootloader or the application and its code for entering the bootloader at all, as far as I can tell. There are even no "new" interrupts or side-effects etc.

The only difference I can see right now is that we have "more code", i. e. more flash consumption... Can this be the source of the problem somehow?

What is the latest USB bootloader for F28069U, where can I find it, and does it also contain all the patches from Trey?

Help would be greatly appreciated, as we need a working bootloader for field upgrades also.

Felix

  • 0
    TI__Mastermind 32995 points
    Felix,

    What modifications did Trey make? Are you using the bootloader that is in controlSUITE or a modified version.?

    Is it possible that you are erasing and parts of the bootloader when you are attempting to upgrade the firmware?

    sal
  • 0 in reply to Sal Pezzino
    Prodigy 150 points
    Sal,

    please ask Trey for the details. :) The USB bootloader from controlSUITE (v136 for 2806x) is/was broken, and Trey had an "inofficial" working version for C2000, which we got from him "officially" via our distributor. There is also a thread about this here.

    No, as far as I understand the bootloader occupies one flash page (0x4000), and you cannot delete only parts of that page. Also this explicit page is not part of our application or linker command file, and the bootloader will not delete itself.

    Felix
  • 0 in reply to Felix Deichmann
    TI__Mastermind 32995 points
    Trey is no longer with C2000 Software. The latest bootloader and flash application is in controlSUITE and I am not sure if it has the patches you received from Trey.