Thanks Chris. I suspected that was the answer. Reflashing the bootloader is technically possible but comes with $erious downside risk. Imagine hundreds of these things installed in the ceilings of a skyscraper with no jtag access. Now imagine all of them bricked.
Thanks again, Bob. On Aug 20, 2012, at 2:51 PM, Chris Liechti wrote: > Am 20.08.2012 22:53, schrieb Robert Henig: >> Apologies if this is no the right list to ask this question. Please >> redirect me if it is. > > i think this is a good place :-) > >> I have an existing product that implements a bootloader compiled with >> the IAR workbench version 5. To save space we implement the I2C >> driver once in the bootloader and then call if from the main firmware >> code based on known function addresses. I would like to write all >> new firmware using mspgcc. > > :-) > >> The firmware it upgradable but the bootloader is not. > > I am not suggesting that you should do that, but you probably could > upgrade the bootloader with an application that reflashes the boot > loader (unless you have a F5x and use the hardware protection). > > if there is no space in a regular application an dummy app only to > reprogram the bootloader could be used. and in a second step the regular > application is downloaded. > > sure that has the risk of failure and really bricking the device on the > users perspective (you may have JTAG or BSL access to recover). > >> Does anyone know if the calling conversion of the >> two versions is the same or what the differences are? > > different. > > mspgcc used to use R15 down to R12. so up to 4 parameters can be passed > in registers. IAR used R12:R13 and R14:R15 as pairs for up to two > parameters (i've not checked if that changed in more recent versions of > the compilers). Further parameters go on the stack in both compilers. > > You probably need to write a small wrapper function (in your firmware) > that moves the registers forth and back. Personally i'd do these in > assembler (or inline assembler and "naked" function attribute in > mspgcc). To get a start on these you could use the other compiler to > compile a sample function call using all parameters and look at the > listing file or disassembly. > > chris > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
