non-bluetooth applications.

[Julian]

I am trying to port an application from MBED LPC1768 to a nRF51822 Evaluation board to develop a multi-function application for the nRF51822. The BLE part (developed on the Eval board) is working, but I first want to develop and test the other sections as stand-alone applications (they use SPI to talk to other peripheral devices) before integrating them into the system. I have working code developed on MBED and ported it to KEIL, but I am not sure how to debug and test it on the Eval board. NRFGo Studio would only load the code after I had erased all memory (including the soft device). Master control Panel detected the emulator, but discovered nothing. Can you help?

[Nguyen Hoan Hoang]

Since you you already have your code in Keil. You need first to configure Keil to use Segger jtag in SW mode (not Jtag mode) for the project. After that you can run or debug or just flash the code.

You may want to have a look at this Blog site for multiplatform development. I use Eclipse only and have code that works both for nRF51, LPC, TI.

embeddedsoftdev.blogspot.ca/.../h.html

[Julian]

What you suggest is exactly how I debugged the BLE part of my project. My question was related more to the platform than the device; specifically the transfer from MBED and memory allocation. How do I avoid using memory space normally reserved for soft devices, although there will eventually be one, or do I need to avoid it?

[Nguyen Hoan Hoang]

You can remap your app with the linker script. Unfortunately, the M0 does not allow relocation of the interrupt vector like the M3. Your code can start anywhere but the vector needs to be at 0. So without the softdevice to forward the interrupts, you need to put your vector there.

[Asbjørn]

I would recommend you to have a look in the softdevice specification for the softdevice you are planning on using. Basically you just have to move your application up in flash and avoid using parts of RAM when you enable the softdevice. Assuming you are planning on using the S110, the S110 softdevice specification can be found here. If you are using a different softdevice, it will have its own specification.

To make this easier, I would recommend you to also program the softdevice into the chip even though you are not enabling it. That way the softdevice will be there in flash and it will forward the run time operation to you application as it will when you are in you final application as well. So just program it and develop code for the chip and once you are ready use the softdevice, you enable it. Also, remember that the softdevice will take control over certain resources and peripherals when you enable it. This is also stated and described in the above mentioned softdevice specification.