How can I check if the nrf52832 in my custom board is working?

[Ander GB]

Good morning!

First of all, the background. I made a custom board and programmed it, everything worked like a charm. After that, I made another one, same hardware, same software, same design, same components, same method, same everything, however this one is not being detected by nrfGO. It detects the nrf52DK, as if there was no custom board connected at all.

At first I thought: human error. I always use ESD protection when soldering. I checked all the components several times. My question, is there a way to know for sure that the MCU is not corrupted? Any pin that should output a square signal or something similar to that?

Thank you in advance!

AGB

[Andreas]

Hi,

 

Measure voltage on VDD and DEC4, if VDD is the correct level and DEC4 is ~1.27V the SoC has power as it should. There is no pin outputting a square signal, or similar. If VDD and DEC4 is as expected you might want to go over your setup once more, possibly try to use a different debugger/DK. Have you measured if there is connection between the SWD pins and the header you hook up to your debugger?

 

Best regards

Andreas

[Ander GB]

Hi Andreas, thank you for replying so fast. The voltage level at VDD is correct (3.3V from a VLO) but for some reason the voltage at DEC4 is also 3.3V, no ~1.27V as you suggested, does that mean that somehow I corrupted the SoC as I first guessed?

Regards,

AGB

[Andreas]

Hi,

 

3.3V on DEC4 is definitely not right if you measured this at C10 (not by accident DEC3 or anything)

Using nrfjprog, part of our command line tools, are you able to make a log and share with us? Install and run the command nrfjprog --recover --log (debugger connected to the custom board), and post the log here.

 

Best regards,

Andreas

[Ander GB]

Sorry for the delay. Here is the log:

--------------------------------------------------------------------------------
nrfjprog.exe --recover --log
nrfjprog verion 9.7.1
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_connected_emu_snr.
FUNCTION: read_device_family.
FUNCTION: read_device_family.
FUNCTION: close_dll.
FUNCTION: close_dll.
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF52832_XXAA" selected.
FUNCTION: recover.
FUNCTION: recover.
Found SW-DP with ID 0x2BA01477
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
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
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
FUNCTION: close_dll.
FUNCTION: close_dll.