I made just the opposite experiences with my projects. When comparing Creator 2.2 usage with 3.0 usage they frequently needed less codespace. Can you upload an example project for 2.2 to let us have a look at?
My experience is > 10% , an astioning 300% , from 55kb , with Creator 2.2 , without any touch, at 142Kb with creator 3.0
.Is interesting lokk why ?.
A upload my project.
Best at all
Your project did not upload, use IE or Firefox, Chrome has issues
The problem was zip blocked by my provider, i create a new zip and rar version.
What i discovery if i take of any bootloader, the code go to 33Kb.
If i leave the bootloader, in creator 2 i have 55Kb, in creator 3 now increase more to astoning 176kb.
I allegate the project.
Best at all
I compiled in 3.0 and got -
Flash used: 33768 of 262144 bytes (12.9 %).
SRAM used: 23645 of 65536 bytes (36.1 %).
Is the code bigger as cocoritococorito said??Asking cause I could not download the project
w/o Bootloader, which was his posted project, I got same. Unfortunately
he did not post final conclusion as to why BL took on a much larger
FLASH footprint. I suspect the BL code had a change assocated with
3.0 that did not get implemented.
The release notes for 3.0 specifically point to need to update that
component. That could have been cause of FLASH bloat.
There is also this in release notes -
New RAM Usage Calculation
Prior to the 3.0 release, the reporting of SRAM usage at the end of a build with the GNU Compiler
Toolchain did not correctly report the stack and heap settings in the System DWR file. This has been
corrected and PSoC Creator is now properly reporting the RAM usage (note that the actual RAM usage
has not changed, just the reporting in the Output Window). You can modify the Stack and Heap Size
values in the System DWR.