XC16 Compilers Discussion

[metal]

XC16 Compilers Discussion Topic

[metal]

XC16 Compilers Discussion Topic

[8bitMCU]

MPLAB xc16 v1.10 has been release

http://www.microchip.com/mplabxc16windows

[respected]

I tried it. But I don't compile

[metal]

really, how is that, explain!?

[respected]

compiler messages;

elf-cpp.exe: PIC24F08KA102.gld: No such file or directory
elf-cpp.exe: warning: '-x c' after last input file has no effect

[Gallymimu]

Sounds like a question for the microchip forums

You've got something misconfigured if that is in fact a supported processor in this version of the compiler.  The gld file, unless you explicitly included it should be automatically loaded from the various include paths.

[respected]

I changed PIC****.gld file P*****.gld.   I compiled .  Thanks.

[marcodassi]

XC16 1.11 is out!

testing medicine...   medicine still seems to work 

[Parmin]

Question.

Anyone have a library for HD44780 for the XC16 and XC32?

After playing with XC16 for a week I seem to start thinking that it is quite rotten.

[Catcatcat]

Here is my production Library for LCD indicators on the driver HD44780 or KS0066U

[Catcatcat]

new version MPLAB® XC16 Compiler v1.20

[marcodassi]

XC16 1.21 is out!
(it's still listed as 1.20, but just click on the link and download!)

[Catcatcat]

A new version
MPLAB® XC16 Compiler v1.22

[Catcatcat]

updated compiler

MPLAB® XC16 Compiler v1.23

[Binary1955]

updated compiler


MPLAB® XC16 Compiler v1.24

don't forget the part support

XC16 v1.24 part support

Part-support updates can be applied to any compiler version, but some functionality may require a later compiler version.

medicine still seems to work   

[mitsos]

hi

v1.26 released

http://www.microchip.com/mplabxc16windows/

regards
mitsos

[Catcatcat]

updated compiler

MPLAB® XC16 Compiler v1.30

testing, optimization level
0


1


2


s


3


medicine works!

[Catcatcat]

A new version

MPLAB® XC16 Compiler v1.36

[Catcatcat]

Comparing the latest versions in code size optimization mode:

[Catcatcat]

MPLAB XC16 Compiler v1.40
checked, it works
But, the truth, the header files of some microcontrollers have different register names, for example, for PIC24FJ128GA204 in 1.36 there is a register REFOTRIMHL in version 1.40 it is called a register REFOTRIMH. This is what I have noticed so far.

[uCApps]

MPLAB XC16 Compiler v1.41(Bug-fix release?)
Medicine works like a charm;)

[Manuel]

MPLAB XC16 Compiler v1.50 (porting to x64 version)

After Checking TOP's x86 solution I confirm it's working . Actually no need of x64 solution.

(PS: I did a mistake, I did not consider that different compiler versions can have also different DEFINE)

SORRY MY FAULT !!!!

X!

Release:  v1.50

    This release is a 64bit only release. All executables shipped with release are 64bit executables. This affects MacOS, Linux and Windows installers.

    Updated MacOS release is Catalina compatible. Catalina has dropped 32bit executable support. This release of MPLAB XC16 is now a 64bit package.

    New linker options that add section attributes to all code, data or PSV (.const) type sections. Additional information is available in the provided User's Guide (DS50002106E).

    Added new functionality in compiler that helps user program inactive slave section of PRAM on dual core devices that have this feature. Users can use the function _program_inactive_slave(slave_number, verify, image); to program the inactive slave panel with the image. The function performs similar to _program_slave() but works only on the inactive panel.

    Added a ported version of objcopy to the release. XC16 version is called xc16-objcopy. This version of objcopy only recognizes XC16 object code. Any other type of object code is not recognized by this objcopy.

[Top]

MPLAB XC16 Compiler v1.50 (porting to x64 version)

Medicine does not work anymore I would say.

I will recompile the fix for 64-bit but Windows should still be OK. Can you test it?

[mars01]

I will recompile the fix for 64-bit but Windows should still be OK. Can you test it?

Hi Top,
It looks like it works. I applied the patch and it reported patch completed.  I made a bogus project, compiled it with Os optimizations and it has done it without complaints.

[Catcatcat]

MPLAB XC16 Compiler v1.50

This universal link will always show the latest version.

[Catcatcat]

MPLAB XC16 Compiler v1.61

Everything works well.

This universal link will always show the latest version.

[Catcatcat]

MPLAB XC16 Compiler v1.70

Everything works well.

[extremgear]

hello,

it seems to be very hard to make the medicine work on mac os big sur , i guess i'm not used to this new os and new terminal, i'll dig a little bit more and see.

[patchjack]

Moderator, please share the patch file here, thank you!

[Manuel]

Did you try TOR-browser ?

X!

[pickit2]

Moderator, please share the patch file here, thank you!

Site Rules state All Software files are to be on a File Host Site not here. unless you want Sonsivri to be taken down.

[patchjack]

Site Rules state All Software files are to be on a File Host Site not here. unless you want Sonsivri to be taken down.

Excuse me, what is the file host site address of this xc16 cracked file?

[Manuel]

MPLAB XC16 Compiler v2.10

...Seems all ok...

X!

[eleks]

I apologize in advance if my question is inappropriate here.
I'm trying to write code in xc16 assembler. I don't understand how to place constants in program memory. In theory, you just need to place data in the program area (after the .text directive). But if I do this:

Code:

.text
...
COEFF_A: .hword  0x4000,0x8F5B,0x4BB5,0xEE34
COEFF_B: .hword  0x2511,0x6F33,0x6F33,0x2511
.end

Then the compiler perceives the labels COEFF_A and COEFF_B as invalid assembler instructions.
If I do this:

Code:

.text
...
.data
COEFF_A: .hword  0x4000,0x8F5B,0x4BB5,0xEE34
COEFF_B: .hword  0x2511,0x6F33,0x6F33,0x2511
.end

The compiler places constants in the data area.  
Tell me what I'm doing wrong?

Posted on: May 07, 2025, 09:59:15 09:59 - Automerged
If I do this:

Code:

.text
...
.section .const
COEFF_A: .hword  0x4000,0x8F5B,0x4BB5,0xEE34
COEFF_B: .hword  0x2511,0x6F33,0x6F33,0x2511
.end

The data seems to appear in the program memory area. But in my opinion, this is not quite the correct syntax.

[eleks]

This will be right:

Code:

.text
...
.section coeff,psv
COEFF_A: .hword  0x4000,0x8F5B,0x4BB5,0xEE34
COEFF_B: .hword  0x2511,0x6F33,0x6F33,0x2511
.end