Can't Start J-Link

Discussions concerning TrueSTUDIO for STM32 9.0.0 and later versions.

Moderators: Markus Girdland, Mattias Norlander

rbrajcich
Posts: 1
Joined: Tue Dec 04, 2018 8:50 pm

Can't Start J-Link

Postby rbrajcich » Wed Dec 05, 2018 5:08 am

Hi,

I am starting work on a project using Ambiq Micro's Apollo 2 Evaluation Board (Cortex-M4) with Atollic. I followed Ambiq's guide for getting started with their SDK, and it shows their board being used with Atollic's debugger without any issues. I have been unable to successfully start the debugger, however, and I cannot figure out why. I am able to see serial prints from the board using the external "J-Link SWO Viewer" program. My debug configuration in Atollic is shown below:

debugopts.PNG


Note that both the 1000 kHz SWO clock matches both Ambiq's documentation and the settings that work for "J-Link SWO Viewer".
The device also matches the documentation, the SWO Viewer setting, and the text printed on the physical board.

When I attempt to begin debugging, the console shows the following while trying to start up:

Code: Select all

SEGGER J-Link GDB Server V6.40 Command Line Version

JLinkARM.dll V6.40 (DLL compiled Oct 26 2018 15:06:02)

Command line: -port 2331 -s -CPU Cortex-M -device AMAPH1KK-KBR -endian little -speed 1000 -if swd -vd -swoport 2332
-----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      localhost only
Generate logfile:              off
Verify download:               on
Init regs on start:            off
Silent mode:                   off
Single run mode:               on
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:                 AMAPH1KK-KBR
Target interface:              SWD
Target interface speed:        1000kHz
Target endian:                 little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link OB-SAM3U128 V3 compiled Jul 12 2018 12:17:50
Hardware: V3.00
S/N: 483027918
Checking target voltage...
Target voltage: 3.30 V
Listening on TCP/IP port 2331
Connecting to target...Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x00001680 (Data = 0x49124811)
Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x00001680 (Data = 0x49124811)
Received monitor command: WriteDP 0x2 0x000000F0
O.K.
Received monitor command: ReadAP 0x2
O.K.:0xE00FF003
Reading 32 bytes @ address 0xE00FFFD0
Read 2 bytes @ address 0x000015AE (Data = 0x2000)
Read 2 bytes @ address 0x0000164A (Data = 0x4B0C)
GDB closed TCP/IP connection
GDB closed TCP/IP connection
Restoring target state and closing J-Link connection...


I then receive a popup error dialog that says "Launch Terminated. Failed to fetch device information"

I do not have much experience with J-Link, Atollic, or Ambiq's boards, but any ideas are welcome as I'm fresh out of things to try.

Thanks!
You do not have the required permissions to view the files attached to this post.

Return to “TrueSTUDIO for STM32 discussions”

Who is online

Users browsing this forum: No registered users and 1 guest