CENTRAL_LINK_COUNT and PERIPHERAL_LINK_COUNT settings

Hi,

See this blogpost.

regards

Jared 

I changed both CENTRAL_LINK_COUNT and PERIPHERAL_LINK_COUNT to 1. I didn't change any address at first and I got this output: 

0> SDH:warning:sd_ble_enable: RAM start should be adjusted to 0x20004638
0> SDH:warning:RAM size should be adjusted to 0xb9c8
...
0> APP_ERROR:ERROR:Fatal

I changed RAM START to 0x20004638 and RAM Size to 0xb9c8 and recompile. This time it seems to be running but the NRF_LOG_INFO no longer outputs messages. Please can you give any suggestion on how to correct the issue? I need the output messages for the development.

I am using an nRF52832 with SDK12.2.0.

I changed both CENTRAL_LINK_COUNT and PERIPHERAL_LINK_COUNT to 1. I didn't change any address at first and I got this output: 

0> SDH:warning:sd_ble_enable: RAM start should be adjusted to 0x20004638
0> SDH:warning:RAM size should be adjusted to 0xb9c8
...
0> APP_ERROR:ERROR:Fatal

I changed RAM START to 0x20004638 and RAM Size to 0xb9c8 and recompile. This time it seems to be running but the NRF_LOG_INFO no longer outputs messages. Please can you give any suggestion on how to correct the issue? I need the output messages for the development.

I am using an nRF52832 with SDK12.2.0.

Hi,

So after increasing the RAM size the application stopped outputting any logs. Have you checked if the application is asserting or not? Use a debugger and verify it. 

regards

Jared 

I looked into this issue further with vn2000.  I used gdb to confirm the application was behaving as expected even though the NRF_LOG_INFO messages weren't displayed in J-Link's RTT Viewer tool.  Then, I noticed the address of the RTT Control Block changed when RAM START was changed to 0x20004638 and RAM Size was changed to 0xb9c8.  We've have always used the "RTT Control Block" "Auto Detection" address range feature in J-Link's RTT Viewer tool.  However, it seems the "Auto Detection" logic was unable to find the "RTT Control Block" after the RAM settings were modified.  When the "RTT Control Block" "Search Range" was set to "0x20004638 0xb9c8", the "RTT Control Block" was detected and the expected NRF_LOG_INFO messages are now displayed again!

This resolved our issue. We can close this ticket. Thank you.