On 22/08/12 19:43, Robert Henig wrote: > Hi JM, > > This is exactly what we do. The bootloader I speak of is the > copy-load program you refer to. Since our code is more then 1/2 the > available space in the MSP we have an external EEPROM. The > bootloader checks there to see if there is code ready for upgrade on > startup. The bootloader implements an I2C driver to do it's job. > It's that driver that is shared that I would like to call from mspgcc > compiled code. The bootloader was compiled using the IAR compiler. >
I find it hard to imagine "i2c driver code" that is big enough to make all this worth the effort. Code to access an external eeprom by I2C is going to be no more than a couple of dozen lines of C code. Do you really /need/ to re-use it in this way? Remember, there is no point to this exercise unless you are sure you have to do it - it will be much faster, easier, and safer to use code compiled within the main program. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
