nRF53 and Zephyr: optimization level

RE: nRF53 and Zephyr: optimization level

Susheel Nuguru — Thu, 04 Nov 2021 07:14:47 GMT

no problem, good luck with your development.

RE: nRF53 and Zephyr: optimization level

Riccardo Gaiati — Wed, 03 Nov 2021 12:48:28 GMT

Hi,

thanks so much for the info.

Kind regards

Riccardo

RE: nRF53 and Zephyr: optimization level

Susheel Nuguru — Tue, 02 Nov 2021 12:45:44 GMT

unfortunately the optimizations for the compiler are global levelled.

But you can enhance the debug experience a bit if you enable the debug option of the individual modules

RE: nRF53 and Zephyr: optimization level

Riccardo Gaiati — Tue, 02 Nov 2021 12:08:31 GMT

Hi again,

in any case i would like to know if there is a proper way to change the optimization between the application and the rest of the code.

Thanks !

RE: nRF53 and Zephyr: optimization level

Riccardo Gaiati — Tue, 02 Nov 2021 12:07:06 GMT

Hi Susheel,

thanks for the reply.

The reason i would like to compile with no optimization is to have a better debug experience. And i am mainly interested to debug our application.

Yesterday I tried to increase the Idle stack size and the problem seems to disappear.

Thanks again for the support !

Kind regards

Riccardo

RE: nRF53 and Zephyr: optimization level

Susheel Nuguru — Tue, 02 Nov 2021 08:42:43 GMT

Hi,

[quote user=""]If i change it to no optimization i am having stack overflow.[/quote]

It is a bit unclear to me why you do not want to have full optimizations on the whole project and only on the application?

[quote user=""]I have increased the main stack size up to 4 KB, but the problem is still present.[/quote][quote user=""]As far as i could get with my tests, the stack overflow happens inside the function pm_system_suspend declared in power.c[/quote]

It is possible that this is the issue with the idle thread stack size. Since most power related things (when enabled) are done in the idle thread, you need to keep an eye on the CONFIG_IDLE_STACK_SIZE as well.