Transition 8.30 to 9.00

Question

Should the application run after the transition or is some kind of refactoring neccessary or usefulel?

Answer 1

Hello,

yes, the migration from version 8.30 to 9.00 is without manual reworking of the project possible. We always take care on compatibility.

In case there are some adaptations necessary by the user or if there are any incompatibilities from one version to another one, we document that explicitely in the Release Notes together with the necessary steps.

In case of version 9.00, there are a lot of changes and improvements - please have a look to the details. In order to use the new features / new widgets, it might be necessary to adapt your project.

Best regards,

Manfred Schweyer.

Comments

Hello,

in another thread (https://ask.embedded-wizard.de/2220/animated-bitmap) you mentioned, that in 9.00 it is possible to locate the pixel data of images in a separated linker section. This is neccessary for me, because the 9.00 version of my application has a larger footprint than the 8.30 version.

The section SectionEwResource is already located in QSPI. Are there any settings within EW to be adapted to increase the amount of resources in the QSPI flash?

---

Hello,

it seem that you put the entire GUI application into the QSPI flash.

Now, if you are using the new feature to locate just the pixel data from resources within the QSPI flash, then the necessary QSPI flash size decreases and the necessary amount of internal flash increases.

The advantage of this new feature is, that you can still keep the application and font metrics within the (faster) internal flash and only the pixel data within the QSPI flash.

In your case, if you want to reduce the consumption of internal flash, I would recommend to keep your approach and locate all objects from generated GUI source code within the QSPI flash.

Does this answer your question?

Best regards,

Manfred.

---

Hello Manfred,

in principle this answers my question: Better stay with 8.30.

But how can I force EW to locate objects in the QSPI flash and not in the internal flash?

Best regards, Roland

---

Hello Roland,

I cannot follow the conclusion to stay on version 8.30 - there is just no need in your case to use this one feature. Apart from that, there are many other improvements...

Anyway, please note, that Embedded Wiard has nothing to do with locating code and constant data into internal or external flash memory! This is always a setting of your linker file. Depending on your toolchain (or makefile) you have the choice to locate the different parts of your application to dedicated address ranges.

Embedded Wizard Studio is a code generating tool - the output is ANSI-C code.

If you want to locate code and data from entire files within the QSPI, you can use the approach that we provided with version 8.30.

Best regards,

Manfred.

---

Hello Manfred,

so I misunderstood your comment.

I will stay with 9.00. Also I found a solution, to move object files to the QSPI.

However, in this configuration my MPU configuration does not work any more.

Best regards, Roland