• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 498 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.

UBL details

Ralf Gütlein
Prodigy 220 points

I wonder if there is some more detailled information for the UBL than shipped with the BLE stack package.

Several questions came up which can not be answered from the available documentation. 2 of them are these:

  1. There are 2 UBL hex files provided in the package, but I can't find any explanation of the differences, in particular, which of the hex files would be more suitable in my custom hardware. For no special reason I decided to use the ubl_cc2540-nano.hex, and is works kind of. However, I would like to know a bit better how to select the most suitable one.
  2. I adjusted the DELAY-JUMP field to 15000 in order to wait for 15 second in the bootloader before starting the application. This works well with a power-on reset. Howver,when I force a watchdog reset from my application the bootloader does not wait but jumps directly back to the application. The watchdog reset seems to be not working as a method to jump to the bootloader. Is that intended or am I doing something wrong?
  3. Is there another, preferred method to start the bootloader from the application? I cannot use the ublAppForceBoot() function as this method (deliberately) destroys the application.

Regards,

Ralf

  • 0
    Intellectual 265 points

    Ralf,

    If you look at ubl_main.c, specifically the __low_level_init() function, you will see that VERY early in the reboot process, the code tests to see if the reboot was caused by a watchdog timeout.  If so, it directly boots into the RC image application.  You would need to modify this to get back to the boot-loader in your situation.

    Doug

  • 0 in reply to Doug Bartlett
    Prodigy 220 points

    Thanks, Doug, for your explanation.

    My questions were rather old and referred to the UBL from the V1.2 stack (hex-files only). So the only chance to make changes to the bootloader was to patch those hex-files.

    Now, with the current stack, the sources are delivered, and I could make my way through them to find the right places to make the necessary changes.

    BTW: the documentation comming with the UBL is not current and does not reflect the changes in the memory usage. This should be corrected a.s.a.p.

    Thanks anyway!

    Ralf