Re: MSP-FET430UIF and mspdebug
Sarfraz Nawaz <[email protected]>
| Newsgroups | gmane.comp.hardware.texas-instruments.msp430.gcc.user |
|---|---|
| Message-ID | <CACDibgHV-TTkYHCNBjaTN971t_V45OJSiVmifgOKJep-1icjtQ@mail.gmail.com> |
Hi Daniel, Thank you for the reply. I tried your suggestion of dropping the leading "/dev/" and this is what I get on Linux. I get the same error on Windows 7 with a precompiled dll that ships with TI's flasher tool. Any idea that what might be wrong? Or how to fix it? Thanks. mspdebug tilib -d ttyACM0 --allow-fw-update MSPDebug version 0.22 - debugging tool for MSP430 MCUs Copyright (C) 2009-2013 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. MSP430_Initialize: ttyACM0 Firmware version is 30400020 MSP430_VCC: 3000 mV tilib: MSP430_VCC: Could not set device Vcc (error = 10) tilib: device initialization failed On Sun, Mar 2, 2014 at 9:27 PM, Daniel Beer <[email protected]> wrote: > On Sat, Mar 01, 2014 at 06:49:17PM +0000, Sarfraz Nawaz wrote: >> mspdebug tilib -d /dev/ttyACM0 >> >> MSPDebug version 0.22 - debugging tool for MSP430 MCUs >> Copyright (C) 2009-2013 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. >> >> MSP430_Initialize: /dev/ttyACM0 >> tilib: MSP430_Initialize: Could not find MSP-FET430UIF on specified >> COM port (error = 57) >> tilib: device initialization failed >> >> but it shows up as /dev/ttyACM0 > > TI's library always prepends "/dev/" to the filename you give it. Try > with -d ttyACM0 instead. > > Cheers, > Daniel > > -- > Daniel Beer <[email protected]> www.dlbeer.co.nz > IRC: inittab (Freenode) PGP key: 2048D/160A553B ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk