app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Mon, 15 Feb 2021 23:18:06 GMT

Hi Amanda,

You may close this issue, I am using printf() to get the output on the serial console.

Regards

Chary BS

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Thu, 28 Jan 2021 14:16:49 GMT

Hi Amanda,

i think it is time to close this case :-)...

I have moved to a different project- on the 52810 and have put away this one.

Thanks for the support..

Cheers

Chary BS

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

Amanda Hsieh — Mon, 13 Jul 2020 08:20:09 GMT

Hi Chary,

Can you check what you have set NRF_SDH_CLOCK_LF_SRC to in sdk_config.h?

If there is no external 32kHz clock source it may be that you should use:

#define NRF_SDH_CLOCK_LF_SRC 0
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 2
#define NRF_SDH_CLOCK_LF_ACCURACY 1

-Amanda H.

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Sat, 11 Jul 2020 13:13:28 GMT

Hi Amanda,

I set the flag

NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0, as instructed but it did not have any impact on the output.

And now i have also changed the deferred log flag,

NRF_LOG_DEFERRED 1 to 0

Still no change.... :(

Looks like i am doing something wrong but unable to determine the reason for this problem ...

Regards

Chary BS

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

Amanda Hsieh — Fri, 10 Jul 2020 08:26:27 GMT

Hi Chary,

Are you using deferred logging ( #define NRF_LOG_DEFERRED 1 )?
In that case, you will need to call NRF_LOG_PROCESS() at a place in your code where you would like log processing to take place - please see the "Deferred logging" section of the logger module documentation for further information about this. Does change the setting NRF_LOG_DEFERRED = 0 help?

I want to check that did you try to set NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0 in sdk_config.h?

-Amanda H.

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Thu, 09 Jul 2020 13:03:12 GMT

Hi Amanda,

Sorry for the late response... 🙂

I did as you instructed - clean and rebuild the project, i made the changes as mentioned in the post you shared. I now see a small difference in behaviour - earlier, the Debug terminal seemed to have no activity. But now i see that when a log is printed, there's no text in the terminal window but the cursor moves down to the next line.

I am still unable to get this debug log thing to work 😞

Regards

Chary BS

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

Amanda Hsieh — Tue, 07 Jul 2020 13:22:21 GMT

Hi Chary,

Please check this post.

Did you clean, rebuild the project, and download the image again?

-Amanda H.

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Mon, 06 Jul 2020 13:29:42 GMT

Hi Amanda

I am just not able to figure out how to get the debug output on the RTT and use the UART normally...:(, can you help me out ?

I need this functionality to debug the code while using the UART to communicate with my peripheral .

Regards

Chary BS

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Fri, 03 Jul 2020 14:12:02 GMT

Hi Amanda,

I am able to receive data from the nRFConnect app onto the board and see it on the laptop's serial port connected to the Tx and Rx pins but the redirection to the RTT backend doesn't seem to be happening.

Also, the data that i am typing on the console is not being received by the app. Do i have to enable some settings for that?

Regards

Chary BS

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Fri, 03 Jul 2020 13:52:00 GMT

Hi Amanda,

Thank you for the pointers. I have increased the two parameters as mentioned in Sigurd's post and it solves the problem, i can now see the LED blinking in advertising state.

However, i am still not getting any DEBUG logs even after setting the flag you mentioned. It doesn't hinder my work in any way, but it would be good to have these logs since i plan to use the UART for communicating with an external peripheral. Kindly let me know if any other settings need to be made to see the logs - even the basic log - "UART Started" and "Debug logging for UART over RTT started", which i can see in main.c are not coming on the debug terminal.

Regards

Sreenivasa Chary

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

Amanda Hsieh — Fri, 03 Jul 2020 12:17:59 GMT

Hi Sreenivasa,

[quote user="SChary"]Therefore, when it returns with this error (code 0x04), the next line in app_button_init() [/quote]

Try Sigurd's suggestion in this post.

[quote user="SChary"]However, in my case i do not see any such log.[/quote]

You can try adding #define NRF_FPRINTF_FLAG_AUTOMATIC_CR_ON_LF_ENABLED 0 to your sdk_config.h

If you want to get the debug log, you should compile with debug mode.

-Amanda H.

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Fri, 03 Jul 2020 11:43:29 GMT

Hi Amanda,

I found the cause of the issue, in app_button.c, in function app_button_init(),

there is this call ,

err_code = nrf_drv_gpiote_in_init(p_btn->pin_no, &config, gpiote_event_handler);

which is in file nrfx_gpiote.c

There, in the pin/channel allocation logic, for Pin number = 13 (0x0d) the code hits line 557:

err_code = NRFX_ERROR_NO_MEM;

Therefore, when it returns with this error (code 0x04), the next line in app_button_init()

line 298 :

VERIFY_SUCCESS(err_code);

is failing. And the system is going to NRF_BREAKPOINT_CND in app_error_weak.c

I saw in another post, a similar report by some one else, but he was able to get the debug log where it suggested the solution - to modify the memory allocation. However, in my case i do not see any such log.

What should i modify to overcome this condition?

Regards

Chary BS

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Fri, 03 Jul 2020 10:16:48 GMT

Yes, I configured the RTT backend and NRF_LOGGING settings using the CMSIS configuration tool. I also tried power cycling the board. 🙂

i am trying to find out where exactly it is getting stuck -will share the details shortly...

Regards

Sreenivasa Chary

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

Amanda Hsieh — Fri, 03 Jul 2020 09:46:13 GMT

Hi Sreenivasa,

[quote user="SChary"]Yes Amanda, I did press the Play button to start the target running, but as i mentioned, there are no NRF_LOG() statements in the code prior to the hanging point.[/quote]

That's strange. The default setting of NRF_LOG_BACKEND_RTT_ENABLED is 1. Could you check the sdk_config.h as

//==========================================================
// <e> NRF_LOG_BACKEND_RTT_ENABLED - nrf_log_backend_rtt - Log RTT backend
//==========================================================
#ifndef NRF_LOG_BACKEND_RTT_ENABLED
#define NRF_LOG_BACKEND_RTT_ENABLED 1
#endif

Could you also try to reset the board by turning off and on the power switch?

-Amanda H.

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Fri, 03 Jul 2020 08:32:50 GMT

Yes Amanda, I did press the Play button to start the target running, but as i mentioned, there are no NRF_LOG() statements in the code prior to the hanging point. So the debug terminal was empty. I will try to program as you said , from the nrfConnect tool and check again, will revert to you asap......

REgards

Chary BS

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

Amanda Hsieh — Fri, 03 Jul 2020 08:10:39 GMT

Hi Sreenivasa,

After loading images, did you press again to run? What is the log you see in the Debug Terminal window? Did you see LED1 blinking (BSP_INDICATE_CONNECTED)? If not, Could you flash the image with nRF Connect Programmer or Command Line Tools with the following commands:

nrfjprog --family NRF52 --program s132_nrf52_7.0.1_softdevice.hex --chiperase --verify
C:\Users\amhs\Downloads\nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_uart\hex
nrfjprog --family NRF52 --program ble_app_uart_pca10040_s132.hex --sectorerase --verify
nrfjprog -r

Did you see LED1 blinking (BSP_INDICATE_CONNECTED)?

-Amanda H.

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Fri, 03 Jul 2020 07:52:16 GMT

I also erased the kit and reloaded the software - both the soft device and the app, but still the same issue is seen.

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

SChary — Fri, 03 Jul 2020 07:36:52 GMT

Hello Amanda

I use the Segger SES example and when I download the application, the output log shows me the following:

Connecting ‘J-Link’ using ‘USB’
Connecting to target using SWD
Loaded C:/Program Files/SEGGER/SEGGER Embedded Studio for ARM 4.30c/bin/JLink_x64.dll
Firmware Version: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 21 2020 17:30:48
DLL Version: 6.54c
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF52832_XXAA" selected.
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x2BA01477
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Preparing target for download
Executing Reset script TargetInterface.resetAndStop()
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘s132_nrf52_7.0.1_softdevice.hex’ to J-Link
Programming 2.7 KB of addresses 00000000 — 00000aff
Programming 146.1 KB of addresses 00001000 — 000258bf
J-Link: Flash download: Bank 0 @ 0x00000000: Skipped. Contents already match
Download successful
Downloading ‘ble_app_uart_pca10040_s132.elf’ to J-Link
Programming 62.1 KB of addresses 00026000 — 0003587f
Programming 0.1 KB of addresses 00035880 — 0003591f
J-Link: Flash download: Bank 0 @ 0x00000000: Skipped. Contents already match
Download successful

Regards

Sreenivasa Chary

[quote userid="77782" url="~/f/nordic-q-a/63335/app_ble_uart-example-not-initializing-ble-on-nrf52dk-pca10040-sdkv16-and-s132-soft-device/258234"]s132_nrf52_7.0.1_softdevice.hex[/quote]

RE: app_ble_uart example not initializing BLE on nRF52DK PCA10040 SDKv16 and S132 soft device

Amanda Hsieh — Fri, 03 Jul 2020 07:26:02 GMT

Hi Sreenivasa,

[quote user=""]When compile and download the program, i do not see it advertising as it is not visible in the scanned device list on the nRF Connect app on my iPad.[/quote]

Did you use the Segger ble_app_uart_pca10040_s132 project file? If not, did you flash the application image with s132_nrf52_7.0.1_softdevice.hex? Did you also Erase the kit board before loading the hex? If you use segger, you should be able to see the log in the Debug Terminal window of Segger. If you still have the issue, I would suggest you download SDK16 again.

-Amanda H.