openocd-devel

[Openocd-development] Busted JLink

[Rogan D. <ro...@da...>]

Hi folks,

I have a clone JLink adapter, that was working fine with OpenOCD (apart
from my not being able to access the flash at the time).

I decided to try it with the JLink software, and it upgraded the
firmware. Every since, I have been unable to use it with OpenOCD.

My config file is available here:

http://dawes.za.net/rogan/dns323.cfg

I invoke it as:

openocd -d3 -l jlink.log -f interface/jlink.cfg -f dns323.cfg -s "mdw
0xffff0000 0x10; sleep 100; shutdown"

(Just to get it to do something, then exit as soon as possible).

The log is available at:

http://dawes.za.net/rogan/jlink_201105102028.log

The main problem appears to be these lines:

Error: 294 300 jlink.c:1541 jlink_usb_message(): jlink_usb_message
failed with result=255)
Error: 295 300 jlink.c:1367 jlink_tap_execute(): jlink_tap_execute,
wrong result -107 (expected 1)

Does anyone know what that means, and if there is anything I can do to
fix them?

Thanks

Rogan

Re: [Openocd-development] Busted JLink

[Jean-Christophe PLAGNIOL-V. <pla...@jc...>]

On 20:30 Tue 10 May     , Rogan Dawes wrote:
> Hi folks,
> 
> I have a clone JLink adapter, that was working fine with OpenOCD (apart
> from my not being able to access the flash at the time).
> 
> I decided to try it with the JLink software, and it upgraded the
> firmware. Every since, I have been unable to use it with OpenOCD.
> 
> My config file is available here:
> 
> http://dawes.za.net/rogan/dns323.cfg
> 
> I invoke it as:
> 
> openocd -d3 -l jlink.log -f interface/jlink.cfg -f dns323.cfg -s "mdw
> 0xffff0000 0x10; sleep 100; shutdown"
> 
> (Just to get it to do something, then exit as soon as possible).
> 
> The log is available at:
> 
> http://dawes.za.net/rogan/jlink_201105102028.log
> 
> The main problem appears to be these lines:
> 
> Error: 294 300 jlink.c:1541 jlink_usb_message(): jlink_usb_message
> failed with result=255)
> Error: 295 300 jlink.c:1367 jlink_tap_execute(): jlink_tap_execute,
> wrong result -107 (expected 1)
which version of openocd do you use and which jlink version?

Best Regards,
J.

Re: [Openocd-development] Busted JLink

[Rogan D. <ro...@da...>]

On 2011/05/11 3:47 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 20:30 Tue 10 May     , Rogan Dawes wrote:
>> Hi folks,
>>
>> I have a clone JLink adapter, that was working fine with OpenOCD (apart
>> from my not being able to access the flash at the time).
>>
>> I decided to try it with the JLink software, and it upgraded the
>> firmware. Every since, I have been unable to use it with OpenOCD.
>>
>> My config file is available here:
>>
>> http://dawes.za.net/rogan/dns323.cfg
>>
>> I invoke it as:
>>
>> openocd -d3 -l jlink.log -f interface/jlink.cfg -f dns323.cfg -s "mdw
>> 0xffff0000 0x10; sleep 100; shutdown"
>>
>> (Just to get it to do something, then exit as soon as possible).
>>
>> The log is available at:
>>
>> http://dawes.za.net/rogan/jlink_201105102028.log
>>
>> The main problem appears to be these lines:
>>
>> Error: 294 300 jlink.c:1541 jlink_usb_message(): jlink_usb_message
>> failed with result=255)
>> Error: 295 300 jlink.c:1367 jlink_tap_execute(): jlink_tap_execute,
>> wrong result -107 (expected 1)
> which version of openocd do you use and which jlink version?
> 
> Best Regards,
> J.

Hi,

I am using the latest git master, and I am currently using:

Info : 226 297 jlink.c:798 jlink_get_version_info(): J-Link ARM V8
compiled Jan 31 2011 18:34:52

Thanks,

Rogan

Re: [Openocd-development] Busted JLink

[Xiaofan C. <xia...@gm...>]

On Wed, May 11, 2011 at 2:30 AM, Rogan Dawes <ro...@da...> wrote:
> I have a clone JLink adapter, that was working fine with OpenOCD (apart
> from my not being able to access the flash at the time).
>
> I decided to try it with the JLink software, and it upgraded the
> firmware. Every since, I have been unable to use it with OpenOCD.
>
> Does anyone know what that means, and if there is anything I can do to
> fix them?

I think you can try downgrade the firmware version. Please refer to Section
9.5.2 of the Segger J-Link documentation.
http://www.segger.com/cms/admin/uploads/productDocs/UM08001_JLinkARM.pdf

-- 
Xiaofan

Re: [Openocd-development] Busted JLink

[Rogan D. <ro...@da...>]

On 2011/05/11 6:52 AM, Xiaofan Chen wrote:
> On Wed, May 11, 2011 at 2:30 AM, Rogan Dawes <ro...@da...> wrote:
>> I have a clone JLink adapter, that was working fine with OpenOCD (apart
>> from my not being able to access the flash at the time).
>>
>> I decided to try it with the JLink software, and it upgraded the
>> firmware. Every since, I have been unable to use it with OpenOCD.
>>
>> Does anyone know what that means, and if there is anything I can do to
>> fix them?
> 
> I think you can try downgrade the firmware version. Please refer to Section
> 9.5.2 of the Segger J-Link documentation.
> http://www.segger.com/cms/admin/uploads/productDocs/UM08001_JLinkARM.pdf
> 

Hi,

Yes, I tried downgrading the firmware (installed older versions of the
JLink software until I found the version it came with). No change in
behaviour, unfortunately.

Regards,

Rogan

Re: [Openocd-development] Busted JLink

[Sébastien B. <sba...@gm...>]

On 11/05/11 06:53, Rogan Dawes wrote:
> Hi,
> Yes, I tried downgrading the firmware (installed older versions of the
> JLink software until I found the version it came with). No change in
> behaviour, unfortunately.
>
> Regards,
>
> Rogan
>
> _______________________________________________
> Openocd-development mailing list
> Ope...@li...
> https://lists.berlios.de/mailman/listinfo/openocd-development
Hello Rogan,

Did you correctly downgrade the firmware of the JLink ? I asked because 
I faced the exact same issue a couple of weeks ago. I don't remember the 
exact steps, but here's what I did :

1- Download version 4.10i of the firmware ( 
http://www.segger.com/cms/admin/uploads/userfiles/file/J-Link/Setup_JLinkARM_V410i.zip 
).
2- Run 'exec invalidateFw' in Segger's command line tool.
3- Reconnect the JLink using the 4.10i version of the software and the 
firmware should be updated automatically.

Kind regards,
Sébastien.

Re: [Openocd-development] Busted JLink

[Rogan D. <ro...@da...>]

On 2011/05/11 10:53 AM, Sébastien Baillou wrote:
> Hello Rogan,
> 
> Did you correctly downgrade the firmware of the JLink ? I asked because
> I faced the exact same issue a couple of weeks ago. I don't remember the
> exact steps, but here's what I did :
> 
> 1- Download version 4.10i of the firmware (
> http://www.segger.com/cms/admin/uploads/userfiles/file/J-Link/Setup_JLinkARM_V410i.zip
> ).
> 2- Run 'exec invalidateFw' in Segger's command line tool.
> 3- Reconnect the JLink using the 4.10i version of the software and the
> firmware should be updated automatically.
> 
> Kind regards,
> Sébastien.

Hi Sebastien,

I had done the downgrade with v2.14, but I tried also with 2.10i.

I get the following errors:

$ openocd -f interface/jlink.cfg -f dns323.cfg -s "mdw 0xffff0000 0x10;
sleep 100; shutdown"
Open On-Chip Debugger 0.5.0-dev-00871-g522d5b8 (2011-05-04-17:13)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.berlios.de/doc/doxygen/bugs.html
Warn : Adapter driver 'jlink' did not declare which transports it
allows; assuming legacy JTAG-only
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
srst_only separate srst_gates_jtag srst_open_drain
5 kHz
8 kHz
Info : J-Link initialization started / target CPU reset initiated
Info : J-Link ARM V8 compiled DEC  1 2009 11:42:48
Info : J-Link caps 0xb9ff7bbf
Info : J-Link hw version 80000
Info : J-Link hw type J-Link
Info : J-Link max mem block 9576
Info : J-Link configuration
Info : USB-Address: 0x0
Info : Kickstart power on JTAG-pin 19: 0x0
Info : Vref = 2.834 TCK = 1 TDI = 1 TDO = 0 TMS = 0 SRST = 0 TRST = 1
Info : J-Link JTAG Interface ready
Info : clock speed 8 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: feroceon.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Embedded ICE version 0
Info : feroceon.cpu: hardware has 1 breakpoint/watchpoint unit
Error: unexpected Feroceon EICE version signature
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: feroceon.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: unexpected Feroceon EICE version signature
Error: unexpected Feroceon EICE version signature
Error: timed out while waiting for target halted
TARGET: feroceon.cpu - Not halted

Runtime Error: dns323.cfg:365:
in procedure 'script'
at file "embedded:startup.tcl", line 58
in procedure 'reset' called at file "dns323.cfg", line 365
$

The target WAS powered at the time.

Rogan