Hi Alan
The function "exit(1)" in my code of the pysimCoder blocks will be
called only if we set "y" to the configuration
CONFIG_NSH_DISABLE_EXIT=y
This configs means, in my opinion, that if exit is disabled, the
function "exit" doesn't exist, but it seem that we have an opposite
behaviour.
I found out the problem, with
CONFIG_NSH_DISABLE_EXIT=y
the exit(1) function in code correctly works otherwise the exit(1) call
leads to:
_assert: Assertion failed panic: at file: armv7-m/arm_hardfault.c:175
task: 0x80002b9
In my opinion it should be the opposite behavior...
Bye
Roberto
On 2024-10-03 17:02:09, Roberto Bucher wrote:
> I developed a python application called "pysimCoder" similar to XCos and
> Simulink, which is able to generate control code for different targets
> (Linux, Linux RT, Raspberry PI, NuttX and others). We have about 175 blocks
> for the different targets
On 2024-10-03 14:16:40, Roberto Bucher wrote:
> _assert: Assertion failed panic: at file: armv7-m/arm_hardfault.c:175 task:
> 0x80002b9
>
> and this is related to the call of the function
>
> exit(1);
>
> in my code, for example if a device is not defined. The call to this exit(1)
> function lea
Thanks to all!
The problem with the network is solved (I've installed ufw for another
project, and the connection with the nuttx target failed!)
I've isolatedthe other problem related to
_assert: Assertion failed panic: at file: armv7-m/arm_hardfault.c:175
task: 0x80002b9
and this is relat
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 wd
at 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
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
On Tue, Oct 1, 2024 at 1:09 PM Tomek CEDRO wrote:
> (..)
> RC is the Release Candidate and is not the official release.. and yes
> WE ARE MISSING THE nuttx-12.6.0 RELEASE TAG ON GITHUB!! :-)
Okay the nuttx-12.6.0 tag is now present, documentation updated, but
it is equivalent to 12.6.0-RC1 from w
Hi
I have some troubles with the 3 boards, with pysimCoder:
GCC version: arm-none-eabi-gcc version 13.3.1 under Debian trixie
*NUCLEO-F746ZG*: generated code works, but network is not reachable (TCP
and UDP). "ping" works, but sending data via LAN not!
*NUCLEO-H745ZI-Q:*
*Code generation:*
On Tue, Oct 1, 2024 at 11:57 AM roberto.bucher.2812
wrote:
> 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.
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_regis
12 matches
Mail list logo
