XC8 Compilers - Discussion

[koky]

for me not work
::: error: (2052) The current license does not permit the selected optimization level and other levels are not permitted by the NOFALLBACK option
(908) exit status = 1

[tumbleweed]

I haven't tried to install it yet, but there may be something different about the new XC '09' versions.

For XC16-

Release Notes for MPLAB XC16 C Compiler
v1.39
Mar 22 2019

This release of the Microchip MPLAB XC16 C compiler is a functional safety compiler based on MPLAB XC16 v1.36B. This compiler requires a functional safety license in order to operate. Once activated, all optimisation levels and compiler features are available.

Maybe they use a different licensing scheme...

[Top]

Maybe they use a different licensing scheme...

Not a different scheme but there are some changes.

[tumbleweed]

FYI - from one of the XC developers...

Just to confirm what it looks like you already know, the XC8 2.09 is a functional safety compiler. It requires a special license, so at this stage you will not be able to run it. It has not actually been officially released yet; however, it made its way onto the list of compilers offered as update by MPLAB X IDE. That issue is being looked into. There will be special functional safety compilers for XC8/16/32 released later in the year.

[uCApps]

Hello,
xc8 ver. 2.10 was released and currently medicine does not works anymore.
I checked in xclm binary and it is updated in this version.

[Top]

Open a command prompt as admin and run the following commands:

"C:\Program Files (x86)\Microchip\xc8\v2.10\bin\xclm.exe"
"C:\Program Files (x86)\Microchip\xc8\v2.10\pic\bin\xclm.exe"

Report back with results.

[uCApps]

Open a command prompt as admin and run the following commands:

"C:\Program Files (x86)\Microchip\xc8\v2.10\bin\xclm.exe"
"C:\Program Files (x86)\Microchip\xc8\v2.10\pic\bin\xclm.exe"

Report back with results.

Dear Top, thanks for kindness, here it is. Successfully it patched binary,but it doesn't work in MPLAB X.
---
C:\Program Files (x86)\Microchip\xc8\v2.10\pic\bin>xclm.exe
Patched 40 bytes in file ./aspic.exe
Patched 40 bytes in file ./aspic18.exe
Patched 40 bytes in file ./cgpic.exe
Patched 40 bytes in file ./cgpic18.exe
Patched 40 bytes in file ./picc.exe
Patched 40 bytes in file ./picc18.exe
Patched SHA in 6 of 6 files

C:\Program Files (x86)\Microchip\xc8\v2.10\pic\bin>

C:\Program Files (x86)\Microchip\xc8\v2.10\bin>xclm.exe
Nothing to do

C:\Program Files (x86)\Microchip\xc8\v2.10\bin>
---

[Top]

When you say "doesn't work" be more specific, give an example, what exactly is not working?

[uCApps]

When you say "doesn't work" be more specific, give an example, what exactly is not working?

Dear Top,
Sorry for that, I meant optimizations in XC8 ver. 2.10 didn't works in Os, O3 on MPLAB X once,
but it WORKS well now after I deleted cache files.

Many apologizes for my recognization...lots of thanks for nice madecine!

uCApps

[Catcatcat]

How I cure version 2.XX.
First, as usual, I do with the files in the folder C:\Program Files (x86)\Microchip\xc8\v2.10\bin
I get two files xclm.exe (26 KB) and xclm.old (1719KB).
Then copy them to the folder
C:\Program Files (x86)\Microchip\xc8\v2.10\pic\bin
and
C:\Program Files (x86)\Microchip\xc8\v2.10\avr\bin
And then in each of these folders I perform the treatment, it seems so far, everything works.

[Mr. Spock]

"And then in each of these folders I perform the treatment"

Hi
Do you mean running again xclm.exe ?
Best regards

[Catcatcat]

"And then in each of these folders I perform the treatment"

Hi
Do you mean running again xclm.exe ?
Best regards

Yes.

[pickit2]

I had a tough time patching xc8
I had to move the files xclm.exe and xclm.old  up a level to
c:\Program Files\microchip\xc8\v2.10

then it worked.

[engiadina]

Hi,

I'm trying to apply the medicine to a Mac with Catalina. Here it does not work, the OS complains about the 32-Bit nature of the medicine. Should be 64-Bit to be able to run. Is there any help available?

Many thanks

engiadina

[pki]

Where can i find the medicine for linux version?

[MarkWalter]

Hi to everyone, i'm using this xclm method since forever and really thanks for it.
I'm really curious about this, anyone can share the source code of the xclm? or maybe just explain the procedure.
I've always been fascinated with those ''softwares'', thanks

[tumbleweed]

xc8 v2.20 was just released.

Part of that package contains a new assembler pic-as.exe (xc8\v2.20\pic-as\bin).
Does anyone know if that program needs to be patched too?

[Catcatcat]

The medicine works, treated according to the method of copying files to bin folders. (V2.20)

[koky]

the new version is 64 bit and the usually medicine work fine

[pickit2]

Hi to everyone, i'm using this xclm method since forever and really thanks for it.
I'm really curious about this, anyone can share the source code of the xclm? or maybe just explain the procedure.
I've always been fascinated with those ''softwares'', thanks

why this post after only two post in forum.

Both your post after being a member here for over 5 years are like this

Quote by you 'Someone can please release the source code of the medicine ?

[tumbleweed]

The medicine works, treated according to the method of copying files to bin folders. (V2.20)

Yes, I know. The medicine patches all the 'old' XC8 files in v2.20 fine.

v2.20 includes a new standalone assembler pic-as.exe which is intended to replace MPASM.
My question is if the new file pic-as.exe needs to be patched as well.

pic-as.exe may just be a front-end for calling the existing aspic.exe/aspic18.exe (which ARE patched by the medicine),
bit I don't know for sure. Hence the question.

[Catcatcat]

Yes, I know. The medicine patches all the 'old' XC8 files in v2.20 fine.

v2.20 includes a new standalone assembler pic-as.exe which is intended to replace MPASM.
My question is if the new file pic-as.exe needs to be patched as well.

pic-as.exe may just be a front-end for calling the existing aspic.exe/aspic18.exe (which ARE patched by the medicine),
bit I don't know for sure. Hence the question.

About 10 years ago I threw the assembler back and I can’t say anything about it, but as far as I remember, assembler has always been free.

[tumbleweed]

I don't think everyone is getting what I'm saying.

Yes, the old MPASM was free. The NEW assembler pic-as.exe is part of XC8 v2.20.

Currently the medicine patches the aspic.exe assembler used in XC8 v2.10:

Code:

Patched 40 bytes in file ./aspic.exe
Patched 40 bytes in file ./aspic18.exe

Now, pic-as.exe is meant as a standalone assembler (I think XC8 still calls on aspic to do its work).

The question, yet again, is a similar patch as was done for aspic.exe needed for pic-as.exe?

[graywolf]

Hi,

I'm trying to apply the medicine to a Mac with Catalina. Here it does not work, the OS complains about the 32-Bit nature of the medicine. Should be 64-Bit to be able to run. Is there any help available?

Many thanks

engiadina

I have been creating my own patcher for Catalina, it has been tested against XC32 v2.40, XC8 v2.20 and works. I will package and do a release in the next few days. 'pickit2' where or how do I get this live?

[Ahmad_k]

I have downloaded the last MLA (Microchip Library v2017) that support PIC18 USB Device also the latest XC8.

All USB samples from MLA compile out of the box without any problem, but non of them are working in Proteus USB simulation. First i thought it was a Proteus problem, i opened usb hid mouse sample provided by proteus and it works, but none of the demo within MLA works. USB analyzer stuck on get device descriptor.

i also tried MikroC simple HID device and it works also in proteus.

The reason i need XC8 and MLA USB stack because it is almost full USB stack and not a light weight stack as provided by MikroC and Proton.

I don't have a real hardware near me to try on real hardware right now.

Please if someone can confirm that USB stacks (XC8 + MLA) (Custom HID sample or mouse sample) is working fine on real hardware or in simulation, if yes then provide the exact version.

Device used : 18F14k50 or 18F45k50