Benjamin Schmidt wrote:
> On Tuesday 19 May 2009 03:19:06 pm Gene Smith wrote:
>> Info : J-Link compiled Dec 2 2004 09:13:33
>
> That seems like a very very old firmware version. And I just remembered
> something...
>
> When I got my JLink, it was on a somewhat old firmware version as well...
> Linux segger tool did nothing at all...
> But when I hooked it up to the windows version of these segger tools, it
> asked
> me whether to update the device or not. (Wine did not do the job, had to use
> a
> native win xp setup for that)
>
> After that I could use the linux tool as well
>
> Maybe you could try that first
>
> Benjamin
Just loaded the windows tools and ran J-Link Commander. Can't seem to
copy/paste from its terminal so I will type in what it says:
SEGGER J-Link Commander V4.05i ('?' for help)
Compiled May 18 2009 19:21:08
DLL version V4.05i, compiled May 18 2009 19:20:52
Firmware: J-Link compiled Feb 20 2006 18:20:20 -- Update --
Hardware: V4.30
S/N : 10001576
OEM: IAR
VTarget = 3.250V
Info: TotalIRLen = 4, IRPrint = 0x01
Found 1 JTAG device, Total IRLen = 4:
Id of device #0: 0x3f0f0f0f
Found ARM with cord Id 0x3f0f0f0f (ARM7)
JTAG speed: 5 kHz
This did not ask me to update f/w. I think yesterday linux version may
have actually updated it to what is says above, not sure. The info above
looks right. The serial number is correct and matches what is printed on
the bottom.
I may not have mentioned that the Linux version of J-Link Commander
always says after starting:
"Can not connect to J-Link via USB"
while windows version above issues no such complaint.
Appears to probably be a USB comm problem. But I have no problem with
other USB devices on same linux box (mem sticks, SD cards, eth adapters,
etc.)
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
