How to setup Keil Uvision for Redbearlab BLE Nano?

RE: How to setup Keil Uvision for Redbearlab BLE Nano?

daniel77 — Fri, 09 Dec 2016 11:12:22 GMT

In order to solve the bootloader issue, I just downloaded a PCA10028 nRF51422 example project .hex which includes softdevice S130 V2, app and bootloader by drag and drop the .hex into mbed USB drive. This will wipe off the Redbearlab S130 V1, bootloader and my app. I then pretty much maintain the same IROM and IRAM settings (for S130 V2) in the SDK PCA10028 nRF51422 examples for my nRF51822. At least for now, 2 SDK examples work on BLE Nano board. I would deep dive bootloader and settings for next time.

For other users, the advice is to save the IRAM & IROM settings of the SDK projects prior to changing the Device from nRF51422 to nRF51822 because Keil will set to default settings which cause the error in flashing.

RE: How to setup Keil Uvision for Redbearlab BLE Nano?

daniel77 — Fri, 09 Dec 2016 09:26:13 GMT

I was just porting the SDK projects to nRF51822 instead of nRF51422 PCA10028 board. It seems like I couldn't get the project running after flashing them. Is my bootloader having problem with these SDK projects? If so, should I compile a new bootloader? Is there any ready nRF51822 a bootloader that works with S130 V2.0/V1.0 for me to test?

RE: How to setup Keil Uvision for Redbearlab BLE Nano?

bjorn-spockeli — Thu, 08 Dec 2016 08:26:06 GMT

Hi Daniel, Keil does not merge the application hex with the SoftDevice and bootloader everytime you press download in your application project. You have to flash the SoftDevice and the Bootloader separately or merge all the hex files ( App, SD and BL) into one hex file and flash that. If you do not DFU in the application, then you have to set the BANK_APP_VALID flag in order to tell the bootloader that there is a valid application, see this answer.

RE: How to setup Keil Uvision for Redbearlab BLE Nano?

daniel77 — Thu, 08 Dec 2016 02:53:11 GMT

Thanks for highlighting the memory map issues. I reviewed the ROM and RAM management tutorial. I realized that Redbearlab uses S130 V1.0. Hence, I used IRAM base: 0x20002800 IRAM size : 0x5800 (32KB) IROM base: 0x1C000 IROM size : 0x24000 (256KB) Nevertheless, your answer is important for S130 V2.0. When I switch to V2.0, I will change to that IROM configuration. I think you should update the tutorial with your answer for V2.0. I am able to download the flash consistently now. But, the SDK example project doesn't run correctly. Does Keil uVision merge with softdevice and bootloader every time it downloads the program like mbed web IDE? My bootloader is not pointing correctly to the application now. It got stuck at OTA DFU bootloader mode loop cycle. It times out and reboots again.

RE: How to setup Keil Uvision for Redbearlab BLE Nano?

daniel77 — Thu, 08 Dec 2016 00:21:16 GMT

I am having same error after changing to this memory map. I tried IRAM1 Start:0x2000y000 (where y=4,6,8) but the error is still the same. Is there a way to report error in more precise way. I don't understand what is really causing "Erase Failed".

RE: How to setup Keil Uvision for Redbearlab BLE Nano?

bjorn-spockeli — Wed, 07 Dec 2016 14:15:01 GMT

Hi Daniel,

if the screenshots of the "Options for Target" window belongs to your firmware project, then you have to modify the IRAM/IROM settings under "Options for Target" --> "Target" to the following

IROM1 Start: 0x0001B000 Size: 0x25000 IRAM1 Start: 0x20002000 Size: 0x6000

the minimum RAM size required by the S130 v2.x SoftDevice is 0x13C8 bytes, see this page in the SDS, but its commen to provide 0x2000 bytes to give the SoftDevice some headroom. If 0x2000 bytes is not enough, then sd_ble_enable will return the correct RAM start address in the app_ram_base argument.

Best regards

Bjørn