I'm debugging custom hardware that has a ST32GM431C8 MCU and am connected using a J-Link. My connection to the hardware is the 5-wire JTAG. When running using Keil MDK5 I have a problem in which the Keil debug windows work fine until I execute a specific version of code then the windows get trashed and I cannot debug. I was hoping to try the GDB debugger with J-Link (I'm new to GDB). When I launch either the command line program or the GUI version I get "GDB waiting for connection..."
I was hoping that I could use the GDB command line version with J-Link to debug to see if my problem was related to the Keil environment or if I have another problem. Here is what get's displayed by GDB:
Display All
Thanks --
I was hoping that I could use the GDB command line version with J-Link to debug to see if my problem was related to the Keil environment or if I have another problem. Here is what get's displayed by GDB:
Source Code
- Verify download: off
- Init regs on start: off
- Silent mode: off
- Single run mode: off
- Target connection timeout: 0 ms
- ------J-Link related settings------
- J-Link Host interface: USB
- J-Link script: none
- J-Link settings file: none
- ------Target related settings------
- Target device: Unspecified
- Target interface: JTAG
- Target interface speed: 4000kHz
- Target endian: little
- Connecting to J-Link...
- J-Link is connected.
- Firmware: J-Link EDU Mini V1 compiled Feb 18 2021 11:25:23
- Hardware: V1.00
- S/N: 801020066
- Feature(s): FlashBP, GDB
- Checking target voltage...
- Target voltage: 3.30 V
- Listening on TCP/IP port 2331
- Connecting to target...
- J-Link found 2 JTAG devices, Total IRLen = 9
- JTAG ID: 0x4BA00477 (Cortex-M4)
- Connected to target
- Waiting for GDB connection...