Xiaofan Chen wrote:
> On Mon, May 18, 2009 at 11:09 PM, Gene Smith <[email protected]> wrote:
>> Mine says: Updating firmware: J-Link compiled Feb 20 2006 18:20:20 --
>> Update --
>> Mine says: Replacing firmware J-Link compiled Dec 2 2004 09:13:33
>> Mine says: S/N : -3
>
> Kind of strange. Could you try the segger utilities under Windows?
Will give it a try.
>
> C:\Program Files\SEGGER\JLinkARM_V337a>jlink
> SEGGER J-Link Commander V3.37a ('?' for help)
> Compiled Aug 8 2006 19:16:44
> DLL version V3.37a, compiled Aug 8 2006 19:16:40
> Firmware: J-Link ARM V6 compiled Dec 03 2007 17:34:18
> Hardware: V6.00
> S/N : xxxxxx
> OEM : IAR
> ...
>
>> WARNING: No matching core found. Selecting default core (ARM7)
>>
>> *** Error: could not read hardware status!
>> JTAG speed: 5 Hhz
>> J-Link>
>> Green LED goes off then *don't* see exactly what you see:
>
> What does dmesg says when this happens? Something
> is wrong with your kernel or this particular version of J-Link.
The only thing I see with dmesg or tail -f /var/log/messages is this
series of messages when I plug the usb into the yellow jlink. The LED
blinks fast for about 30-45 seconds then goes solid when the last
message appears:
May 19 09:20:20 localhost kernel: usb 5-1: USB disconnect, address 61
May 19 09:20:24 localhost kernel: usb 5-1: new full speed USB device
using uhci_hcd and address 62
May 19 09:20:34 localhost kernel: usb 5-1: string descriptor 0 read
error: -110
May 19 09:20:54 localhost kernel:last message repeated 2 times
May 19 09:20:54 localhost kernel: usb 5-1: configuration #1 chosen from
1 choice
May 19 09:20:54 localhost kernel: usb 5-1: New USB device found,
idVendor=1366, idProduct=0101
May 19 09:20:54 localhost kernel: usb 5-1: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Running openocd command or the segger utility commands does produces no
new messages. (FYI: this is fedora 8 with last possible updates.) But
openocd commands to the jlink cause the LED to go off but segger
commands don't.
>
>> My libusb on my fedora 8 is libusb-0.1.12-10.fc8. Do you think I might
>> need a newer libusb? That is the last version it updated to.
>>
>
> That should be fine. libusb 0.1 has not changed for a while.
>
> David Brownell is on this list and he is a prominent member of the
> Linux USB kernel team. So if there is a real USB/Kernel issue here,
> I think he can probably help you here. ;-)
>
>
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
