On 10/3/2024 7:07 PM, yfliu2008 wrote:
- Two kernel mode configs `nsbi` and `knsh` both show used memory growth after
ostest.
I would consider memory leaks in core OS functions to be a major problem.
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
Nice imrovement Lup!
Thank for looking into it
Best regards
Alin
On Thu, 3 Oct 2024, 16:16 Alan C. Assis, wrote:
> Hi Lup,
>
> This is a great improvement! Kudos!!!
>
> BR,
>
> Alan
>
> On Thu, Oct 3, 2024 at 11:05 AM Lee, Lup Yuen wrote:
>
> > Hi All: We're rolling out enhancements to the CI
Hi Lup,
This is a great improvement! Kudos!!!
BR,
Alan
On Thu, Oct 3, 2024 at 11:05 AM Lee, Lup Yuen wrote:
> Hi All: We're rolling out enhancements to the CI Workflow, to skip the
> unnecessary NuttX Builds for PRs. Right now we wait for the CI Builds to
> complete across All Architectures (
Hi All: We're rolling out enhancements to the CI Workflow, to skip the
unnecessary NuttX Builds for PRs. Right now we wait for the CI Builds to
complete across All Architectures (Arm32, Arm64, RISC-V, Xtensa), even
though our PR modifies a Single Architecture. With the enhancements, the CI
Workflow
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
AFAIK the AI bot is used only to help identify things that are missing in
the PR, so it avoids asking users again and again to fill the Summary, etc.
BTW, I don't think simple things like that need Apache or PMC approval.
It is an open-source project after all and contributions are welcome!
But
Hi Mark,
Thank you for letting us know about CodeSecure and CodeSonar static
analysis.
Some years ago I used PVS-Studio (info here:
https://acassis.wordpress.com/2017/07/13/using-pvs-studio-to-find-bugs-in-cc/
), but this kind of software coverage finds tons of false positives.
So, we will spend
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
Hello,
I work for CodeSecure, who builds and sells the CodeSonar static analysis tool
that detects both coding style violations (think MISRA) as well as deep
security vulnerability (think buffer overruns due to tainted data). Over the
past while, we have been running CodeSonar on a couple of op
+1 but I've to check more for nucleo-h745
Results:
arm-none-eabi-gcc -v
Thread model: single
Supported LTO compression algorithms: zlib
gcc version 13.3.1 20240614 (15:13.3.rel1-1)
*nucleo-144:f746-pysim*
-rwxrwxr-x 1 bucher bucher 467588 Oct 3 13:25 nuttx
-rwxrwxr-x 1 bucher bucher 30
+1 for Milk-V Duo S, Ox64, Star64 and PinePhone
= Milk-V Duo S Compiler
+ riscv-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv-none-elf-gcc
COLLECT_LTO_WRAPPER=/Users/luppy/xpack-riscv-none-elf-gcc-13.2.0-2/bin/../libexec/gcc/riscv-none-elf/13.2.0/lto-wrapper
Target: riscv-none-elf
Co
Hi,
I am now the owner of 4 Micron NAND chips and I am at the disposal of
NuttX developers who want to test code to drive and use them.
Tomek: It doesnt change a damn thing.
If LLM are used to make up for contributor laziness that's even worse.
You'll get unreliable slop when the proper thi
Hello all,
Apache NuttX 12.7.0 RC0 has been staged under [1] and it's
time to vote on accepting it for release. Voting will be open for 72hr.
A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
required to pass.
The Apache requirements for approving a release can be found here
16 matches
Mail list logo
