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.

[Simonr]

Hi

Okay, do you perhaps only flash the application, and not the SoftDevice? As this is necessary to flash as well when building/flashing using Keil.

Best regards,

Simon

[Alexandre Tessier]

Hello Simonr,

No, as seen in the first image from nRFConnect, I would flash both the application and the SoftDevice. Attached is the Flash log of the SoftDevice. I had only sent the applications flash log as I would think the error was only occuring there. 

Fullscreen Flash Log.txt Download

Load "..\\..\\..\\..\\..\\..\\components\\softdevice\\s130\\hex\\s130_nrf51_2.0.1_softdevice.hex" 
Set JLink Project File to "C:\ncs\nRF5_SDK_12.3.0_d7731ad\examples\ble_peripheral\ble_app_uart\pca10028\s130\arm5_no_packs\JLinkSettings.ini"
* JLink Info: Device "NRF51422_XXAC" selected.
 
JLink info:
------------
DLL: V7.68 , compiled Jul 14 2022 16:47:42
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 20 2022 16:43:31
Hardware: V1.00
S/N : 681222439 
Feature(s) : RDI, FlashBP, FlashDL, JFlash, GDB 
 
* JLink Info: Found SW-DP with ID 0x0BB11477
* JLink Info: DPIDR: 0x0BB11477
* JLink Info: CoreSight SoC-400 or earlier
* JLink Info: Scanning AP map to find all available APs
* JLink Info: AP[1]: Stopped AP scan as end of AP map has been reached
* JLink Info: AP[0]: AHB-AP (IDR: 0x04770021)
* JLink Info: Iterating through AP map to find AHB-AP to use
* JLink Info: AP[0]: Core found
* JLink Info: AP[0]: AHB-AP ROM base: 0xF0000000
* JLink Info: CPUID register: 0x410CC200. Implementer code: 0x41 (ARM)
* JLink Info: Found Cortex-M0 r0p0, Little endian.
* JLink Info: FPUnit: 4 code (BP) slots and 0 literal slots
* JLink Info: CoreSight components:
* JLink Info: ROMTbl[0] @ F0000000
* JLink Info: [0][0]: E00FF000 CID B105100D PID 000BB471 ROM Table
* JLink Info: ROMTbl[1] @ E00FF000
* JLink Info: [1][0]: E000E000 CID B105E00D PID 000BB008 SCS
* JLink Info: [1][1]: E0001000 CID B105E00D PID 000BB00A DWT
* JLink Info: [1][2]: E0002000 CID B105E00D PID 000BB00B FPB
* JLink Info: [0][1]: F0002000 CID B105900D PID 000BB9A3 ???
ROMTableAddr = 0xF0000000
* JLink Info: Reset: Halt core after reset via DEMCR.VC_CORERESET.
* JLink Info: Reset: Reset device via AIRCR.SYSRESETREQ.
 
Target info:
------------
Device: nRF51422_xxAC
VTarget = 3.300V
State of Pins: 
TCK: 0, TDI: 1, TDO: 1, TMS: 1, TRES: 1, TRST: 1
Hardware-Breakpoints: 4
Software-Breakpoints: 8192
Watchpoints:          2
JTAG speed: 1000 kHz
 
Erase Done.
Programming Done.
Verify OK.
* JLink Info: Reset: Halt core after reset via DEMCR.VC_CORERESET.
* JLink Info: Reset: Reset device via AIRCR.SYSRESETREQ.
Application running ...
Flash Load finished at 23:56:23

SIncerely,

Alexandre Tessier

[Simonr]

Okay, and still the only change you made from the original example is to change the DEVICE_NAME, correct? What did you change it to exactly? If it is too long to fit in the advertising packet it might not show up as the name you thought.

Best regards,

Simon

[Alexandre Tessier]

Hello Simonr, I changed the name to EMG. So definetly should not have any effect.

[Simonr]

Hi

I'm inclined to think that there must be something else changed in your project, as it should be identical to the .hex file you're using. Can you try downloading a fresh instance of the SDK, as the ble_app_uart project works fine on my end in SD v12.3.0

Best regards,

Simon