I'm attempting to download the network core image using the procedure described in "Programming the network sample from SES". My app prj.conf file includes the following statements:
# Bluetooth configuration # For nRF5340 CONFIG_BOARD_ENABLE_CPUNET=y CONFIG_BT_RPMSG_NRF53=y CONFIG_NRF_802154_SER_HOST=n
My assumption is that loading the "Bluetooth: HCI RPMsg" sample into the network core will provide the BLE "soft device" equivalent for the nRF5340 (network core side).
Step 8 of this sequence produces the following log in the target output window of SES:
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 ‘merged.hex’ to J-Link Programming 126.5 KB of addresses 00000000 — 0001fa4f J-Link: Flash download: Bank 1 @ 0x00000000: Skipped. Contents already match Download successful Connecting ‘J-Link’ using ‘USB’ Connecting to target using SWD Loaded E:/AdditionalWindowsTools/Nordic/nRF_Connect_SDK/v1.5.0/toolchain/segger_embedded_studio/bin/JLink_x64.dll Firmware Version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01 DLL Version: 6.94a Hardware Version: V1.00 Target Voltage: 3.300 Device "NRF5340_XXAA_NET" selected. ConfigTargetSettings() start ConfigTargetSettings() end InitTarget() start InitTarget() end Found SW-DP with ID 0x6BA02477 DPIDR: 0x6BA02477 AP map detection skipped. Manually configured AP map found. AP[0]: AHB-AP (IDR: Not set) AP[1]: AHB-AP (IDR: Not set) AP[2]: MEM-AP (IDR: Not set) AP[3]: MEM-AP (IDR: Not set) AP[1]: Core found AP[1]: AHB-AP ROM base: 0xE00FE000 CPUID register: 0x410FD214. Implementer code: 0x41 (ARM) Found Cortex-M33 r0p4, Little endian. FPUnit: 8 code (BP) slots and 0 literal slots Security extension: not implemented CoreSight components: ROMTbl[0] @ E00FE000 ROMTbl[0][0]: E00FF000, CID: B105100D, PID: 000BB4C9 ROM Table ROMTbl[1] @ E00FF000 ROMTbl[1][0]: E000E000, CID: B105900D, PID: 000BBD21 Cortex-M33 ROMTbl[1][1]: E0001000, CID: B105900D, PID: 000BBD21 DWT ROMTbl[1][2]: E0002000, CID: B105900D, PID: 000BBD21 FPB ROMTbl[1][6]: E0042000, CID: B105900D, PID: 000BBD21 CSS600-CTI Loading target script file nRF_Target.js Preparing target for download Executing Reset script Reset(); ResetTarget() start ResetTarget() end Downloading ‘merged_CPUNET.hex’ to J-Link Programming 189.1 KB of addresses 01000000 — 0102f47b T-bit of XPSR is 0 but should be 1. Changed to 1. Timeout while preparing target, RAMCode did not respond in time. (PC = 0x00000000, CPSR = 0x00000000, LR = 0x41000003)! Failed to prepare RAMCode using RAM Download failed Failed to download application. Generic error. Please check J-Link and target connection. Illegal value 0x21009658 written to register 67 (PSP_NS) ignored
This appears to indicate that the download failed. (Note that the J-Link interface works to download the app core image, so J-Link must be OK. And earlier, I downloaded the .hex files for the HRM example (using the nRF Connect Programmer) to test the nRF5340-DK board. )
If I then make the "app" the active project and use Debug->Go to download the app image and start execution, the app appears to hang when the statement:
err = bt_enable(NULL);
is executed. The screen capture shows:
Am I doing something wrong?
Thanks...
