Albert's bootloader use XINST ENABLED and all applications adapted for it works as a dream. Is the case for Jaluino and FreeJALduino boards which use this bootloader.
Vasi(funlw65) On Apr 15, 10:38 am, Rob Hamerling <[email protected]> wrote: > On 04/15/10 03:56 pm, m...@watty wrote: > > >> I'll add 'pragma target XINST disabled' to the blink samples (of PICs > >> with that config bit) with the comment 'not supported by JalV2' as > >> reminder. > > > no need > > Maybe not for the blink samples themselves, but solely as a general > reminder. > > > > > the giant 18F4550 version of catpad, even with file transfer enabled > > (106 bytes free in 32K!) with "pragma target XINST ENABLED" > > compiles and works on target hardware fine. > > I must say I don't understand why Kyle says it's 'not wise' to use XINST > enabled. I would think that it won't harm when the compiler doesn't > generate extended instructions. It can imagine it could give problems > when inline assembly uses extended instructions, but I suppose the > compiler doesn't accept the mnemonics of extended instructions either. > > Regards, Rob. > > -- > Rob Hamerling, Vianen, NL (http://www.robh.nl/) -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
