Hi.

First post!

I have a J-Link Base, with V6.14a software installed on a Windows 8.1 Pro (64-bit) laptop. Its connected to the SWD port of the Invensense ICM-30630 Dev Board. Also have Eclipse Mars.2 Release 4.5.2. The debug session is started from within the Invensense 'Sensor Studio Desktop'. Initially the error is reported as "Error in services launch sequence:" " followed by "Starting J-Link GDBServer timed out". After a bit of searching,I found that the debugger options may not be properly populated by the Invensense stuff, i.e. I have to manually enter the device name, a non-zero timeout value, and the serial link of the J-Link probe, then the behaviour changes a bit: now I get:

Could not connect to target.
Please check power, connection and settings.SEGGER J-Link GDB Server V6.14a Command Line Version

JLinkARM.dll V6.14a (DLL compiled Feb 27 2017 18:41:26)

-----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: on
Silent mode: off
Single run mode: on
Target connection timeout: 1000 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: ATSAMD21G18
Target interface: SWD
Target interface speed: 1000kHz
Target endian: little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link V10 compiled Jan 9 2017 17:48:51
Hardware: V10.10
S/N: 50108046
Feature(s): GDB
Checking target voltage...
Target voltage: 3.30 V
Listening on TCP/IP port 2331
Connecting to target...ERROR: SAMD (connect): Could not access AHB-AP.

ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
Shutting down...


So, the probe is connected to the PC OK. If I try JLINK at the command line, everything looks OK, until:

Found SWD-DP with ID 0x0bb11477
Found SWD-DP with ID 0x0bb11477
Found SWD-DP with ID 0x0bb11477
Found SWD-DP with ID 0x0bb11477

******** Error: SAMD (connect) Could not access AHB-AP

Found SWD-DP with ID 0x0bb11477
Found SWD-DP with ID 0x0bb11477
Found SWD-DP with ID 0x0bb11477
Found SWD-DP with ID 0x0bb11477

******** Error: SAMD (connect) Could not access AHB-AP

Cannot connect to target.
J-Link>


I was expecting this stuff to work out-of-the-box....... What's wrong?

Any help appreciated!

Many thanks!

Hi Niklas.

Here are four of the documents. The most useful ones though, (software guide and hardwware guide), are over the size limit. Is there another means I can get them to you? AN_Eclipse_J-Link_debugging_ICM30630.pdfFireFly-Product-Brief.pdfICM-30630_ProductSpec_V1.0.pdfICM-30630-ProductBrief.pdf


Thanks for giving this your attention. Meanwhile, I'm going to check that I can debug something else with the probe, (I have a few arduino boards kicking around). Then at least we'll know the probe and the J-Link s/w are OK.


cheers for now,


Mark.

Me again.

If you could give me an external email address, I'll send them to you. To get them from their website, you'd need login, ... but its trivial to setup a developers account.

Actually, there's nothing in the docs that says it's an ATSAMD21G18 - I think that mistakenly came from the
Arduino Zero material. The Invensense docs only mention that it's a Cortex-M0.... (with a couple of motion co-processors). However, there is an app note specifically for debugging The Invensense Studio stuff with J-Link, and I've followed the instruction. (No device name, and no probe sedrial number). Leaving the device name as 'unspecified', and the serial number blank, on attemting to debug I get an Error box saying,

"Exception occured during Launch.
Reason:
Error in services launch sequence".

If I look in details, it says,

"Starting J-Link GDB Server timed out"

For what its worth, I tried the spare 20-pin-to-skinny-10-pin adapter and cable: no difference.


... I'm impressed you're going to get your own board to investigate this! I hope you can still get your hands on one - we got ours not long ago, but its recently become a 'legacy product'.

I've contacted Invensense support also - naturally I'll let you know if anything comes of that.

cheers for now,

Mark.

Hi Niklas.

Don't go buying a board.... I've answered my own question: if I put "Cortex-M0" in the device name field in the debugger tab of the debug configurations, AND fill in the probe's serial number, it springs into life!

... strictly speaking "Cortex-M0" is a CORE name, not a device name. Anyway, its working now.

Thanks anyway Niklas, and apologies if I wasted your time.

Mark