• State Verified Answer
  • Locked Locked
  • Replies 17 replies
  • Subscribers 73 subscribers
  • Views 6384 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 122063
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

dfu bootloader eclipse managed project issue

gotthcha

I tryed to port the dfu secure bootloader sample of sdk 13 to eclipse managed project. after a few hours, i finished it. compiling and linking went fine but the filesize is a little bit bigger then the ordinary gnu make in the sample folder. if i flash the .hex, bootloader is starting. but after a ble flash with the app from an iphone, there is no response from the chip. no application is starting. no dfu bootloader anymore. if i use the .hex from the sample folder, all works fine. i attached the eclipse project for u guys to try it by yourself. maybe there is someone who can fix the issue and figure out what the problem is?

The sdk should be in folder "sdk" in folder before project.

Bootloader.zip

You can download folder with sdk here: www66.zippyshare.com/.../file.html

MBR Page of eclipse compiled bootloader. read after dfu update: eigen_mbrset.txt

Parents
  • 0

    After flashing all are fine. If i upgrade the Firmware With dfu then it is written after the Firmware is send With ble. the Whole System is broken when the Code (upper) is reached. After that the mbr page is no longer r clear. Then i cant start the bootloader anymore. If i clear mbr page i can get Into bootloader again. the problem might be the nrf_dfu_mbr_vector_table_set function, but why. the firmware is written just fine with dfu (log files).

Reply
  • 0

    After flashing all are fine. If i upgrade the Firmware With dfu then it is written after the Firmware is send With ble. the Whole System is broken when the Code (upper) is reached. After that the mbr page is no longer r clear. Then i cant start the bootloader anymore. If i clear mbr page i can get Into bootloader again. the problem might be the nrf_dfu_mbr_vector_table_set function, but why. the firmware is written just fine with dfu (log files).

Children
No Data
Related
Terms of service