RE: nRF52840 based MDBT50Q flashing error.

Abhimanyu K K — Wed, 06 Feb 2019 11:39:45 GMT

Sir,

Thank you for your reply. I solved the issue by the following steps.

1. Do as I documented above(the question).

2. In this window Option for Target > Debug > Settings(Near ST-Link Debugger) > Flash Download > Programming Algorithm click Add and select nRF52xxx SoftDevice Error and nRF52xxx_UICR if the target is Soft Device. If the target is Project file then select nRF52xxx and nRF52xxx_UICR.

3. Then change the size of RAM to 0x2000.

4. Build the project file.

5. Flash the soft device.

6. Flash the Project file.

RE: nRF52840 based MDBT50Q flashing error.

Edvin — Tue, 05 Feb 2019 14:39:41 GMT

Hello,

You should be using the pca10056 project files, as these are intended for the nRF52840. I know it is a bit confusing, but PCA10056 is the name of the development kit with the nRF52840, while PCA10040 is the name of the development kit with the nRF52832.

It seems like you have forgotten to flash the softdevice first before programming your application. The "Coretex M4" error is a typical error message to get when the softdevice is missing.

The softdevice is the .hex file found in:

SDK\components\softdevice\s140\hex\

Note that it is the s140 softdevice that is used on the nRF52840.

Now to flash it, I have never tried this using an ST link, but maybe you can try to open the same project in segger embedded studio.

Open:

SDK\examples\ble_peripheral\ble_app_uart\pca10056\ses\

And open the project file. Segger embedded studio (full version) is free to use for nRF5 development. Please see this guide on how to install, and activate the license.

Segger embedded studio will automatically upload the softdevice for you.

Alternatively, you can try Nordic Command Line Tools or nRFgo Studio, but I don't know whether any of them work with the ST link.

Your last option is to figure out how to upload .hex files with ST Firmware, and upload the .hex files that way.

Best regards,

Edvin