Andres Vahter writes:
> I do not know anymore how to program using eZ430-F2013
> With version 0.8 it was like this:
> mspdebug -u /dev/ttyUSB2
>
> But how i'm doing it with the new version?
> I do not know which driver to use - there isn't anything similar to
> eZ430-F2013 in the list.
> I know there is another board called eZ430-RF2500 - so i'm guessing RF2500 is
> also right driver for eZ430-F2013?
>
> But how to use it ?
> mspdebug rf2500 -d /dev/ttyUSB2
> MSPDebug version 0.9 - debugging tool for MSP430 MCUs
> Copyright (C) 2009, 2010 Daniel Beer <[email protected]>
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> This driver does not support tty devices.
>
> Another try:
> tmspdebug rf2500 -U /dev/ttyUSB2
> MSPDebug version 0.9 - debugging tool for MSP430 MCUs
> Copyright (C) 2009, 2010 Daniel Beer <[email protected]>
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> usbutil: location must be specified as <bus>:<device>
>
>
> My USB devices:
> mspdebug --usb-list
> MSPDebug version 0.9 - debugging tool for MSP430 MCUs
> Copyright (C) 2009, 2010 Daniel Beer <[email protected]>
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> Devices on bus 005:
> 005:043 0451:f430
> 005:001 1d6b:0001
> Devices on bus 004:
> 004:001 1d6b:0001
> Devices on bus 003:
> 003:001 1d6b:0001
> Devices on bus 002:
> 002:102 0403:6001
> 002:076 0403:6001
> 002:001 1d6b:0001
> Devices on bus 001:
> 001:003 046d:0990
> 001:001 1d6b:0002
>
>
> Last thing i tried:
> mspdebug rf2500 -U 005:043 0451:f430
> MSPDebug version 0.9 - debugging tool for MSP430 MCUs
> Copyright (C) 2009, 2010 Daniel Beer <[email protected]>
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> rf2500: failed to open RF2500 device
>
>
>
> Could you give me an example what are correct arguments using eZ430-F2013.
Hi Andres,
Sorry, I should've mentioned this in the original message. The eZ430
is a UIF-compatible device, so in your case, you'd use a command-line
like this:
mspdebug uif -d /dev/ttyUSB2
Cheers,
Daniel
