PCA10100 project not working for nRF52833 SoC

[Sridhar Jonnavittula]

Hi,

We have custom board based on nRF52833 SoC. We are trying to use SDK_v16.0.0/examples/ble_peripheral/ble_app_uart/pca10100/s140.

Using Segger Embedded studio, program is not downloading to flash but with nRF Connect it is downloading.

Is it the problem with SES?

[Karl Ylvisaker]

Hello,

How is the nRF52833 SoC connected to your computer - do you have it connected to a debugger?
SES will need a J-Link interface to program and debug your SoC.
The nRF Connect programmer can write a prebuilt .hex directly to your MCUbootloader.

Furthermore, be advised that the ble_app_uart PCA10100 project is made for the nRF52833 DK specifically, and it is not guaranteed to work right off the bat on a custom board - due to possible differences in the PCB's.

Best regards,
Karl

[Sridhar Jonnavittula]

Yes, our custom board has JLink pins out and connected via debugger.

So when debugger USB interface is connected to Windows PC which runs SES cant able to download prebuilt hex file ble_app_uart_pca10100_s140.hex using Download Intel Hex file option but nRF Connect for desktop Programmer application and nrfjprog can download in the same Windows PC.

Furthermore, be advised that the ble_app_uart PCA10100 project is made for the nRF52833 DK specifically, and it is not guaranteed to work right off the bat on a custom board - due to possible differences in the PCB's.

Why SES cant even program?

[Karl Ylvisaker]

Sridhar Jonnavittula said:

Yes, our custom board has JLink pins out and connected via debugger.

Alright, this is good to know, that changes things.

Sridhar Jonnavittula said:

So when debugger USB interface is connected to Windows PC which runs SES cant able to download prebuilt hex file ble_app_uart_pca10100_s140.hex using Download Intel Hex file option but nRF Connect for desktop Programmer application and nrfjprog can download in the same Windows PC.

Are you able to connect to the JLink from SES? Is there an error prompt when you try to use the "Target->Download" button? If so, which one?

Sridhar Jonnavittula said:

Furthermore, be advised that the ble_app_uart PCA10100 project is made for the nRF52833 DK specifically, and it is not guaranteed to work right off the bat on a custom board - due to possible differences in the PCB's.

I do not understand what you mean by this including this quotation from my previous reply, please elaborate.

Sridhar Jonnavittula said:

Why SES cant even program?

SES should be able to program your device just fine as long as it is connected to the JLink, which in turn is connected to your nRF52833 SoC.
Please specify what behavior you are seeing when you attempt to use SES to program your device.

Best regards,
Karl

[Sridhar Jonnavittula]

Target->Connect J-Link

Connecting 'J-Link' using 'USB'
  Connecting to target using SWD
    Loaded /usr/share/segger_embedded_studio_for_arm_4.22/bin/libjlinkarm.so
    Firmware Version: J-Link EDU Mini V1 compiled May 26 2020 15:04:19
    DLL Version: 6.50a
    Hardware Version: V1.00
    Target Voltage: 3.299
  Device "CORTEX-M4" selected.
  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

Target->Download File->Download

Connecting 'J-Link' using 'USB'
  Connecting to target using SWD
    Loaded /usr/share/segger_embedded_studio_for_arm_4.22/bin/libjlinkarm.so
    Firmware Version: J-Link EDU Mini V1 compiled May 26 2020 15:04:19
    DLL Version: 6.50a
    Hardware Version: V1.00
    Target Voltage: 3.299
  Device "CORTEX-M4" selected.
  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 's113_nrf52_7.0.1_softdevice.hex' to J-Link
  Programming 2.7 KB of addresses 00000000 -- 00000aff
  Programming 105.0 KB of addresses 00001000 -- 0001b3ff

It says Generic Error

Is there any particular SES version for this nRF52833 SoC? We use version 4.22.

[Karl Ylvisaker]

Hello,

This could be caused by a faulty connection, or a bad Segger install.
Could you ensure that the connection between the nRF52833 SoC and the J-Link is in good condition?
Please see this ticket for details around resolving a bad Segger install - in essence it seems that you will need to reinstall Segger and the related JLink drivers to resolve this issue.

Could you reinstall SES and J-Link driver, and let me know if this resolves your issue?

Best regards,
Karl

[Sridhar Jonnavittula]

Hello,

Yes after reinstalling it is working fine.

Thank you.