I would like to import the Mesh examples to Keil or VisualGDB (I have both licenses) instead running the examples using SES
Which mesh SDK are you currently running? v2.2.0? I would not recommend porting SES to Keil or Visual GDB. We unfortunately do not support either in the mesh sdk.
May I ask why you do not want to use SES? There is a free commercial license to use it with Nordic products (no memory limits like in the free version of Keil). I have used both SES & Keil & in my opinion, they are very similar to use. I prefer to use SES actually to Keil.
Hi Bjørn, we are using VisualGDB because it is a requirement where I work, I managed to port my code to VisualGDB and it is compiling, but I am getting on my RTT output:
> <warning> nrf_sdh_ble: RAM starts at 0x20002A98, can be adjusted to 0x00005668. 0> <warning> nrf_sdh_ble: RAM size can be adjusted to 0xa998. 0> <error> nrf_sdh_ble: sd_ble_enable() returned NRF_ERROR_NO_MEM.
no sure how can I solve it
The warnings seem pretty self-explanatory to me: you need to adjust your VisualGDB project settings - specifically, the RAM start & size - to match what those warnings tell you.
As you say that VisualGDB is mandated at you workplace there must, surely, be co-workers who can show you how to do that?
I adjusted the RAM start and size how is it recommend by the warning, but now my code does not start, co-workers are not familiar with nRFx
I found this information https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v14.2.0%2Flib_bootloader.html&cp=4_0_2_3_5_0_1&anchor=lib_bootloader_memory, but is there something similar for the RAM?
MeliodasD said:my code does not start
What do you mean by that?
What debugging have you done to see where it's getting stuck?