1.8k views
in System Integration by
Our current project will reach the limit of the available code size soon. Of course, we can optimize the C-code (middleware) of our project - but we are looking for some hints to reduce the resulting code size of our Embedded Wizard GUI project.

1 Answer

0 votes
by

The article Memory Footprint explains all details about the flash memory (ROM) usage and the data memory (RAM) usage. Furthermore, the article contains implementation hints and describes the different configuration macros the can help to optimize the memory footprint.

Especially, the section Optimizing the Flash Memory (ROM) usage describes the different possibilities to reduce the code size.

With version 9.20 a couple of code size optimizations have been done.

With version 9.30 Embedded Wizard was enhanced to create a Code Generation Report. It is an HTML file reporting the amount of flash memory (ROM) for the entire application as it will be needed in the target system. It includes all involved resources (e.g. bitmaps) as well as the logic of the application (the classes and the Chora implementation). 

Ask Embedded Wizard - Archive

Welcome to the Ask Embedded Wizard archive. This community forum served us well for many years, but we've evolved our support approach!

Your resources:

The Embedded Wizard Online Documentation provides comprehensive documentation, tutorials, examples and ready-to-use software packages.

For dedicated assistance, explore our Embedded Wizard Product Support.

You can still browse the valuable discussions from our community history here.

Embedded Wizard Website | Privacy Policy | Imprint

...