Hi,
it took me some time to figure out how to use an Olimex JTAG Tiny V2
because, under Linux, it behaves so much differently than the previous
version.
The new device type will easily provide a serial port via cdc_acm (USB
communication class device) without further kernel patching
(e.g. /dev/ttyACM0).
Unfortunately it needs different modem line settings and (probably) a
different speed: no CTS, no DTR, 115200 baud.
The including patch will make a V2 work - at the cost of probably
destroying V1 serial support.
Hopefully this information will save other people some grief, so …
Merry Christmas and a Happy New Year to all
Christof
PS: Thank you for solving so many other problems by creating mspdebug -
it is great!
PPS: The direct USB connection did not work for me …
$ ./mspdebug --usb-list
003:003 15ba:0031 Olimex MSP-JTAG-TINY (v2) [serial: 00000381]
$ ./mspdebug olimex
MSPDebug version 0.18 - debugging tool for MSP430 MCUs
usbutil: unable to find a device matching 15ba:0002
drivers/olimex.c: Trying to open interface 1 on 003
drivers/olimex.c : driver -61 (first time 0)
drivers/olimex.c: open_interface: Sending control message
CP210x_REQTYPE_HOST_TO_DEVICE, ret = -32
drivers/olimex.c: can't enable CP210x UART: Broken pipe
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
