Re: Developing the NuttX Standard Board

uld propose that we create the boards stackable with distributed power > and data lines to facilitate the testing farm application > > Best regards > Alin > > > On Mon, Sep 8, 2025 at 3:01 PM Alan C. Assis wrote: > > > Hi Tomek, > > > > Thank you for attendin

Re: git going rust

> > > Brian Kernighan said the same quite recently, at VCE > > https://thenewstack.io/unix-co-creator-brian-kernighan-on-rust-distros-and-nixos/ > > Alan, do you have the link to Ken's presentation? From what I find, he is > usually placed on the "supporting Rust" side due to his famous "invisible"

Re: Developing the NuttX Standard Board

e like > 5x for low cost and then solder things up at home? Maybe ordering > already soldered boards can be cheap too. It would be good to provide > cos simulation from various places when things are ready :-) > > Thanks again! :-) > Tomek > > > > On Sun, Sep 7, 2025 at

Re: Developing the NuttX Standard Board

will be useful. Thinner ENIG PCBs gave me some problems in a SFP module > context. > > With that in mind, the thicker HASL coating may play nice with 0.8mm > PCBs :-) > > > Sebastien > > > On 08/09/2025 09:39, Sebastien Lorquet wrote: > > > > On 07/09/2025 22:0

Re: Developing the NuttX Standard Board

BR, Alan On Sun, Sep 7, 2025 at 9:14 AM Alan C. Assis wrote: > Hi Everyone, > > For those who will participate in the design phase, please join in the > Jitsi, we will start in 45min: > > https://meet.jit.si/Developing_NuttX_Standard_Board > > BR, > > Alan > >

Fwd: Call for Participation: Embedded & IoT micro-conference at Linux Plumbers 2025

Could be interesting for NuttX speakers to participate: -- Forwarded message -- From: *Stefan Schmidt* Date: Friday, September 5, 2025 Subject: Call for Participation: Embedded & IoT micro-conference at Linux Plumbers 2025 To: linux-arm-ker...@lists.infradead.org, linux-embed...@v

Re: git going rust

Hahaha, always clever comments !!! Miss you Ken! I hope you are doing well !!! BR, Alan On Sat, Sep 6, 2025 at 10:51 AM Kenneth Pettit wrote: > On 9/6/25 6:41 AM, Alan C. Assis wrote: > > I don't know if Rust will end up replacing C, but I think we will need to > > le

Re: Developing the NuttX Standard Board

Hi Everyone, For those who will participate in the design phase, please join in the Jitsi, we will start in 45min: https://meet.jit.si/Developing_NuttX_Standard_Board BR, Alan On Sat, Sep 6, 2025 at 11:57 AM Alan C. Assis wrote: > Hi Everyone, > > We will have tomorrow morning (

Developing the NuttX Standard Board

Hi Everyone, We will have tomorrow morning (afternoon/evening for merians A to M) our first meeting about the NuttX Standard Board: https://www.youtube.com/live/keZAZ8GiYzI New to this subject? Ref: https://github.com/NuttX/nuttx_hardware/blob/main/Documentation/standard/index.rst Please join u

Re: git going rust

Hi Štěpán Pressl, Because Nathan is a subversion contributor/developer, hehehe :-) Few days ago I saw a Ken Thompson presentation where someone asked him if Rust will replace C. He said he tried to develop a program in Rust and had difficulties to get it working, then sometime later with it trie

Re: RPI 4B Roadmap

Hi Matteo, I think for WiFi/BLE the driver will be straightforward after we get SDIO working because RPi uses the same Broadcom chip (BCM43455) that is already supported on NuttX. Fun fact is that WiFi driver was created by Cypress after they bought the Broadcom WiFi IoT division ( https://invest

Re: RPI 4B Roadmap

Hi Matteo, I think it is a good idea! I got a RPI 4B a few days ago to use as a server for BOOTP/TFTP and haven't had the chance to test NuttX on this board yet, but I'm looking forward to it. I saw you already added many drivers (gpio, serial, i2c, spi, ...) and some still missing: pwm, emmc/sd,

Re: OPEN Alliance 10BASE-T1x Driver PR strategy

Nice work Michal! I think these modifications are important to add support to other chips. This ADIN1110 module (10Base-T1L) from Sparkfun is a good candidate: https://www.sparkfun.com/sparkfun-micromod-single-pair-ethernet-function-board-adin1110.html BR, Alan On Mon, Aug 25, 2025 at 3:59 AM

[OT] NIST Lightweight Crypto Standard

This could be interesting to be included in the NuttX codebase: https://www.nist.gov/news-events/news/2025/08/nist-finalizes-lightweight-cryptography-standard-protect-small-devices BR, Alan

Re: Follows the Conventional Commits //was: Avoid including "[BREAKING]" in the commit title

M Tomek CEDRO wrote: > The real problem here is that breaking changes were passed unmarked :-( > > We can change marking no problem, but we need some sort of mark both > in git commit topic and PR title, do you agree Alan? > > Tomek > > On Sun, Aug 10, 2025 at 3:50 PM Alan C. A

Re: Follows the Conventional Commits //was: Avoid including "[BREAKING]" in the commit title

he conventional commits! BR, Alan On Sat, Aug 9, 2025 at 6:45 PM Tomek CEDRO wrote: > On Sat, Aug 9, 2025 at 11:10 PM Tomek CEDRO wrote: > > > > On Sat, Aug 9, 2025 at 9:47 PM Alan C. Assis wrote: > > > > > > Hi Everyone, > > > > > > I'm

Re: Follows the Conventional Commits //was: Avoid including "[BREAKING]" in the commit title

It was not an email sequence, just a reference to our discussion about it here: https://github.com/apache/nuttx/pull/16793 On Sat, Aug 9, 2025 at 6:28 PM Tomek CEDRO wrote: > Btw "/was: Avoid including "[BREAKING]" in the commit title" where was it? > > -- > CeDeROM, SQ7MHZ, http://www.tomek.ced

Re: Follows the Conventional Commits //was: Avoid including "[BREAKING]" in the commit title

Hi Michal, On Sat, Aug 9, 2025 at 5:08 PM Michał Łyszczek wrote: > On 2025-08-09 16:47:01, Alan C. Assis wrote: > > * It passes a wrong message, as something very negative (not all > > breaking are bad, or shouldn't be) > > * Someone reading our git history could get

Follows the Conventional Commits //was: Avoid including "[BREAKING]" in the commit title

Hi Everyone, I'm proposing to modify the item 1.13.9 from our CONTRIBUTING.md to avoid including the prefix "[BREAKING]" in the commit title for the following reasons: * It passes a wrong message, as something very negative (not all breaking are bad, or shouldn't be) * Someone reading our git his

Re: Porting renesas DA1470X - stuck

Hi Luca, As Nathan suggested you can start looking at the stack side, before trying other root causes. BTW, what development board or device are you using (i.e. MiBand 7) ? I didn't find a low cost DA1470x board at Aliexpress, but I found some DA145xx boards, i.e.: https://aliexpress.com/i/1005

Re: Making external libraries available during "make export"

Hi Stefan, AFAIK NuttX doesn't have support to export apps side libraries. Actually it should be nice to have "real" support for libraries on apps/ Makefiles (we could use the approach that Google used originally on Android Makefiles) since NuttX supports ELF loading for executable and for librar

Re: Feedback on C++/CMake Guide – Outdated Folder Structure and Build Issues

Hi Ali, Actually include/libcxx never was removed because it never existed there, actually it is installed when you build the llvm libcxx! Please take a look at libs/libxx/libcxx/Make.defs: $(TOPDIR)/include/libcxx: libcxx/libcxx $(Q) $(DIRLINK) $(CURDIR)/$https://github.com/apache/nuttx

Re: Integrating NuttX to existing C++23 multiplatform application

in to avoid this issue? > Best regards, > Bartek > > > Wiadomość napisana przez Alan C. Assis w dniu 25 > lip 2025, o godz. 16:57: > > > > Hi Bart, > > > > You cannot replace NuttX libc with another external libc because the > kernel > > is tightly cou

Re: Integrating NuttX to existing C++23 multiplatform application

Hi Bart, You cannot replace NuttX libc with another external libc because the kernel is tightly coupled to it. Some functions could work fine, but others will create issues. In the past all kernel libc used the same name as these libc functions for applications, not when a function is kernel spec

Re: New type of input idea: an action button

8:13 PM Tomek CEDRO wrote: > Very cool thank you Alan :-) > > On Sat, Jul 12, 2025 at 12:57 AM Alan C. Assis wrote: > > > > Hi Tomek, > > > > I agree with you, but in this first "incarnation" it will support only > two > > actions, but people

Re: New type of input idea: an action button

more actions :-) > > It would be great if the driver could return event code or have return > codes configurable (build time?) on selected actions. That would make > things really versatile :-) > > Thanks :-) > Tomek > > > On Fri, Jul 11, 2025 at 11:26 PM Alan C. Assis

Re: New type of input idea: an action button

thought initially. BR, Alan On Wed, Jul 9, 2025 at 10:16 AM Alan C. Assis wrote: > Hi Everyone, > > Some years ago a customer asked me to develop a project with NuttX for > this board that used a small OLED display and a single button. > That button should be used to navigate in the

Re: New type of input idea: an action button

ed in the GPIO system? > > There are gpio interrupts iirc. these could be used to trigger a signal. > > If a system does not have gpio interrupts, polling can do the same trick. > > Just my two cents! > > Sebastien > > > On 09/07/2025 15:16, Alan C. Assis wrote:

Re: New type of input idea: an action button

bout "Single Button Actions" or similar? Singe Button > tells only one button is used to perform various Actions. > > Thanks :-) > Tomek > > > On Wed, Jul 9, 2025 at 3:17 PM Alan C. Assis wrote: > > > > Hi Everyone, > > > > Some years ago a custome

New type of input idea: an action button

Hi Everyone, Some years ago a customer asked me to develop a project with NuttX for this board that used a small OLED display and a single button. That button should be used to navigate in the menu, as a side note: initially he suggested: quick press and release will work as a ENTER and long press

Re: RFC: do not copy const variables to RAM in AVR

Nice work KR and great Documentation! Kudos BTW, I added a comment about using AVR_BOARD_HAS_FLMAP vs ARCH_HAVE_FLMAP. BR, Alan On Mon, Jul 7, 2025 at 7:23 AM wrote: > Hello, > > I would like to submit patches which change handling of const variables > in AVR architecture, DA/DB family. > > A

Re: [VOTE] Apache NuttX 12.10.0 RC0 release

+1 STM32F103-Minimum: Compiler: $ arm-none-eabi-gcc -v ... Thread model: single Supported LTO compression algorithms: zlib gcc version 13.2.1 20231009 (15:13.2.rel1-2) Compilation: $ ./tools/configure.sh stm32f103-minimum:nsh $ make -j Size: $ arm-none-eabi-size nuttx text databssd

Re: [VOTE] Apache NuttX 12.10.0 RC0 release

Hi KR, In order to register this information for future reference (for comparison about bloat size, compiler error, etc), could you please include: Compiler version (i.e. "$ avr-gcc -v") NuttX size (ie. "$ avr-size nuttx") Free memory in the nuttshell ("nsh> free") BR, Alan On Thu, Jul 3, 2

Re: dup2() uses FD already allocated to NET skt

ughly perhaps. It was an change to multiple files. > > nuttx-apps issue: https://github.com/apache/nuttx-apps/issues/3111 > > original PR: https://github.com/apache/nuttx-apps/pull/2595 > > Simply reverting that change fixes it. The only thing needed. > > On 01/07/2025 19:00, Alan

Re: dup2() uses FD already allocated to NET skt

sty wrote: > But that's the point - thttp *does* call exec() so the open socket file > descriptor gets closed when it is still needed by the exec'd application. > > If there's another way of doing this I'm listening! > > On 01/07/2025 16:13, Alan C. Assis wrote

Re: dup2() uses FD already allocated to NET skt

t is now opened > > like this and I assume CLOEXEC will mess up the operation of the > > executed CGI app (will investigate on Monday; not sure what socket > > mode it needs to be): > > > > hc->conn_fd = accept4(listen_fd, (struct sockaddr *)&sa, &sz, > &

Re: NuttX for a critical system

Hi Matteo, thanks for sharing these results here! That is really fantastic! I'm looking forward to seeing it rising in the sky! Kudos for you and your team!!! BR, Alan On Mon, Jun 30, 2025 at 2:21 PM Matteo Golin wrote: > Wanted to share some footage of Carleton University InSpace's successf

Re: dup2() uses FD already allocated to NET skt

Hi Tim, Yes, I think send() is the preferred form to work with sockets because you can have fine control, i.e. passing flags at forth argument (MSG_DONTWAIT, etc). If you suspect that the bug was caused by some recent modification, try to find a supported board that was used to test thttpd in the

Re: CTU OTREES theses, more related to NuttX and RISC-V Was: book: RISC-V System-On-Chip Design. [resent]

Hi Nathan, I think this is a good idea! We need some Who's using NuttX and a Testimonial area. I posted about the 10Base-T1S/T1L project at Linkedin: https://www.linkedin.com/feed/update/urn:li:activity:7342911868623056897/ BR, Alan On Mon, Jun 23, 2025 at 11:00 AM Nathan Hartman wrote: > S

Re: X11 vs Wayland: KiCAD story.

Yes, I think many Linux Distros will keep X11 support for many years, but then there is another issue: companies will follow the "mainstream" distros and will develop tools for Wayland. This will keep this old-school distros out of the commercial game (pun intended), this is not a big issue if you

X11 vs Wayland: KiCAD story.

Hi Tomek, Xorg also is getting forked, BTW a nice article: https://www.dedoimedo.com/computers/xlibre.html I truly believe that the idea of Wayland created by Kristian Høgsberg was to fix many issues existing in X11. But of course, just like PulseAudio and Systemd from Lennart Poettering, this p

Re: Inquiry About Hypothetical Pointer‐Validation in NuttX Protect Mode

Dear MacTavish, I'm redirecting your question to nuttx dev mailing list, that mailing you used is for PMC usage purpose: Dear NuttX Maintainers, I hope you’re doing well. I’m reaching out to gather your perspective on a hypothetical scenario concerning pointer‐validation in NuttX’s protect mode.

Re: [OT] NuttX Standard Board

> > Need to fill your list with my boards and start testing. It's in the > backlog for too long. > > Simon > > -- > Hard- and Softwaredevelopment Consultant > > Geschäftsführung: Simon Filgis > USt-IdNr.: DE305343278 > ISO9001:2015 <https://activities.ingeni

Re: [OT] NuttX Standard Board

pay > expensive licensing costs for a commercial electronics design software. > > Thanks to everyone for your efforts! > > Nathan > > On Tue, Jun 10, 2025 at 1:51 PM Alan C. Assis wrote: > > > Hi Tomek, > > > > Thank you for those nice suggestions. > >

Re: [OT] NuttX Standard Board

urce electronics design > > package. (The only one I am familiar with is KiCad [1].) By using > free/open > > source software, anyone will be able to participate without having to pay > > expensive licensing costs for a commercial electronics design software. > > > >

Re: [OT] NuttX Standard Board

e. you want to attach arduino shield from top to female connector > below, but also want to solder additional pins to then stick the board > to breadboard below). I know this seems trivial but when you have > different boards to physically manage sometimes its a problem :-) > > Have

Re: [OT] NuttX Standard Board

cus/boards and so improve coherence? :-) > > Thanks :-) > Tomek > > > > > On Mon, Jun 9, 2025 at 10:43 PM Alan C. Assis wrote: > > > > Hi Everyone, > > > > To implement the item 11 of the actions to improve NuttX: > > https://github.com/apach

[OT] NuttX Standard Board

Hi Everyone, To implement the item 11 of the actions to improve NuttX: https://github.com/apache/nuttx/issues/16278 I requested ChatGPT to list the most common signals/interfaces existent on NuttX: https://chatgpt.com/share/6841d483-5400-8012-ada6-b962d215f410 So I created a project to Document a

Re: STM32F479NGH6 + Ethernet

Hi Simon, I used DP83848C about 10 years ago and it was really easy to use on NuttX ("just works"). Then about 3 years ago I used LAN8740AI with STM32H743 and it also worked, but it required some tweaks to configure the right PHY registers. BTW, you are not limited only to those two options we ci

Re: book: RISC-V System-On-Chip Design.

Really cool!!! Thanks Pavel Pisa for helping to spread NuttX! Please post the port link here when it become public. BR, Alan On Thursday, June 5, 2025, Tomek CEDRO wrote: > On Thu, Jun 5, 2025 at 9:55 PM Tomek CEDRO wrote: > > Very interesting book upcoming soon on RISC-V :-) > > > > https:/

Re: Sv: RFC: fix race conditions in drivers/serial/serial.c

Hi Miguel, Which kind of modification are you looking for? RS-485 is already supported: https://embeddedrelated.com/showarticle/1715.php BR, Alan On Mon, Jun 2, 2025 at 3:52 PM MIGUEL ALEXANDRE WISINTAINER < tcpipc...@hotmail.com> wrote: > should be good change too this driver to enable the R

Re: Path to [MAX_MQUEUE_PATH] not found

regards, > > Am Mo., 2. Juni 2025 um 17:44 Uhr schrieb Alan C. Assis >: > > > Hi Oussama, > > > > Could you please tell us which board and profile you are using? > > > > Although mqueue.h is in the local directory the root directory (fs/) > should > >

Re: Path to [MAX_MQUEUE_PATH] not found

Hi Oussama, Could you please tell us which board and profile you are using? Although mqueue.h is in the local directory the root directory (fs/) should be in the path, then the file should be found. Note that there is a "notify/notify.h" that follows the same logic (it is at fs/). BR, Alan On

Re: NuttX Logo for rocket/PCBs

You are welcome Matteo, Looking at it with more critical thinking I saw it needs some improvements in the area simulating the gray color, see attached image. BR, Alan On Thu, May 29, 2025 at 9:46 AM Alan C. Assis wrote: > Hi Matteo, > > I have this attached monocolor version that

Re: NuttX Logo for rocket/PCBs

Hi Matteo, I have this attached monocolor version that I use on PCBs, I will send you the SVG version as well, since here that file extension will be blocked. BR, Alan On Wed, May 28, 2025 at 11:20 PM Matteo Golin wrote: > Hello everyone, > > CU InSpace would like to feature the NuttX logo am

Re: Comment for AVR GitHub issue 16444 and PR 16443

Thank you KR, I posted your message in that issue for reference. I have a BK-AVR128 board: https://aliexpress.com/item/1005006234334573.html and will test NuttX on it to confirm. If everything is working as expected I will submit the board support to the mainline. BR, Alan On Tue, May 27, 202

Re: NuttX RTOS entirely in CPU Cache

possible, faster than L2, and a lot > faster than DRAM/SRAM, that is faster than any storage drive :-) Just > a curiosity :-) > Tomek > > On Wed, May 21, 2025 at 10:34 PM Alan C. Assis wrote: > > > > Hi Tomek, > > > > Yes, it is possible, coreboot (Linux

Re: NuttX RTOS entirely in CPU Cache

Hi Tomek, Yes, it is possible, coreboot (LinuxBIOS) did it more than 20 years ago: https://web.archive.org/web/20200530213938/https://www.coreboot.org/images/6/6c/LBCar.pdf But since the computer normally will have DDR memory in the board, there is not much motivation to do it for NuttX. BR, Al

Re: RFC - AVR fixes and support for AVR DA/DB family

Hi KR, Everything is fine. I opened that PR with your modifications, but later Alin included your new patches in the original PR that he opened with your previous patches. BR, Alan On Wednesday, May 21, 2025, wrote: > Hello, > > I noticed that the patches are now merged in master branch. Than

Re: RFC - AVR fixes and support for AVR DA/DB family

Hi KR, Actually you shouldn't edit the Kconfig manually. Please see inside these files, there is this disclaimer: # # This file is autogenerated: PLEASE DO NOT EDIT IT. # # You can use "make menuconfig" to make any modifications to the installed .config file. # You can then do "make savedefconfig

Re: mDNS - apps utility or kernel? And licensing

Hi Tim, I think everything that speeds up NuttX users development and makes user experience easy is welcome! Please also include some basic Documentation/ explaining how to test it on NuttX. BR, Alan On Tue, May 13, 2025 at 3:07 PM Tim Hardisty wrote: > I have it working as a downloaded 3rd

[OT] We got 2 projects approved to GSoC 2025

Dear NuttXers, Great news! NuttX was again accepted to GSoC! These are the projects and contributors: NuttX Support for IEEE 802.3-2022 10BASE-T1x Ethernet using Open Alliance SPI MAC-PHYs Michal Matias Firmware Upgrades over Silicon-Heaven Protocol for NXboot Demonstrated on pysimCoder Štěpán

Re: sched lock/unlock issue on rp2350

n the scope. > > On 5/6/25 23:19, Alan C. Assis wrote: > > This file: > > > https://github.com/apache/nuttx/commit/9de9f8168d6de8eab8d3a97aac21aacc4e84dd84#diff-ac1d3cade3d9ab380d40fe31f8c006b3035c7b53d04c28e23d9f1ce9a176572c > > > > On Tue, May 6, 2025 at 1:

Re: How to enable rcS script in nucleo-stm32h753zi

/src and compiled in Makefile"* > > This helped me to finally deploy the rcS script successfully. > > > Thanks and Regards > Karukkuvel Raj D > Flight Controls Engineer > > -- > *From:* Alan C. Assis > *Sent:* Monday, May 5, 202

Re: sched lock/unlock issue on rp2350

This file: https://github.com/apache/nuttx/commit/9de9f8168d6de8eab8d3a97aac21aacc4e84dd84#diff-ac1d3cade3d9ab380d40fe31f8c006b3035c7b53d04c28e23d9f1ce9a176572c On Tue, May 6, 2025 at 1:18 PM Alan C. Assis wrote: > Hi Serg, > > I did an analysis here and this macro was introduced in Ja

Re: sched lock/unlock issue on rp2350

Hi Serg, I did an analysis here and this macro was introduced in Jan 10 2024, so it was more than 1 year ago: https://github.com/apache/nuttx/commit/9de9f8168d6de8eab8d3a97aac21aacc4e84dd84 BR, Alan On Tue, May 6, 2025 at 1:12 PM Alan C. Assis wrote: > WOW! Nice catch! > > Questio

Re: sched lock/unlock issue on rp2350

WOW! Nice catch! Question to some people with more experience in the scheduler: Why wasn't this issue detected before? It was added more than 9 months ago. Is there some way to test and enforce that nxsched_process_delivered() and other schedule functions are working as expected? BR, Alan On

Re: How to enable rcS script in nucleo-stm32h753zi

Hi Karukkuvel, There is a 7 years video tutorial here: https://www.youtube.com/watch?v=jYvCe8yQ1OY It is from an old version of NuttX, but could help you to get it working. Also there is an official Documentation here: https://nuttx.apache.org/docs/latest/guides/etcromfs.html#start-up-scripts

Re: [RFC] How to improve NuttX quality and reliability

a serious > proposal: > > * Reduce the number of commits that enter nuttx upstream main branch > each day. > > There are several methods to do that, associated with different states > of comfort and different technical solutions. > > Sebastien > > > On 28/04/2025 18:41, Al

Re: [VOTE] Change setlogmask behavior to POSIX standard

+1 On Tue, Apr 29, 2025 at 3:38 AM Michal Lenc wrote: > Hi all, > > I've submitted pull request that changes setlogmask function behavior to > the one expected by POSIX standard > . The description of the > change is provided in the mailing list, to su

Re: [RFC] How to improve NuttX quality and reliability

being tested), see what comes up? > > Nathan > > On Sun, Apr 27, 2025 at 8:33 AM Alan C. Assis wrote: > > > Dear NuttXers, > > > > In the last weeks we are seeing some degradation of NuttX reliability as > > some users have reported. > > > > We saw it h

Re: RFC - AVR fixes and support for AVR DA/DB family

Hi KR, What avr-gcc version are you using? I'm getting this error: "avr-gcc: error: device-specs/specs-avr128da28: No such file or directory" I found a reference to it here: https://www.avrfreaks.net/s/topic/a5C3l00UlWyEAK/t193338 I downloaded the Microchip.AVR-Dx_DFP.2.7.321.atpack file re

Re: [RFC] How to improve NuttX quality and reliability

ck usage? If stacks are > overflowing, you will get all kinds of weird behaviors. Maybe git bisect > since a month or two ago and run some tests (like run ostest a few times > for each commit being tested), see what comes up? > > Nathan > > On Sun, Apr 27, 2025 at 8:33 

Re: [RFC] How to improve NuttX quality and reliability

or the reliable ports and another one for the experimental ports. > For > > sure it will help Nuttx to become more reliable, safe and for > consequences > > more popular as well. > > > > BR, > > Vinicius > > > > On Sun, Apr 27, 2025, 2:33 PM Alan C. Assis

Re: [RFC] How to improve NuttX quality and reliability

ion I do agree on keeping, kind of, two directories. > One for the reliable ports and another one for the experimental ports. For > sure it will help Nuttx to become more reliable, safe and for consequences > more popular as well. > > BR, > Vinicius > > On Sun, Apr 27, 2025, 2:3

[RFC] How to improve NuttX quality and reliability

Dear NuttXers, In the last weeks we are seeing some degradation of NuttX reliability as some users have reported. We saw it happening yesterday during our Live video: the fb command behaved in some very strange ways: https://www.youtube.com/watch?v=pbq3suU3g5g&t=1740s First it printed all the re

Re: RFC - AVR fixes and support for AVR DA/DB family

Hi KR, On Mon, Apr 21, 2025 at 6:22 AM wrote: > Hello, > > I would like to submit some patches for review and comments. The overall > goal is to provide support for AVR DA/DB family of chips but some of the > patches are more generic - fixes in other AVR chips and some typofixes > elsewhere. > >

Re: HaloOS: Implementation of AutoSAR OS based on the NuttX kernel

I just saw about it in LinkedIn: https://www.linkedin.com/feed/update/urn:li:activity:7321243748682633216 BR, Alan On Fri, Apr 25, 2025 at 10:19 AM Peter van der Perk < peter.vanderp...@nxp.com> wrote: > Thanks for sharing. > > I see that the project is bypassing the NuttX network stack and is

Re: File Sharing Service Mirror

Hi Siddhartha, NuttX is an open-source project, everything you have committed (if you have committed something) it should be in the git: https://github.com/apache/nuttx https://github.com/apache/nuttx-apps Seems like you don't have submitted anything to NuttX (at least searching for your name or

Re: [nuttx] Re: fatfs seems to confuse the Master Boot Record with the FAT32 boot record.

Hi Bob, It was 7 years ago, but today I saw a similar message with a USB Thumb drive:nsh> ehci_waiter: connected nsh> ls /dev /dev: console null sda ttyS0 nsh> mount -t vfat /dev/sda /mnt fat_checkbootrecord: WARNING: Signature: aa55 FS sectorsize: 20487 HW sectorsize: 512 nsh> Maybe it sect

Re: RFC - some AVR (and other) fixes

Hi KR, Sorry for my delay to review your commits. First kudos for your first contribution, it passed without any issues in the checkpatch: $ ./tools/checkpatch.sh -g HEAD~...HEAD $ You did really great including all necessary information in the commit log messages: commit 9ce4bbf808416b9c5be23

Re: Documentation tags for boards

Hi Matteo, That is a great idea! I'm not sure if Nathan's idea will work because Kconfig are completely independent of the board features. Look for example the Photon board, it has WiFi support (BROADCOM_BCM43362) but the only place where it appears is in the defconfig. So, that information sho

Re: Vote for using system dd instead of nsh dd, avoid duplicate code

Yes, if we can merge both in a single dd command, but keep the configuration to have a small dd (like that from nshlib) for small microcontroller as Sebastien suggested, it will be fine. +1 On Mon, Apr 14, 2025 at 10:59 AM Xiang Xiao wrote: > The functionality in system/dd and nshlib is unsync,

Re: [Bug] RP2040 broken, any config&boards, ostest and apps hang

e was some commit in last 3 months. BR, Alan On Mon, Apr 14, 2025 at 8:44 AM alin.jerpe...@sony.com < alin.jerpe...@sony.com> wrote: > Hi Alan, > > 12.9 is already released > I will prepare a 12.9.1 release ASAP > > Best regards > Alin > > > _____

Re: [Bug] RP2040 broken, any config&boards, ostest and apps hang

chips. > I have only tried fresh PicoSDK installs. I have not tried older versions > of PicoSDK yet. > However, I *believe* the PicoSDK is only used for the bootloader, which > might cause problems initializing the hardware? > > Best, > > Kevin > > Op ma 14 apr 2025 om

Re: [Bug] RP2040 broken, any config&boards, ostest and apps hang

pse.com/2022/09/17/picoprobe-using-the-raspberry-pi-pico-as-debug-probe/ > > I find that quite cool. > > Sebastien > > > On 14/04/2025 14:09, Alan C. Assis wrote: > > Hi Kevin, > > > > I will order a Pico Debug probe, it is something new for me. > > > >

Re: [Bug] RP2040 broken, any config&boards, ostest and apps hang

> "heisenbug". > > Best, > > Kevin > > Op ma 14 apr 2025 om 13:27 schreef Alan C. Assis : > > > Hi Kevin and Alin, > > > > I confirmed that NuttX 12.9-RC1 is broken on Raspberry Pi Pico. > > > > After copying the nuttx.uf2 to virtual d

Re: [Bug] RP2040 broken, any config&boards, ostest and apps hang

_FOR_TARGET=arm-none-eabi-readelf STRIP_FOR_TARGET=arm-none-eabi-strip SED=/bin/sed SHELL=/bin/sh BASH=/bin/bash CONFIG_SHELL=/bin/bash Thread model: single Supported LTO compression algorithms: zlib gcc version 13.2.1 20231009 (15:13.2.rel1-2) NuttX support on Raspberry Pi is very important (low co

Re: [Bug] RP2040 broken, any config&boards, ostest and apps hang

Hi Kevin, Thanks for reporting the issue! I will test the new 12.9-RC1 on rasp pico and if the issue happen there I will suggest Alin to wait before releasing the final 12.9 version. BR, Alan On Mon, Apr 14, 2025 at 7:46 AM Kevin Witteveen wrote: > Hi NuttX, > > This is a follow up on previo

Re: Vote for rename modlib to libelf

+1 On Mon, Apr 7, 2025 at 6:13 AM chao an wrote: > Hi community, > > Some green hand and individual developer who are not familiar with nuttx > may be confused by the naming of modlib, in currect implement, modlib as an > elf loader and parser, does not provide any features other than elf. > > I

Re: Vote for default crc16 directory to be CRC-16/XMODEM or CRC-16/IBM

Agree! This will end this discussion! And it will make it clear what algorithm was used. BR, Alan On Wed, Apr 9, 2025 at 9:07 AM Nathan Hartman wrote: > I think the real problem here is that the function is called crc16() with > no details about which CRC polynomial is used. Maybe it's better

Re: Vote for default crc16 directory to be CRC-16/XMODEM or CRC-16/IBM

s my attempt to suggest a clean and better solution to the crc16 > problem. A simple substitution, with bad words, is just replacing trash > with another trash. Absolutely useless. > > There is a better way. > > > Again and again, dont break the default crc16. Consider it legacy. Ke

Re: Vote for default crc16 directory to be CRC-16/XMODEM or CRC-16/IBM

Hi Sebastien, This is a case where compatibility is more important than API stability. New developers are spending a lot of time trying to figure out why existing code is not working and end up discovering that the issue is the CRC incompatible with Linux or other OS. If breaking API is an issue

Re: Discuss NXBoot

; > Tim. > > > On 25 Mar 2025, at 08:16, Sebastien Lorquet > wrote: > > > > Hello, > > > > I agree that for compacity, reintroducing the possibility to disable the > VFS entirely would be quite interesting. > > > > That is a large challenge! &g

Re: Arduino R4 Minima

Hi Roberto, I tested NuttX on an Arduino R4 Minima board and it worked like a charm! The point is: we don't have the serial console at the USB connector by default (I think we just need to change the port in the menuconfig). So to get the serial console working you need to use the RX and TX pins

Re: RP2040 multiple GPIO interrupts

Hi Matteo, I think RP2040 and new RP2350 are good MCUs, but Raspberry Pi Foundation did some terribles mistakes, like using a serial port control that doesn't have indication of transmission done (useful for RS485 support) and GPIO INT with both edges support. When I created the ultrasound sensor

Re: Can NSEC_PER_USEC in clock.h be changed to 1000L?

Hi KR, Nice finding! Could you please open a PR and submit a fix? ( https://nuttx.apache.org/docs/latest/contributing/index.html ) Also if you can, please submit your AVR DA/DB port to be included into the mainline, I'm sure it will be useful to many people here. Some models, like AVR128DB48, ha

Re: Discuss NXBoot

Hi Nathan, It could be just: default y if LCD_FRAMEBUFFER This way it will be "ON" for boards with LCD and Framebuffer enabled and "OFF" for all other boards. Maybe we need to think about how to get NXlogo working for LCD_DEV too. BR, Alan On Fri, Mar 28, 2025 at 10:07 AM Nathan Hartman wro

Re: Discuss NXBoot

gt; Also:i f we wanted to do something "fancy" on multi-cpu architectures, > what are the relevant system calls to get the number of cores? > > On 24/03/2025 19:38, Alan C. Assis wrote: > > Hi Tim, > > > > Yes, these suggestions make sense! >

Re: GSoC 2025 - two topics registered

> > > > >>> - porting https://microblocks.fun/ to NuttX, some proof of > > > > >>> feasibility (smallvm https://bitbucket.org/john_maloney/smallvm > bare > > > > >>> core compilation) already done > > > > >>> &g

  1   2   3   4   5   6   7   8   >