Magnus Lundin wrote:
> The following patch combines my previous patch with most of Ben's patch. 
> It can use both  EMU_CMD_HW_JTAG2  and   EMU_CMD_HW_JTAG3
> 
> It defaults to EMU_CMD_HW_JTAG2 so it should work with all interfaces 
> but EMU_CMD_HW_JTAG3 is recommended by SEgger,  you can change the 
> behaviour with
> 
>  > jlink_hw_jtag  3
> or
>  > jlink_hw_jtag  2
> 
> Autodetection can be done when we know which versions JLink can use what 
> setting,  (-d3 logs of setup messages )
> 
> Have a nice day
> Magnus
> 

Seems to work OK for me too (hw version yellow/V4 OEM IAR). If I do 
"jlink_hw_jtag 2" it loses USB comm (LED on jlink goes off) and I see 
messages:

jlink hw jtag  3
Error: usb_bulk_read failed (requested=12, result=-110)
Error: jlink_tap_execute, wrong result -107 (expected 12)
Error: usb_bulk_read failed (requested=12, result=-110)
Error: jlink_tap_execute, wrong result -107 (expected 12)
Error: usb_bulk_read failed (requested=12, result=-110)
:
:Must restart openocd to recover.

Note: see similar string of messages if USB is unplugged from Jlink 
while running and must restart it. Does not recover when USB replugged.

So I guess I must use 2.

Still see occasional segfault on startup (still running r1833 except for 
jlink.c patch).

-gene




_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to