Problem flashing nrf52832 custom board on keil uvision CMSIS-DAP Debugger. can anyone help me?

RE: Problem flashing nrf52832 custom board on keil uvision CMSIS-DAP Debugger. can anyone help me?

Nguyen Hoan Hoang — Fri, 26 Jan 2018 19:16:46 GMT

You can use openOCD to flash softdevice

openocd -f interface/cmsis-dap.cfg -f target/nrf52.cfg -c "program s132.hex verify"

Click the link for more details using CMSIS-DAP with nRF5x. This blog for using Eclipse GCC with nRF5x and openOCD + CMSIS-DAP.

RE: Problem flashing nrf52832 custom board on keil uvision CMSIS-DAP Debugger. can anyone help me?

AmbystomaLabs — Fri, 26 Jan 2018 18:46:09 GMT

Anything that writes to flash on the chip can write the SD. However since you are using a non j-link programmer you can't use some of the Nordic tools like nRFgo. You will have to use whichever tools are provided by your programmer vendor.

Here is some Q&A on using the CMSIS-DAP with Keil: devzone.nordicsemi.com/.../

devzone.nordicsemi.com/.../

RE: Problem flashing nrf52832 custom board on keil uvision CMSIS-DAP Debugger. can anyone help me?

Felipe Duarte — Fri, 26 Jan 2018 18:34:44 GMT

I have a cmsic-dap debugger, can i download sd with this?

RE: Problem flashing nrf52832 custom board on keil uvision CMSIS-DAP Debugger. can anyone help me?

AmbystomaLabs — Fri, 26 Jan 2018 18:14:33 GMT

Here is a blog entry where I discussed the SD: devzone.nordicsemi.com/.../

Since BLE requires the SD be loaded to function, either the project needs to load it separately, or you need to load it via nRFgoStudio. The precompiled SD's are in the components/softdevice folder of the SDK. You just have to choose the correct SD to match up with the functions utilized in your app and the chipset it is going on. The project will never have sourcecode for the SD it is only an application that talks to the SD via API commands.

The SD and MBR always go at 0x0 which is the boot vector for the processor. If you don't have need of an SD (like a blinky app) then this goes at 0x0. The starting pointing for you app is in project settings. When using an SD you have to adhere to the settings in the SD docs. The SD has to know where you app is in order to launch it, since the MBR/SD launch first.

Occasionally, the projects may be scripted to cause the IDE to load the SD when required. This hasn't always been true, thus easier just to load the SD yourself.

You should really go through one of the basic tutorials. Such as: devzone.nordicsemi.com/.../

RE: Problem flashing nrf52832 custom board on keil uvision CMSIS-DAP Debugger. can anyone help me?

Felipe Duarte — Fri, 26 Jan 2018 17:37:11 GMT

Can you explain a little bit more?

RE: Problem flashing nrf52832 custom board on keil uvision CMSIS-DAP Debugger. can anyone help me?

AmbystomaLabs — Fri, 26 Jan 2018 17:33:51 GMT

The BLE examples do not include the Soft Device. The correct soft device for your sdk/application needs to be loaded separately. Just search in the blog for info on this or go over one of the beginners tutorials.

Likely the reason you still see the blinky app is since it is a non-ble app it will start at 0x0 whereas BLE applications start after the SD often at 0x1C000 or later. So keil just writes it into that portion of memory but blinky is still sitting at 0x0.