BLE (NORDIC_UART) Not Adevertising in Android phone , when i change UART pins ?

[naresh]

Dear  support team,

i hope you are doing good.

i am using nrf51822 customized board, SDK 12.3.0 version keil 5.26 is development on windows environment. 

softdevice s130

nRF Tool box App i am using.

In the SDK 12.3.0  Ble_Peripheral example (BLE_APP_UART) UART default pins are  TX -9 / RX-11 when i changed  these pins to according my customized Board UART TX-21 RX-22 , Uart printf() is  not working.

"NORDIC_UART" not visible in Android phone , some times even BLE not advertising.  

CASE : 1 if i keep default UART pins, BLE is sensing i am able to connect through the android phone, but at this time : My UART  Printf is not working

what could be the issue ? please suggest me

[Susheel Nuguru]

 I am guessing that your execution never reaches a point where your device starts advertising.

It sounds like there has been an APP_ERROR_CHECK failure in your code when you change the pins to 21/22. What caused it depends on where it happened and the error code. You should be able to tell that when you start your code in debugger and let the NRF_BREAKPOINT_COND hit in app_error_weak.c

If the execution does not reach here, then you need to take a harder approach and step through your code.

[naresh]

Dear Susheel Nuguru,

App_error_check nothing it showing after changing pins.

i am using SDK 12.3.0 Source code in that uart pins are  RX 11 / TX -9, nrf51822 (BT600I) Processor UART pins  RX -22/ TX-21 so according to the my customized board i change the pins in the source code  UART RX- 22/ TX- 21, after changing NORDIC_UART ble device name is not advertising.   

so what could be the issue ? how can i solve this problem ?

Regards,

Naresh,

Have a nice day .

[Susheel Nuguru]

The execution has to be looping somewhere or maybe there is a chip is doing a soft reset (NVIC_SystemReset()). Make sure to see if the advertising start API has been called and to see if the code is not looping. It is not hard to do this once you start your program to run in the debugger.