[quote user="Chester Gillon"]On further investigation with MSPFlasher v1.3.11 the Intel hex line length is sensitive to something in the debug probe / device used.[/quote]The hex line length in sensitive to the debug probe, not the device used. As a different combination jumpered the ez-FET debug probe on a MSP-EXP430FR5969 to connect to the MSP430G2553 on a MSP-EXP430G2 . This time the same command generated an Intel hex with a line length of 16 bytes (as opposed to the Intel hex line length of 32 bytes when the eZ430 debug probe was used): C:\ti\MSPFlasher_1.3.11>MSP430Flasher.exe -r [test.hex,MAIN] * -----/|-------------------------------------------------------------------- * * / |__ * * /_ / MSP Flasher v1.3.11 * * | / * * -----|/-------------------------------------------------------------------- * * * Evaluating triggers...done * Checking for available FET debuggers: * Found USB FET @ COM44 <- Selected * Initializing interface @ COM44...done * Checking firmware compatibility: * FET firmware is up to date. * Reading FW version...done * Setting VCC to 3000 mV...done * Accessing device...done * Reading device information...done * Dumping memory from MAIN into test.hex...done * * ---------------------------------------------------------------------------- * Arguments : -r [test.hex,MAIN] * ---------------------------------------------------------------------------- * Driver : loaded * Dll Version : 30901002 * FwVersion : 30900000 * Interface : TIUSB * HwVersion : E 4.0 * JTAG Mode : AUTO * Device : MSP430G2xx3 * EEM : Level 1, ClockCntrl 1 * Read File : test.hex (memory segment = MAIN) * VCC OFF * ---------------------------------------------------------------------------- * Powering down...done * Disconnecting from device...done * * ---------------------------------------------------------------------------- * Driver : closed (No error) * ---------------------------------------------------------------------------- */
↧