Be aware that XC8 doesn't support the extended instruction set... I had to disable it in the chip config for the compiler to produce output. Surprising.
<http://www.microchip.com/forums/m710874.aspx> This may clarify the choice for you! J > Hi, > > I'm at cross roads, should I go on with SDCC (which I'm happy > with and familiar) or move to MPLAB X compilers... > > The dilemma: > > I'm planning to use the Diolan bootloader which uses extended > instructions set. That bootloader is very nice as it is in > asm and fits (just!) into the boot block and offers encryption > for the firmware to be bootloaded. > > Problem is that code compiled with SDCC does not work with > the extended instruction set enabled and as this [extended > instruction set mode] cannot be changed at run time this > combination [SDCC and diolan] does not work. > > I converted the diolan bootloader to 'legacy' mode, but > of course it did not fit. So I've optimised it and now it > fits and runs, but the encryption does not work properly, > obviously some of optimisations or conversion broke something. > > I'm working on fixing that but the big question is, if I > would be better of with MPLABX compilers in the long run... > > In theory the MPLABX compiler with the extended instruction > set enabled should produce better and faster code so in > that respect the answer is obvious ... why go through all > the trouble making the diolan work with SDCC... OTH > emigrating to a new compiler is bound incur some pain and > a learning curve. Also my own USB stack optimised for SDCC > is half size of the (Free) USB M-stack (not to mention > Microchip's own stack) ... at least when compiled with > the free MLABX C-compiler. > > As this is a free as beer project I don't feel like paying > for the compiler ... though I could afford it. > > So any on going work on SDCC to support extended instruction > set? > > I could live with code generation that does not take advantage > of the extended instruction set as long as the generated code > would be compatible with it. > > This document (at the end) mentions that it is possible to > write code like that with some 'hacks' > > diolan plus readme.zip > <http://dangerousprototypes.com/forum/download/file.php?id=5934&sid=783f188 > 28453f727272fbda73537545d> > > I'm not familiar with SDCC code generation or PIC assembly > so I can't evaluate if it would realistic to do something like > that. > > cheers Kusti > > > > ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
