Hello matrix team,
is it possible to look at this situation what happens there?
May be, that it was simple bug to repair.
Jorg
Problem to build a project from Version8 [solved]
-
Jorg_Guldner
- Posts: 58
- http://meble-kuchenne.info.pl
- Joined: Wed Dec 23, 2020 9:55 am
- Been thanked: 4 times
-
medelec35
- Matrix Staff
- Posts: 2190
- Joined: Wed Dec 02, 2020 11:07 pm
- Has thanked: 664 times
- Been thanked: 743 times
Re: Problem to build a project from Version8 [not solved]
Hi Jorg.
If 2 x UARTS stop your project from compiling you could consider UART Software Timer.
I have found it to work great with both RX and TX
If 2 x UARTS stop your project from compiling you could consider UART Software Timer.
I have found it to work great with both RX and TX
Tat is because as soon as a component is added to the 2D or 3D panel, space will be automatically allocated for it.Jorg_Guldner wrote: ↑Thu Oct 23, 2025 5:37 pmIf both uarts are disabled in the program, the compiler stops likewise?
Martin
-
Jorg_Guldner
- Posts: 58
- Joined: Wed Dec 23, 2020 9:55 am
- Been thanked: 4 times
Re: Problem to build a project from Version8 [solved]
Hello matrix team,
I get it now compiling:
Boot segment write protect & Boot segment protect where enabled. This setup causes the memory problems. Are both disabled, then it compiles without errors.
In FC8 are both enabled if you choose the chip. This old compiler have no problems with this setup. For the newer compiler I found in a forum:
"Again, V2.00 has a problem in CODE GENERATION, not optimization.
the microchip 16bit architecture can deference a pointer with offset in a single instruction.
Pointer with offset can be a member of a pointer to struct, or when you pass an array to a function, because you pass the address of the first element and the compiler can't use the literal address."
"XC16 2.0 doesn't work as well as previous versions, internal changes added unnecessary bloat (the compiler forgot that it can do indirect addressing with an offset, and instead calculates the actual address every time. all pointers, including arrays, are affected)"
Jorg
I get it now compiling:
Boot segment write protect & Boot segment protect where enabled. This setup causes the memory problems. Are both disabled, then it compiles without errors.
In FC8 are both enabled if you choose the chip. This old compiler have no problems with this setup. For the newer compiler I found in a forum:
"Again, V2.00 has a problem in CODE GENERATION, not optimization.
the microchip 16bit architecture can deference a pointer with offset in a single instruction.
Pointer with offset can be a member of a pointer to struct, or when you pass an array to a function, because you pass the address of the first element and the compiler can't use the literal address."
"XC16 2.0 doesn't work as well as previous versions, internal changes added unnecessary bloat (the compiler forgot that it can do indirect addressing with an offset, and instead calculates the actual address every time. all pointers, including arrays, are affected)"
Jorg
Last edited by Jorg_Guldner on Wed Nov 12, 2025 4:54 pm, edited 2 times in total.
-
Steve-Matrix
- Matrix Staff
- Posts: 1638
- Joined: Sat Dec 05, 2020 10:32 am
- Has thanked: 227 times
- Been thanked: 387 times
Re: Problem to build a project from Version8 [not solved]
That could be the issue. The free version of the underlying XC16 compiler may not be optimised and be adding unnecessary bloat to the HEX file.
I think some of our users have used the professional version of XC16 with Flowcode with success, but I have never tried it myself.
I think some of our users have used the professional version of XC16 with Flowcode with success, but I have never tried it myself.