At least one problem have been caught: latest FW does not select JTAG
transport by default.

I've added EMU_CMD_SELECT_IF command to the jlink_init().
At least initial setup steps are passed now, my cores is detected normally.

The second patch is on top of previous, "unsupported versions".
I think this patch should be kept for some time, to warn users about
potential problems.
I've changed the message to "warning" class, and add a segger's site reference.

I have problem connecting to gerrit from behind firewall;
using http[s]://openocd.zylin.com/p/openocd.git
asks username/password, and not accepting ssh keys and "http password"
from the zylin's control panel.

If sometimes I will happen to connect,
- should such chained patches be uploaded as separate push operations,
  or as single push of a branch containing all of them ?
- may I use a local branch, or must go to 'origin/master' before push?

Regards,
Alex.

Attachment: 0001-J-Link-Unsupportedfirmwareversioncheck.patch
Description: Binary data

Attachment: 0002-J-Link:-Forcibly-select-JTAG-transport.patch
Description: Binary data

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to