Re: MSPDebug unable to find 0451:f430

On Sat, Nov 23, 2013 at 01:20:02PM -0800, garyr wrote:
> My OS is XP, Im using the FET430UIF. I've installed MSPDebug according to the
> instructions for Windows in the FAQ with one exception:
> 
> The libusb-win32 I found is libusb-win32-1.2.6.0.zip. I couldn't find a
> libusb0.dll so I extracted bin\x86\libusb0_x86.dll to MSPDebug\. When I ran
> MSPDebug I get an error message because libusb0.dll was not found.
> I then renamed libusb0_x86.dll to libusb0.dll. Now running MSPDebug yields the 
> above error.
> 
> The FET works with IAR Kickstart. The Device Manager says the FET has
> vid/pid of 2047:001. Now
> 
> C:\MSPDebug>mspdebug uif -U2047:0010
> MSPDebug version 0.22 - debugging tool for MSP430 MCUs
> ...snip...
> usbutil: unable to find 2047:010
> 
> The file ti_3410.fw.ihex is present in C:\MSPDebug.

Hi Gary,

If your device actually does have a vendor:product ID of 2047:0010, then
you have V3 firmware, and will need to use the V3 DLL from TI:

    http://processors.wiki.ti.com/index.php/MSP_Debug_Stack#Downloads

Download the "DLL Developers Package", extract and place MSP430.DLL in
your PATH (or wherever you run mspdebug from). Then use the "tilib"
driver:

    mspdebug tilib

Cheers,
Daniel

-- 
Daniel Beer <[email protected]>    www.dlbeer.co.nz
IRC: inittab (Freenode)    PGP key: 2048D/160A553B

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk