#67 VID/PID for usbconn cables are parsed as decimal

[Kolja Waschk]

Reported by Steve Franks

jtag> cable jlink vid=1366 pid=0101
Couldn't connect to suitable USB device.
Error: Cable connection failed!

jtag> cable jlink
J-Link initial read failed, don't worry (result=-110)
Vref = 0.0 TCK=1 TDI=1 TDO=1 TMS=1 TRES=1 TRST

[Kolja Waschk]

Logged In: YES
user_id=478715
Originator: YES

Hm, the vid/pid is currently only parsed in decimal. Shall we make hex the default? Or require "0x" prefix for hex PID/VID?

jtag> cable jlink vid=4966 pid=257
J-Link initial read failed, don't worry (result=-110)
Vref = 0.0 TCK=1 TDI=1 TDO=1 TMS=1 TRES=1 TRST=1

[Kolja Waschk]

Logged In: YES
user_id=478715
Originator: YES

Changed title of the bug because the actual problem is the parsing of the vid/pid as decimal. I think we should rather allow hex only.

[Kolja Waschk]

Logged In: YES
user_id=478715
Originator: YES

Now the argument X to vid=X or pid=X is interpreted as hexadecimal, with optional "0x" prefix.

[Kolja Waschk]

Logged In: YES
user_id=478715
Originator: YES

(in revision 1229)