Gene Smith wrote:
> 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.
I forgot that I have to run "./start" as root or sudo or you get this error.
>
> 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.)
Well, I was wrong. Running this in Windows (XP) does seem to do
something to the jlink device. When I put it back on linux version of
J-Link Cmdr it now works better (have to run as root).
[g...@localhost jlink-segger]$ sudo ./start
Password:
SEGGER J-Link Commander V4.03a ('?' for help)
Compiled Feb 2 2009 11:34:21
DLL version V4.03a, compiled Feb 2 2009 11:34:13
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
WARNING: Identified core does not match configuration. (Found: ARM7,
Configured: None)
Found 1 JTAG device, Total IRLen = 4:
Id of device #0: 0x3F0F0F0F
Found ARM with core Id 0x3F0F0F0F (ARM7)
JTAG speed: 5 kHz
J-Link>f
Firmware: J-Link compiled Feb 20 2006 18:20:20 -- Update --
Hardware: V4.30
Also, now when I run openocd it seem better now:
[g...@localhost src]$ sudo ./openocd -f target/interface/jlink.cfg -f
target/board/iar_str712_sk1.cfg
Password:
Open On-Chip Debugger 0.2.0-in-development (2009-05-19-10:03) svn:1833M
BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
$URL: svn://localhost:36903/openocd/trunk/src/openocd.c $
10 kHz
Info : J-Link compiled Feb 20 2006 18:20:20 -- Update --
Info : JLink caps 0x3
Info : Vref = 3.251 TCK = 1 TDI = 1 TDO = 0 TMS = 1 SRST = 1 TRST = 1
Info : J-Link JTAG Interface ready
Error: usb_bulk_read failed (requested=1, result=-110)
Error: jlink_tap_execute, wrong result -107 (expected 1)
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive
packet not sent! (3217). Workaround: increase "set remotetimeout" in GDB
Error: usb_bulk_read failed (requested=1, result=-110)
Error: jlink_tap_execute, wrong result -107 (expected 1)
Error: usb_bulk_read failed (requested=1, result=-110)
Error: jlink_tap_execute, wrong result -107 (expected 1)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
However, when telnet'ing, I still get usb_bulk_read failed errors when I
do anything such as jlink_info, halt or reg.
A few more observations: When I plug the linux usb to the jlink the
blinking time is now only about a second (before it was 30-45 seconds).
Also, lsusb -vvv now shows the segger device like Xiaofan posted. So
running the windows J-Link Cmdr did something to the jlink.
I am using the jlink.c patch from Magnus he posted this morning.
-gene
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
