You're right, if the problem is only related to stack.I checked some weeks ago
the same blockdiagram with the previous version of arm-none-eabi-gcc without
problems, including network, and the officicial last RC1 NuttX version. I'll
retry this version with the new compiler and see what happens. Otherwise I'll
try to downgrade the compiler...ThanksRobertoInviato dal mio Galaxy
-------- Messaggio originale --------Da: michal.lyszc...@bofc.pl Data: 01/10/24
11:41 (GMT+01:00) A: dev@nuttx.apache.org Oggetto: Re: Problems with STM32F7
and STM32H7 boards On 2024-10-01 10:52:18, Roberto Bucher wrote:> Thanks
Michal> > changing the arm-gcc version can probably change the size of the
generated> code.No, stack size is per thread, and has nothing to do with code
size.Stack size refers to automatic storage variables like int main(void) {
int a; char c[32]; }This will take about 36 bytes of stack memory. Each
nested function also usessome stack space for arguments, return pointers etc.I
don't know how you generate your app, if it's automatic from
kconfig+makefilethen stacksize is determined by STACKSIZE makefile variable,
which is usuallyset by some Kconfig setting with similar name.--
.-----------------.-------------------.----------------------.-----------------.|
Michal Lyszczek | Embedded C, Linux | Company Address | .-. opensource
|| +48 727 564 419 | Software Engineer | Akacjowa 10a; 55-330 | oo| supporter
|| https://bofc.pl `----.--------------: Brzezinka Sredzka PL | /`'\ &
|| GPG FF1EBFE7E3A974B1 | Bits of Code | NIP: 813 349 58 78 |(\_;/) programer
|`----------------------^--------------^----------------------^-----------------'
