On Sat, Mar 08, 2014 at 09:40:07PM +0000, Sarfraz Nawaz wrote: > Looking at the data sheet of MSP430F5528, this is what I see in the > memory organisation map, > > Interrupt vector table 0xffff to 0xff80 (128 bytes) > Main code memory 0x243ff to 0x4400 (131072 bytes or 128 Kb) > > So using the following two will give me enough information to restore > the firmware? > > "hexout 0xff80 128 invtable.hex" > > "hexout 0x4400 131072 main.hex" > > How can I restore the firmware with these two hex files? > > I am just curious that why do I have to save the interrupt vector > table? MSPFlasher only gives the option of reading out the main, bsl, > info and ram but no interrupt vector table. I can save it using > mspdebug but was just curious.
Hi Sarfraz, In this case, the interrupt vector table is a subset of the main flash, so you only need one hexout command: hexout 0x4400 131072 main.hex You can restore with: prog main.hex Cheers, Daniel -- Daniel Beer <dlb...@gmail.com> 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 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users