Forum Replies Created
-
Posts
-
I already included the “test” button log for you. It’s called “JLinkGDBServerCL.exe -select IP=127.0.0.1:2331 -device ATSAMR34J18 -speed auto -if SWD -port 44565”.
If I run it manually but with the correct port, it shows the following.
If I remove “-select IP=127.0.0.1:2331” from the command argument, I get the following
And for reference, this is my J-Link GDB config
As a test, I tried running J-Link GDB directly and under VisualGDB using TCP/IP instead of USB, but I cannot change the port. It’s always something random! In this case, 44565.
J-Link GDB is listening on port 2331 and if I set the “Remote IP address” field to 127.0.0.1:2331 to force the port, it connects but then drops it instantly.C:\Program Files (x86)\SEGGER\JLink\JLinkGDBServerCL.exe -select IP=127.0.0.1:2331 -device ATSAMR34J18 -speed auto -if SWD -port 44565 SEGGER J-Link GDB Server V6.60 Command Line Version JLinkARM.dll V6.60 (DLL compiled Dec 16 2019 15:10:44) Command line: -select IP=127.0.0.1:2331 -device ATSAMR34J18 -speed auto -if SWD -port 44565 -----GDB Server start settings----- GDBInit file: none GDB Server Listening port: 44565 SWO raw output listening port: 2332 Terminal I/O port: 2333 Accept remote connection: localhost only ...
Do I need to use GDB? I have J-Link selected in VisualGDB and that should work as intended shouldn’t it??
Here is the log from J-Link commander if it helps. It shows that I can in fact connect to the MCU. Halting, resetting, etc all works fine.
SEGGER J-Link Commander V7.96l (Compiled Jun 12 2024 18:56:19) DLL version V7.96l, compiled Jun 12 2024 18:55:26 Connecting to J-Link via USB...O.K. Firmware: J-Link EDU Mini V1 compiled May 28 2024 15:38:10 Hardware version: V1.00 J-Link uptime (since boot): 6d 20h 47m 50s S/N: 123456789 License(s): FlashBP, GDB USB speed mode: Full speed (12 MBit/s) VTref=3.294V Type "connect" to establish a target connection, '?' for help J-Link>connect Please specify device / core. <Default>: ATSAMR34J18 Type '?' for selection dialog Device> Please specify target interface: J) JTAG (Default) S) SWD T) cJTAG TIF>S Specify target interface speed [kHz]. <Default>: 4000 kHz Speed> Device "ATSAMR34J18B" selected. Connecting to target via SWD InitTarget() start InitTarget() InitTarget() end - Took 2.95ms Found SW-DP with ID 0x0BC11477 DPIDR: 0x0BC11477 CoreSight SoC-400 or earlier Scanning AP map to find all available APs AP[1]: Stopped AP scan as end of AP map has been reached AP[0]: AHB-AP (IDR: 0x04770031) Iterating through AP map to find AHB-AP to use AP[0]: Core found AP[0]: AHB-AP ROM base: 0x41003000 CPUID register: 0x410CC601. Implementer code: 0x41 (ARM) Found Cortex-M0 r0p1, Little endian. FPUnit: 4 code (BP) slots and 0 literal slots CoreSight components: ROMTbl[0] @ 41003000 [0][0]: E00FF000 CID B105100D PID 000BB4C0 ROM Table ROMTbl[1] @ E00FF000 [1][0]: E000E000 CID B105E00D PID 000BB008 SCS [1][1]: E0001000 CID B105E00D PID 000BB00A DWT [1][2]: E0002000 CID B105E00D PID 000BB00B FPB [0][1]: 41006000 CID B105900D PID 001BB932 MTB-M0+ Memory zones: Zone: "Default" Description: Default access mode Cortex-M0 identified.
Okay, I found the issue. I need to press the reset button on the nRF52840 development board during programming. It seems VisualGDB doesn’t auto-reset the MCU during flashing. Is that something which is fixable in software?
I don’t think that is the cause of the problem however. The issue is a poor linker script since the code is being compiled fine. I am getting both
PL_smallEPD.cpp.dandPL_smallEPD.cpp.oin theOutputdirectory.
