Issue connecting JLink with ISM43362

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
RaD_4001476
Level 1
Level 1
First like given

Hi,

I am facing below issue in connecting a JLink with ISM43362. I am trying to debug my application using Jlink.

I am using WICED SDK 6.4. Any help or pointers in resolving this will be helpful.

Below is the error:

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

JLinkARM.dll V6.62 (DLL compiled Jan 24 2020 16:32:09)

Command line: -if jtag -device CYW43362 -endian little -speed 1000 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0 -nogui

-----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:     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:                 CYW43362

Target interface:              JTAG

Target interface speed:        1000kHz

Target endian:                 little

Connecting to J-Link...

J-Link is connected.

Failed to set device (CYW43362). Unknown device selected?ERROR : Failed to set device.

GDBServer will be closed...

Shutting down...

Strict limitation error. Please check for correct device name and settings.

Thanks,

Raghu

0 Likes
1 Solution
GauravS_31
Moderator
Moderator
Moderator
10 questions asked 250 solutions authored 250 sign-ins

It appears that the VID, PID has not been set correctly. Please contact your module partner to get the JTAG settings reviewed.

View solution in original post

1 Reply
GauravS_31
Moderator
Moderator
Moderator
10 questions asked 250 solutions authored 250 sign-ins

It appears that the VID, PID has not been set correctly. Please contact your module partner to get the JTAG settings reviewed.