the XINST is a red herring. What ever is the instability causeing compiler to crash when there are no errors (1st phase of p-code to asm after syntax check OK, I think) is not affected one way or the other by XINST.
The ORDER of pragmas might be important. I don't know. I can't identify why one set of files compiles and the other doesn't I now have the full project compiling perfect with 18f67j50 include. pragma target clock 48_000_000 -- fuses pragma target PLLDIV P5 -- Pn where n x 4 = crystal MHz pragma target CPUDIV P2 -- OSC1_OSC2_SRC_1_96MHZ_PLL_SRC_2 -- next line for 18F4550, but what does it do? --pragma target USBPLL F48MHZ -- CLOCK_SRC_FROM_96MHZ_PLL_2 pragma target OSC HS_PLL pragma target FCMEN DISABLED pragma target IESO DISABLED --pragma target PWRTE ENABLED -- power up timer --pragma target VREGEN ENABLED -- USB voltage regulator --pragma target VOLTAGE V20 -- brown out voltage --pragma target BROWNOUT DISABLED -- no brownout detection --pragma target WDTPS P32K -- watch dog saler setting --pragma target WDT DISABLED -- no watchdog --pragma target CCP2MUX pin_C1 -- CCP2 pin --pragma target PBADEN DIGITAL -- digital input port<0..4> --pragma target LPT1OSC LOW_POWER -- low power timer 1 --pragma target MCLR EXTERNAL -- master reset on RE3 --pragma target LVP DISABLED -- no low-voltage programming pragma target XINST ENABLED -- extended instruction set pragma target DEBUG DISABLED -- background debugging pragma target STVR DISABLED -- reset on stack over/under flow --pragma target CP0 DISABLED -- code block 0 not protected --pragma target CP1 DISABLED -- code block 1 not protected --pragma target CP2 DISABLED -- code block 2 not protected --pragma target CP3 DISABLED -- code block 3 not protected --pragma target CPB DISABLED -- bootblock code not write protected --pragma target CPD DISABLED -- eeprom code not write protected --pragma target WRT0 DISABLED -- table writeblock 0 not protected --pragma target WRT1 DISABLED -- table write block 1 not protected --pragma target WRT2 DISABLED -- table write block 2 not protected --pragma target WRT3 DISABLED -- table write block 3 not protected --pragma target WRTB DISABLED -- bootblock not write protected --pragma target WRTD DISABLED -- eeprom not write protected --pragma target WRTC DISABLED -- config not write protected --pragma target EBTR0 DISABLED -- table read block 0 not protected --pragma target EBTR1 DISABLED -- table read block 1 not protected --pragma target EBTR2 DISABLED -- table read block 2 not protected --pragma target EBTR3 DISABLED -- table read block 3 not protected --pragma target EBTRB DISABLED -- boot block not protected I'm unhappy with how clock and dividers are specified We need either a better syntax or a "builder" wizard that asks you what cpu type, CPU clock & USB and other options you want and then asks you to pick a crystal...then builds the config words... I don't know what the solution is except I think current "pragma" system is flawed. I'm temped to write a GUI wizard that automatically selects the include file and all config words -- 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.
