ble_app_uart won't advertise as coded from example set

[Alexandre Tessier]

Hello, I am currently trying to program the uart example code from the nRF5_SDK_12.3.0_d7731ad zip file. After dealing with various reference address and device package issues, I am now able to flash the softdevice and progam sets to the chip. However, the chip is not advertising and it does work with the premade hex file. At this point I have no idea what could be wrong, the only noticible difference between the hex file layout in nRF Connect and the flashed softdevice and code from Kiel 5 is shown in the attached image, with hex file on the left covers the register address from 0 to 0x0001E3F7 while the flashed program from Keil goes from 0 to 0x0001E3FF. Other than that the recovery error is shown in the command window, but this occured even for the hex file which would advertise so I am unsure how to proceed.

[Alexandre Tessier]

An additional question that has come up is there is a program that was previously used by one of my colleagues. I have noticed that when I connect with my Iphone 13, it is very sparadic when the connection is done, often disconnecting. This does not seem to happen often with my other colleagues phones, is it possible the nrf51422 chip is not adaquate for the latest models? Also, if I have a signal that is from -2 to 2 V peak to peak, will this cause issues with the bluetooth connection and cause it to disconnect?

[Simonr]

Hi

Please check out our Adjustment of RAM and Flash memory guide here to understand how Flash and RAM (start and size) should be set up in a Keil or SEGGER project.

Seems like the project builds correctly, but what about the flashing process where you flash the project onto the board?

Regarding your final question. What pin(s) do this 2V signal go on, and is it located physically close to the antenna or antenna pin? If this is the case, then it might be affecting the radio performance. What advertising and connection parameters have you set for the nRF51?

Best regards,

Simon

[Alexandre Tessier]

Hello Simonr,

The flashing process is done exactly as described in the files, I clear the chip with nrfjprog --eraseall, rebuild the program, flash it to the target, switch to the softdevice, DO NOT rebuild the softdevice and flash it to the board as well.

For the signal, it is being sent into the PO.01 pin, so on the other side of the chip in relation to the antenna pin and other side of the PCB from the antenna.

Advertising and connection parameters were left as written in the example code given for ble_app_uart. I would have expected the code to be written in the same way the premade hex files were.

Sincerely,

Alexandre Tessier

[Simonr]

Hi Alexandre

I don't think the 2V signal should have anything to say here. If the application flashes successfully I think you need to debug what is going wrong when the application is running. I also see that you have tagged this ticket with "Bluetooth 5", which the nRF51 series does not support. So if you have added any features that aren't supported by the nRF51, that might be why you're having issues.

Best regards,

Simon

[Alexandre Tessier]

Hello Simonr,

I wasn't sure about the bluetooth level so that was what I selected. Any particular guide you would point to in assisting understanding the best way to debug the DK with Keil?

Sincerely,

Alexandre Tessier