On 04/18/2014 04:52 PM, Peter Bigot wrote: > The result would be a single image combining bootloader and > application which could be flashed with mspdebug without having to > figure out how to erase only the application parts of the memory, > leaving the bootloader. > > Of course, since this would couple the application to the bootloader > it's not clear what value the bootloader has.
If the bootloader does not stay available through the standard compile cycle, all of the rely-on-it value is gone. IOW, you could do a pilot error mistake in compiling to install a dead bootloader and be stuck. So, you would have to define strict ways of doing compiles to stay productive. So you could rely on the bootloader being there and working. Not that I have any experience in writing bootstrapping code...but I have done some chip circuits, where you decide what you want in a meeting, then make it happen in hardware with a code method in mind. Just a point to ponder. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
