NRF51_DK firmware in release package invalid about daplink

[c1728p9]

@gamnes, can you confirm that the nrf51dk expects the application to be loaded at 0x8000?

[gamnes]

Depending on which bootloader you are running; the nrf51dk expects the application to be loaded at 0x8000 for the new DAPLink bootloader (MAINTANANCE), or if running with the old CMSIS-DAP bootloader (BOOTLOADER) it expects the application at 0x5000.

[c1728p9]

Hi @gamnes, are new boards being created with the DAPLink bootloader?

[gamnes]

New boards are created with the (old) CMSIS DAP bootloader, not the DAPLink bootloader. This is to keep compatibility with the other firmware that can be used on our boards.

[maclobdell]

okay, so this issue is because the board I had was upgraded to the daplink bootloader, but most people will have the cmsis-dap bootloader out of the box. Maybe it would still be good to have both binaries in the release package to cover both cases. @c1728p9 would you agree?

[c1728p9]

There isn't a user facing way to get or update the DAPLink bootloader. To avoid confusion the release package contains only interface firmware for existing bootloaders. I would prefer to keep it this way until new bootloaders are publicly released.