Memory settings for working with rigDFU (Rigado BMD-300)

RE: Memory settings for working with rigDFU (Rigado BMD-300)

bjorn-spockeli — Fri, 28 Apr 2017 07:43:25 GMT

Great! Happy to help! I would appreciate if you could mark the answer as correct/accepted by clicking the checkmark in the grey circle to the left of the answer.

RE: Memory settings for working with rigDFU (Rigado BMD-300)

Sébastien Schiesser — Fri, 28 Apr 2017 07:40:05 GMT

Yes! Downloaded S132 v2, made a SoftDevice archive folder and linked my uVision project there. In additipn set the IROM to 0x1C000 and changed a preprocessor flag NRF_SD_BLE_API_VERSION to 2.

Now loading with DFU & working well. Thanks!

RE: Memory settings for working with rigDFU (Rigado BMD-300)

bjorn-spockeli — Fri, 28 Apr 2017 07:14:48 GMT

@sschiesser: This worked?

RE: Memory settings for working with rigDFU (Rigado BMD-300)

bjorn-spockeli — Thu, 27 Apr 2017 12:03:24 GMT

Q1: If you go to Options for Target-> C\C++ and then Iclude paths you'll see that you're including the SoftDevice headers from ..\..\..\..\..\..\components\softdevice\s132\headers and ..\..\..\..\..\..\components\softdevice\s132\headers\nrf52. Just point Keil to a folder where the header files for the SoftDevice version you want to use. You can download the SoftDevices and their header files from here.

Q2: You only have to adjust the size of the application IROM settings to BOOTLOADER_START_ADDRESS - APPLICATION START ADDRESS( in your case 0x1C000).

RE: Memory settings for working with rigDFU (Rigado BMD-300)

Sébastien Schiesser — Thu, 27 Apr 2017 11:50:40 GMT

makes sense... and opens two questions:

how can I change the SD version I'm compiling against in uVision?
if I do so, what are the memory settings I have to take care about to let some space for the bootloader?

RE: Memory settings for working with rigDFU (Rigado BMD-300)

bjorn-spockeli — Thu, 27 Apr 2017 09:32:15 GMT

You are compiling your new application against the SoftDevice headers that corresponds to the SoftDevice present on the Rigado Module? If the SoftDevice ends at 0x1C000, then it sounds like its a S132 v2.0.x SD, but it could sound like you've compiled your application against a S132 v3.x.x SD.

RE: Memory settings for working with rigDFU (Rigado BMD-300)

Sébastien Schiesser — Thu, 27 Apr 2017 09:22:50 GMT

As posted in the question:

bootloader starts at 0x75000
IROM: start 0x1C000, size 0x2B000 (previously default was: 0x1F000, 0x61000)
IRAM: start 0x20002128, size 0xDED8

RE: Memory settings for working with rigDFU (Rigado BMD-300)

bjorn-spockeli — Thu, 27 Apr 2017 09:13:04 GMT

Do you know the rigado bootloader start address? Please post the current IROM and IRAM settings in Keil of your application.

RE: Memory settings for working with rigDFU (Rigado BMD-300)

Sébastien Schiesser — Thu, 27 Apr 2017 06:18:20 GMT

yes it uses the version 2.0 (using 0x1C00)...

I first tried to change the start address in uVision, as well as the size to 0x2B000 (the rigDFU datasheet gives these values for the user application space) -> compiled & load well but didn't work.

I also tried to install the "correct" SoftDevice (2.3.0 I think) -> same thing.

Basically I miss a link for setting up the correct environment in order to develop with rigado DFU at factory settings...

RE: Memory settings for working with rigDFU (Rigado BMD-300)

RK — Wed, 26 Apr 2017 21:03:48 GMT

if you're developing against a softdevice which uses 0x1f000 and then changing that to one which uses 0x1c000 then you're using a different softdevice from that you're developing against. Surely the rigado eval board uses the same version as the module.