XC8 Compilers - Discussion

[metal]

XC8 Compilers Discussion Topic

Related XC8 topics, updates, bugs, etc.
No "code does't work" here

[asergin]

MPLAB xc8 v1.01 has been release
http://www.microchip.com/mplabxc8windows

[marcodassi]

seems that MPLAB XC8 1.01 has been removed from microchip's site.
and XC16 download is down.

wondering about a next massive update...

[metal]

I noticed that, I downloaded v1.01 nearly a week ago, and now microchip claims there are bug fixes that were introduced in v1.01, when you report a bug, they just tell you it was fixed in v1.01, this is not true, ... and their site reports that file is not found.. xc8_v1_01_windows.exe

[marcodassi]

XC8 1.01 officially re-upped on Microchip site

EDIT: it's exactly the same as the one from a week ago (compared byte-by-byte)

[metal]

yes, I agree, microchip has seriously ***ed up. The funny thing is that microchip is now lying/misleading about bug fixes and is putting irrelevant images on the support ticket to convince you that they solved the problem!

They are twisting the facts, unbelievable...

[LithiumOverdosE]

Or perhaps HiTech guys are doing the same exact thing. 

[metal]

The problems are mainly in PIC18 compiler. In v1.00 header files were changed and differ from v1.01..

[LithiumOverdosE]

You're talking about incompatibilities between MCC18 and PICC18  I guess?

[metal]

No, I am talking about the new buggy PIC18 CX8. But it was a coincidence when I noticed that the header files were actually changed and differ from v1.01.

[LithiumOverdosE]

Most interesting. I mean, I switched to XC8 and I'm doing a complex project but I haven't encountered any problems so far. I'm also using hardware libs (plib.h) which are basically the same as in PICC-18.

As a side note - I did quick and dirty adaptation of PWM and EPWM libs from PICC-18 to be used with MikroC so if somebody needs them I can post it here.

[metal]

Strange, which PIC chip and what programmer are you using?

[LithiumOverdosE]

I use 18F46K22 together with Proteus and PICkit3. Project involves XC8 (PICC18) EPWM libs together with custom LCD, 1-wire, SHT-75, SD Card and software PID procedures. Not a single problem so far with XC8.

[marcodassi]

@metal:

can you please describe the bug you've found (in 1.00) that wasn't squashed in version 1.01

thank you

[metal]

It is a configuration bits problem. When you set fuses for PIC18, they are not correctly configured, MC is not sure how many chips are affected. The problem is really complicated, it took more than 3 weeks to convince MC that there is a problem. I am not sure if they are going to be able to solve it in the next release.

The workaround for now is that you have to make sure you are using the programmer itself to set the configuration bits, and not to try configuring them neither from the code nor from the configuration bits window in MPALB.

I have not seen any problems with PIC16 chips on XC8, but be sure MC has received tons of bug reports on XC8.

regards.

[odessa]

Is anyone else here getting a crash to desktop using XC8 with a Pickit2?
The machine I'm running on is XP 32bit Sp3.

I know there are seperate drivers for ICD3 etc but can't see anything regarding Pickit2

[metal]

When does it happen, give more information..

It hangs for ever while I am debugging when PICKit3 enters a __delay_us() and __delay_ms() and I must end task MPLAB process.

[odessa]

I would if I could, It happens just after compiling before programming. It's so quick I don't get a chance to read the build window. I'll try my pickit3 and see if that helps, just the place I work uses the pickit2.

[metal]

you can record your desktop to see what the message says, I don't know if MPLAB saves a log in a file as well.

[metal]

Any one tried to use microchip application libraries with xc8?

[8bitMCU]

MPLAB xc8 v1.10 has been release

http://www.microchip.com/mplabxc8windows

[Gallymimu]

xc8 is still a bit buggy.  When using it with the PIC18 at least be careful of whether the IDE detects all of the include files properly.  In my situation the code will compile but the code detection doesn't work correctly (peripheral keywords are indicated as missing). 

Adding a define for:
#define __18Fxxxx

helped, even if #include <p18cxxx.h> exisited already. 

[dotm]

Has anyone an idea how to reformat the __CONFIG() code generated by the config parser in MplabX not to be detected as an error?
says : unexpected token: (
I tried to enter space around the brackets as mentioned in some forums but nothing did work for me.
Altough it compiles without error, the marking in the editorwindow is annoying me!
If they want us to use #pragma instead, why does the config parser not support this formatting? AND(!) it is quite an effort to find the definitions for the options used with #pragma.

[metal]

I assume you are asking about PIC18. In the manual:

2.5.14 Specifying Configuration Bits
The #pragma config directive may be used to program the configuration bits for a device. The pragma has the form:
#pragma config setting = state|value
2.5.14.1 EXAMPLE
The following shows configuration bits being specified using this pragma.
#pragma config WDT=ON, WDTPS = 0x1A
3.6.11 What Devices are Supported by the Compiler?
HTML listings are provided in the compiler’s docs directory. Open these in your favorite web browser. They are called pic_chipinfo.html and pic18_chipinfo.html.
5.3.5 Configuration Bit Access
The settings and values associated with PIC18 devices can be determined from an HTML guide. Open the file pic18_chipinfo.html, which is located in the DOCS directory of your compiler installation. Click on your target device and it will show you the settings and values that are appropriate with this pragma. Check your device data sheet for more information.

Look up this file under "..\Microchip\xc8\v1.11\docs\" Open it and find your chip, click on the chip-link and you will find info about the config bits for your chip and how to correctly configure them.

Read the manual before complaining :- )

Here is an example for PIC181330:

Code:

#pragma config IESO = OFF
#pragma config OSC = INTIO2
#pragma config FCMEN = OFF
#pragma config BOR = BOHW
#pragma config BORV = 2 //2.7 volts
#pragma config PWRT = ON
#pragma config WDTPS = 1
#pragma config WDT = OFF
#pragma config PWMPIN = OFF
#pragma config HPOL = HIGH
#pragma config LPOL = HIGH
#pragma config T1OSCMX = HIGH
#pragma config FLTAMX = RA5
#pragma config MCLRE = OFF
#pragma config DEBUG = ON
#pragma config STVREN = OFF
#pragma config XINST = OFF
#pragma config BBSIZ = BB256
#pragma config CP0 = OFF
#pragma config CP1 = OFF
#pragma config CPD = OFF
#pragma config CPB = OFF
#pragma config WRT0 = OFF
#pragma config WRT1 = OFF
#pragma config WRTB = OFF
#pragma config WRTC = OFF
#pragma config WRTD = OFF
#pragma config EBTR0 = OFF
#pragma config EBTR1 = OFF
#pragma config EBTRB = OFF

[dotm]

Read the manual before complaining :- )

Damn. I lower my head in shame. Is Pic16 though but you're right everything is there.