Running BLE example using Segger Embedded Studio

RE: Running BLE example using Segger Embedded Studio

Raphael — Sat, 27 Feb 2016 20:27:00 GMT

I had the same problem and the solution (at least for me) was setting the Section Placement Macros to: FLASH_START=0x1b000 RAM_START=0x20001f00 based on the linker file included in the armgcc directory. Note that I was using S130 with PCA10028 and SDK v11-alpha2. I did not change the flash_placement.xml. The start values for flash and RAM there should probably remain what they are and not be the same as the section placement macros, i.e. not factor in the SoftDevice.

RE: Running BLE example using Segger Embedded Studio

Michael Dietz — Tue, 02 Feb 2016 14:57:46 GMT

Hey Jan,

I edited the blog post. Ditch the device pack for now and try to follow it step by step. If you are still having problems then I'm going to recomend starting from a clean slate (an unmodified BLE example). Please PM me if you try blog and clean state and still doesnt work and lets set up a skype to get this fixed

RE: Running BLE example using Segger Embedded Studio

Michael Dietz — Tue, 02 Feb 2016 14:55:09 GMT

Mats:

Your SRAM_START should be 0x20001F00 and size should be 0x6500. But please see the blog post I updated it to use the softdevice. You will want to set the memroy map macros back to the full memory map size and start addresses and set aside room for softdevice in the flash placement file as i describe in the blog post. Do not use the nRF package for now.

RE: Running BLE example using Segger Embedded Studio

Mats — Tue, 02 Feb 2016 11:51:22 GMT

I've been working since yesterday with the nRF52 (PCA10040) on my Mac. I've followed this tutorial; devzone.nordicsemi.com/.../

The blinky-program is working but when I tried the ble_peripheral/ble_app_beacon/pca10040/s132/arm5_no_packs project file. But i'm also getting the same error as the TS:

Unknown function at 0x000009D4

First i had flashed the softDevice (s132_nrf52_2.0.0-7.alpha_softdevice.hex) with

jLinkExe -device nrf52

I've changed the Memory Map Macro's:

FLASH_START=0x1b000
FLASH_SIZE=0x65000
SRAM_START=0x20000000
SRAM_SIZE=0x8000

I've also tried this step:

In "Linker Options" you will need to set the "Section Placement File" as $(StudioDir)/targets/Cortex_M/flash_placement.xml.

But this causes an error;

cyclic memory section dependency with section .fast_run

I also tried using the emPackage but that doesn't really changed something...

I hope somebody can help me with my problem. (And maybe it's not related to the TS post?)

RE: Running BLE example using Segger Embedded Studio

Jan Lundskov — Tue, 02 Feb 2016 06:56:24 GMT

Hi Michael! I have downloaded and installed the nRF.emPackage, but I get two errors (Reset_Handler and RAM_segment_end ), so I guess that is what you are referring to. Let me know once you have had time to look at the softdevice falsh and ram settings. Thanks. Also when you talk to Segger and mention that two identical folders are imported, note that the first project folder has all the Includes, Preprocessor definitions etc, but the second one doesn't. So until it is fixed it is important to remember to delete the second folder and not the first one though they seem identical.

RE: Running BLE example using Segger Embedded Studio

Michael Dietz — Mon, 01 Feb 2016 15:10:19 GMT

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

RE: Running BLE example using Segger Embedded Studio

Jan Lundskov — Mon, 01 Feb 2016 14:24:21 GMT

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.

RE: Running BLE example using Segger Embedded Studio

Michael Dietz — Mon, 01 Feb 2016 14:18:12 GMT

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

RE: Running BLE example using Segger Embedded Studio

Jan Lundskov — Mon, 01 Feb 2016 13:58:06 GMT

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.

RE: Running BLE example using Segger Embedded Studio

Jan Lundskov — Mon, 01 Feb 2016 12:11:38 GMT

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..

RE: Running BLE example using Segger Embedded Studio

Jan Lundskov — Mon, 01 Feb 2016 11:49:32 GMT

I never get to main, but get the error right away. I have nRFGo Studio on my Windows laptop (I couldn't install it using playonmac for some reason), but I am running SES from my Mac, so I can't chose a softdevice hex file from the same directory as my SES project file. Is that what you mean?

RE: Running BLE example using Segger Embedded Studio

Michael Dietz — Mon, 01 Feb 2016 11:41:37 GMT

hm. So are you getting to main when debugging or are you getting this error right away? In project properties, linker options, additional output format specify 'hex'. Now from nrfgo studio erase, program softdevice, program this hex (this hex should be in the Output->Debug->Exe directory in the same folder as your SES project file. Now see if it works. If it works then you know your problem is related to flashing & runing/debuging the program if it doesnt work you know that the problem is in the compiling

RE: Running BLE example using Segger Embedded Studio

Jan Lundskov — Mon, 01 Feb 2016 10:59:56 GMT

I actually forgot to change target connection to J-Link this time. I have imported the project several times today. I have changed it and it seems to connect fine under Target->Connect J-Link (I see Cortex-M4 r0p1 on J-Link in buttom status bar) Anyway now I am back to the initial error 'Stopped by vector catch' on 0x9d4 4B01 ldr r3, 0x000009DC.

RE: Running BLE example using Segger Embedded Studio

Jan Lundskov — Mon, 01 Feb 2016 10:47:29 GMT

Hi Michael! Thanks. I have now erased all using nRFGo Studio and programmed Softdevice s132_nRF52_2.0.0-8.alpha successfully. When I run and debug I recieve 'Memory simulation error storing word to 0x200151f8', so I don't reach the first instruction of main.c. It stops on line 62 in system_nRf52.c just inside void SystemInit(void).

Just before the error I can see that download was successful, so that part should be ok.

RE: Running BLE example using Segger Embedded Studio

Michael Dietz — Mon, 01 Feb 2016 10:31:57 GMT

EDIT: Did you connect to your device? In SES go to your project properties and change 'Target Connection' from 'Simulator' to 'J-Link'. Make sure you can properly conenct to your device in the file menu select 'Target' and 'Connect J-Link' after editing this project to makes ure you can. Although enterring debug mode will connect automatically.

Not sure why its not visible but see my most recent answer to one of your questions that is: devzone.nordicsemi.com/.../

You shouldn't need to install keil. An easier way is to look at the GCC makefile to get these definitions (they will be the same as in keil, you just don't need to download it). In YOUR_PROJECT/PCA_100XX/s132/armgcc open the Makefile and look for: CFLAGS = -DNRF52 CFLAGS += -DSOFTDEVICE_PRESENT

You will see some defines denoted by -D'what_is_defined'. Just define these in your SES project (dont include -D). But note that SES gets these definitions from Keil by default so you shouldn't even have to do this. After you checked were the definitions different?

As for the two folders, I have seen this too.. I just deleted one of them. I'll contact SEGGER about this.

Sounds like you are close. 1.) Erase the entire chip. 2.) program softdevice. 3.) run and debug from SES.

Once in debug mode make sure your application atleast gets to the first instruction of main.c. Then single step over functions. After stepping a few times you will get to ble_stack_init(); When you try to step over this function if your debugger doesnt return hit pause and you will most likley be in a hardfault. This means that there is a problem with the softdevice and we can go from there. tell me what you find