Hi Daniel, 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. Cheers On Fri, Mar 7, 2014 at 11:44 PM, Daniel Beer <dlb...@gmail.com> wrote: > On Fri, Mar 07, 2014 at 10:29:26PM +0000, Sarfraz Nawaz wrote: >> I have finally managed to get the FET talking to my board! I >> downgraded the FET to V2 and then upgraded it again to V3 using TI's >> MSPFlasher. Now I can make a JTAG connection to the board using both >> MSPFlasher and mspdebug. >> >> I have one more query related to this. My board comes pre-programmed >> with software from the vendor and is functioning properly. Now before >> I start playing with it, I want to read out an image that I can use to >> restore the board to its working state if I mess up. Looking at the >> memory map of MSP430F5528 in the data sheet, the flash memory starts >> at 0x4400. So doing a "hexout 0x4400 0xbbff defaultimage.hex" on >> mspdebug prompt will give me a restorable image? Or do I have to do >> something else to achieve this? > > Hi Sarfraz, > > The second argument to hexout is the size of the region, rather than the > ending address. > > It'd be best to grab one image for each contiguous flash region (main > and interrupt vector table, if there's a gap between them). You can trim > the HEX header and footer and splice them together if you want to be > able to restore in one step. > > 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
