Running BLE example using Segger Embedded Studio

[Jan Lundskov]

@Michael Dietz

Hi Michael! I am not sure what happened to my last question regarding the BLE example using Segger Embedded Studio. It is no longer visible in the post comments.

I have now added the preprocessor definitions you mentioned. I am installing Keil on my Windows PC to check the definitions as well.

One other thing I noticed is that when I import the Blinky example into SES only one project is created in the Project Explorer, but when I import the ble_app_hrs_s132_pca10040 example two apparently identical folders are created...

Is that correct?

I have now tried to delete one of the folders and add/change everything as we have discussed and now I am able to compile and run the code.

When I open the nRF Toolbox App on the HRM screen the device is not visible though. I have downloaded and verified the s132 softdevice.

If I try to start a debug session I get a 'stopped by vector catch' error (0x7bc 4B01 ldr r3, 0x000007C4).

What can cause this issue?

[Jan Lundskov]

Just an observation. If I choose to rebuild the project then it fails to build even though it has just build successfully before. I found that it is because the "../../../../../../components/device" that I added to User Include Directories is now lost/gone and the Memory Map macros are also back to default. Could that be related to the issue? Also after successfully downloading the Softdevice the Firmware says 'Unknown (Id: 0x007b), but I guess that has nothing to do with it..

[Jan Lundskov]

Is it not possible to say what may be the cause when debugging is stopped by vector catch? Can the Softdevice version cause the issue. In the GCC makefile it is s132_nrf52_2.0.0-7.alpha_softdevice.hex where I am using s132_nrf52_2.0.0-8.alpha_softdevice.hex.

[Michael Dietz]

No, i dont think it is the softdevice. I'm really not sure right now, I'm experimenting with some stuff in SEGGER Embedded Studio and will look into this as well i have some ideas of what might be causing but will let you know

[Jan Lundskov]

Ok. I have tried three different s132 Softdevice versions, but I get the same error. It says 'Unknown function at 0x000009D4'. I don't know if this information is useful. Let me know when you have something that I can try. Thanks.

[Michael Dietz]

this is as far as i got.. maybe it will help but im guessing you will still have problems with the softdevice. check the blog post i added an edit at the bottom. the issue is setting the flash and ram for the softdevice to be present now. i didnt get to that today but if you really want to you can check out the nRF52832_xxAA_MemoryMap.xml and also the sections placement file in linker options. Otherwise I should have time to get this done tomorrow and ill edit the blog