On Mon, Aug 26, 2013 at 06:44:11PM +1200, Andrew McLaren wrote: > I've done a bit more poking, and understand this a bit more. I gather the > TI3410 is a USB-serial chipset used internally in the FET, not the FET > itself. Still unsure why this decided it needed new firmware after > connecting once? > > Was just going to ask where this firmware came from, but have just found the > hex file in the mspdebug build directories. I had moved the mspdebug into my > mspgcc runtime structures from where it was built, but of course had left > the TI3410 firmware behind... I appear to be running again!
Hi Andrew, Glad to hear you got it working. By default the TI3410 contains no firmware except for a very basic bootloader. Every time you plug it in, the bootloader is fed the firmware in the HEX file, which goes into the TI3410's RAM. The chip restarts, and then you have a functioning USB-UART. Since the firmware is only ever stored in RAM, this needs to be done every time you repower the chip, but it should ideally be automatic and seamless. Cheers, Daniel -- Daniel Beer <dlb...@gmail.com> www.dlbeer.co.nz IRC: inittab (Freenode) PGP key: 2048D/160A553B ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
