Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Thread

J-Link errors on initial installation

J-Link errors on initial installation

2005-12-13 by Steve Franks

Hi All,

Just plugged in a jlink for the first time.  Usb drivers look good in
devman, and green light on unit is on, but I can't talk to it; I thought
someone on the list might have seen the following errors before.

Thanks,
Steve

J-Link>usb 0
Connecting to J-Link via USB (Port: 0)
JTAG_GetFirmwareString: J-Link reports unsupported firmware string size of
26956
 (expected 112)
Could not identify firmware (Read failure)
J-Link>usb 1
Connecting to J-Link via USB (Port: 1)
Can not connect to J-Link via USB.
J-Link>usb 2
Connecting to J-Link via USB (Port: 2)
Can not connect to J-Link via USB.
J-Link>usb 3
Connecting to J-Link via USB (Port: 3)
Can not connect to J-Link via USB.
J-Link>usb 0
Connecting to J-Link via USB (Port: 0)
JTAG_GetFirmwareString: J-Link reports unsupported firmware string size of
27502
 (expected 112)
Could not identify firmware (Read failure)
J-Link>usb 0
Connecting to J-Link via USB (Port: 0)
JTAG_GetFirmwareString: J-Link reports unsupported firmware string size of
25376
 (expected 112)
J-Link>

RE: [lpc2000] J-Link errors on initial installation

2005-12-13 by Joel Winarske

Is green light solid or blinking?  If driver is not loaded it will just
blink.  The driver updates the J-Link firmware on the fly.  So you want to
be working with the latest J-Link driver from Segger's website.

Are you restarting jlink.exe each time you reinsert your J-link, or leaving
it open?

The other thing you might want to do is power cycle your machine with J-Link
plugged in.  Then see if devmgmt.msc (shortcut from start/run) is still
happy.


Joel
Show quoted textHide quoted text
> Hi All,
> 
> Just plugged in a jlink for the first time.  Usb drivers look good in
> devman, and green light on unit is on, but I can't talk to it; I thought
> someone on the list might have seen the following errors before.
> 
> Thanks,
> Steve
> 
> J-Link>usb 0
> Connecting to J-Link via USB (Port: 0)
> JTAG_GetFirmwareString: J-Link reports unsupported firmware string size of
> 26956
>  (expected 112)
> Could not identify firmware (Read failure)
> J-Link>usb 1
> Connecting to J-Link via USB (Port: 1)
> Can not connect to J-Link via USB.
> J-Link>usb 2
> Connecting to J-Link via USB (Port: 2)
> Can not connect to J-Link via USB.
> J-Link>usb 3
> Connecting to J-Link via USB (Port: 3)
> Can not connect to J-Link via USB.
> J-Link>usb 0
> Connecting to J-Link via USB (Port: 0)
> JTAG_GetFirmwareString: J-Link reports unsupported firmware string size of
> 27502
>  (expected 112)
> Could not identify firmware (Read failure)
> J-Link>usb 0
> Connecting to J-Link via USB (Port: 0)
> JTAG_GetFirmwareString: J-Link reports unsupported firmware string size of
> 25376
>  (expected 112)
> J-Link>

RE: RE: J-Link errors on initial installation

2005-12-14 by Steve Franks

Joel,

Did all that. Light is solid, rebooted machine, deleted & re-installed
latest driver from segger site, etc.  Figure the box is just fried?  It's
been in the dev-kit box unused for a year...but it was in a cool, dark,
ESD-controlled place.

From the error messages, it looks like jlink.exe is about to load the
firmware, but keeps getting bogus string sizes for the fw update.  Tried
several usb cables.  I just thought someone might of seen this, but if not,
I think I'll assume it's DOA.

Thanks,

Steve
Show quoted textHide quoted text
> Message: 2         
>    Date: Tue, 13 Dec 2005 12:54:33 -0800
>    From: "Joel Winarske" <joelw@...>
> Subject: RE: J-Link errors on initial installation
> 
> Is green light solid or blinking?  If driver is not loaded it 
> will just
> blink.  The driver updates the J-Link firmware on the fly.  
> So you want to
> be working with the latest J-Link driver from Segger's website.
> 
> Are you restarting jlink.exe each time you reinsert your 
> J-link, or leaving
> it open?
> 
> The other thing you might want to do is power cycle your 
> machine with J-Link
> plugged in.  Then see if devmgmt.msc (shortcut from 
> start/run) is still
> happy.
> 
> 
> Joel
> 
> > Hi All,
> > 
> > Just plugged in a jlink for the first time.  Usb drivers 
> look good in
> > devman, and green light on unit is on, but I can't talk to 
> it; I thought
> > someone on the list might have seen the following errors before.
> > 
> > Thanks,
> > Steve
> > 
> > J-Link>usb 0
> > Connecting to J-Link via USB (Port: 0)
> > JTAG_GetFirmwareString: J-Link reports unsupported firmware 
> string size of
> > 26956
> >  (expected 112)
> > Could not identify firmware (Read failure)
> > J-Link>usb 1
> > Connecting to J-Link via USB (Port: 1)
> > Can not connect to J-Link via USB.
> > J-Link>usb 2
> > Connecting to J-Link via USB (Port: 2)
> > Can not connect to J-Link via USB.
> > J-Link>usb 3
> > Connecting to J-Link via USB (Port: 3)
> > Can not connect to J-Link via USB.
> > J-Link>usb 0
> > Connecting to J-Link via USB (Port: 0)
> > JTAG_GetFirmwareString: J-Link reports unsupported firmware 
> string size of
> > 27502
> >  (expected 112)
> > Could not identify firmware (Read failure)
> > J-Link>usb 0
> > Connecting to J-Link via USB (Port: 0)
> > JTAG_GetFirmwareString: J-Link reports unsupported firmware 
> string size of
> > 25376
> >  (expected 112)
> > J-Link>

RE: [lpc2000] RE: RE: J-Link errors on initial installation

2005-12-14 by Joel Winarske

> Did all that. Light is solid, rebooted machine, deleted & re-installed
> latest driver from segger site, etc.  Figure the box is just fried?  It's
> been in the dev-kit box unused for a year...but it was in a cool, dark,
> ESD-controlled place.
> 
> From the error messages, it looks like jlink.exe is about to load the
> firmware, but keeps getting bogus string sizes for the fw update.  Tried
> several usb cables.  I just thought someone might of seen this, but if
not,
> I think I'll assume it's DOA.

You might try an incremental update from approximate version of original
manufacture.  Perhaps once you update to a certain version it will take the
most recent.  You might contact Segger directly to get driver archives.

Joel

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.