• State Verified Answer
  • Replies 10 replies
  • Subscribers 69 subscribers
  • Views 3922 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 248596
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

external nRF5340 getting locked up

Dushan_zvertech

Hi,

I have developed a piece of software that only uses the GPIOs on the APP core to evaluate a sensor. The software worked on the development board processor so I made a custom board with the nRF5340. After I would load the same software that worked on the dev board onto the external board the debugging would start and immediately jump to the following code in fault_s.S

#if defined(CONFIG_ARMV6_M_ARMV8_M_BASELINE) || \
defined(CONFIG_ARMV7_M_ARMV8_M_MAINLINE)
mrs r0, MSP
mrs r1, PSP
mov r2, lr /* EXC_RETURN */

push {r0, lr}

it would run to push {r0,lr} after which I would loose connection to the board and every attempt to talk to the board after what would result in error message 

Firmware Version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
DLL Version: 6.60f
Hardware Version: V1.00
Target Voltage: 3.300
Device "NRF5340_XXAA_APP" selected.
ConfigTargetSettings() start
ConfigTargetSettings() end
ConfigTargetSettings() start
ConfigTargetSettings() end
connect failed
Failed to connect to target.
No idcode detected.
Please check connection and Target Interface Type

I have tried running the --eraseall and --recovery with nrfjprog but that failed as well. Here is the dump form the log

-------------------------------------------------------------------------------

nrfjprog -f UNKNOWN --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.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1.
JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102.
FUNCTION: close_dll.
FUNCTION: close_dll.

I have a 32k XTAL on the target board if that makes any difference in this situation

Any input would be appreciated

Dusan

Parents
  • 0

    Hi,

    Thank you for your quick response.

    The board is supplied form a separate supply at 3.3V

    I am uploading the page of the schematic where the nRF is and you can also see which pins are used. I had to change the names but you can see the functionality.

    I find it very odd that it can be programmed only once, a new board is totally responsive over SWD. I can query it, read things out, erase it but as soon as I put the compiled software it stops responding and locks itself up. Is there a bare metal example without zephyr that I could try to test with? Are there special pins zephyr is expecting? Do I have to have the network core programmed as well?

Reply
  • 0

    Hi,

    Thank you for your quick response.

    The board is supplied form a separate supply at 3.3V

    I am uploading the page of the schematic where the nRF is and you can also see which pins are used. I had to change the names but you can see the functionality.

    I find it very odd that it can be programmed only once, a new board is totally responsive over SWD. I can query it, read things out, erase it but as soon as I put the compiled software it stops responding and locks itself up. Is there a bare metal example without zephyr that I could try to test with? Are there special pins zephyr is expecting? Do I have to have the network core programmed as well?

Children
No Data
Related