Thanks Michal
changing the arm-gcc version can probably change the size of the
generated code.
I'll check it
Bye
Roberto
On 10/1/24 10:36 AM, michal.lyszc...@bofc.pl wrote:
On 2024-10-01 09:38:56, Roberto Bucher wrote:
By launching "main" I have this error:
nsh> main
ERROR: Failed to wdump_assert_info: Current Version: NuttX 12.6.0-RC1
d4968905c5 Oct 1 2024 08:53:59 arm
dump_assert_info: Assertion failed panic: at file: :0 task: 0x8000361
up_dump_register: R0: 00000000 R1: 38005bf0 R2: 00001810 R3: 00001800
up_dump_register: R4: 080002e9 R5: 00000000 R6: 00000000 FP: 00000000
up_dump_register: R8: 00000000 SB: 00000000 SL: 00000000 R11: 00000000
up_dump_register: IP: 00000000 SP: 38006318 LR: 08002807 PC: 0800a692
up_dump_register: xPSR: 21000000 PRIMASK: 00000000 CONTROL: 00000000
up_dump_register: EXC_RETURN: ffffffe9
dump_stack: User Stack:
dump_stack: base: 0x38005cc0
dump_stack: size: 00002024
dump_stack: sp: 0x38006318
Any ideas?
Is this "main" your own app? First thing I would check is stack size for
that thread. Also enable stack colorization, stack canaries and stack usage
statistics. Overflowing stack on embedded is number 1 in amount of errors
I've seen during early development.
Sharing your main code might also be helpful in debuging it.
