This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

DFU in custom board without Segger

Good afternoon, I have developed a custom board based on nRF51822 device and SD-110-v8. For debugging I have been usign the Ulink2 tool with Keil. Now, I want to implement DFU on my custom device but I have problems to program the DFU Bootloader into my device with my debuggin tool. So, is there any way of programming the DFU without a Segger tool (to access UICR) and continue using my ULINK2? If not, which Segger debugger do you recommend the most? The solution should also think in the future production stage.

Parents
  • How about this alternative here. multi-boards can be used for parallel programming on OS X & Windows. Can Flash all 3 (SD, App, DFU) all at once without mergehex. Support drag & drop with support for mBed compiled hex. Lot's features.

  • I purchased the tool you have suggested and, once received, I have proceeded as follows:

    • First, I have taken the example '...\examples\dfu\bootloader\pca10028\dual_bank_ble_s110\arm4' from the SDK, and I have compiled it with the following memory mapping: - IROM1: 0x3C000, 0x3C00 - IRAM1: 0x20002C00, 0x5380 - IRAM2: 0x20007F80, 0x80 (noinit)
    • I have also compiled my application with this other memory mapping: - IROM1: 0x18000, 0x24000 - IRAM1: 0x20002000, 0x6000
    • Then, and by means of the IDAP_link and IDAPnRFProg I have successfully programmed my device.
    • My device works fine and I also succeeded in changing my application by using the DFU utility. But... (continues)
Reply
  • I purchased the tool you have suggested and, once received, I have proceeded as follows:

    • First, I have taken the example '...\examples\dfu\bootloader\pca10028\dual_bank_ble_s110\arm4' from the SDK, and I have compiled it with the following memory mapping: - IROM1: 0x3C000, 0x3C00 - IRAM1: 0x20002C00, 0x5380 - IRAM2: 0x20007F80, 0x80 (noinit)
    • I have also compiled my application with this other memory mapping: - IROM1: 0x18000, 0x24000 - IRAM1: 0x20002000, 0x6000
    • Then, and by means of the IDAP_link and IDAPnRFProg I have successfully programmed my device.
    • My device works fine and I also succeeded in changing my application by using the DFU utility. But... (continues)
Children
No Data
Related