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.
> >
> >
> "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
_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
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
+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
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
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
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
;
> 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
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
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
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
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
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!
>
> > > > >>> - porting https://microblocks.fun/ to NuttX, some proof of
> > > > >>> feasibility (smallvm https://bitbucket.org/john_maloney/smallvm
> bare
> > > > >>> core compilation) already done
> > > > >>>
&g
But changing from GNU to Altman (removing 2 "half" indentation spaces)
could fall on this category:
``No "revolutionary" changes to the coding standard (but perhaps some
"evolutionary" changes).''
BR,
Alan
On Wed, Mar 19, 2025 at 10:24 AM Gregory Nutt wrote:
> Coding style change are discuss
Hi Tim,
Yes, these suggestions make sense!
I think for NXBoot should be nice to have the option to disable features
that were used for minsh board profile:
#
# RTOS Features
#
CONFIG_DISABLE_SIGNALS=y
#
# Files and I/O
#
CONFIG_SDCLONE_DISABLE=y
CONFIG_NFILE_DESCRIPTORS=0
CONFIG_NFILE_STREAMS=0
el Pisa
> > phone: +420 603531357
> > e-mail: p...@cmp.felk.cvut.cz
> > Department of Control Engineering FEE CVUT
> > Karlovo namesti 13, 121 35, Prague 2
> > university: http://control.fel.cvut.cz/
> > personal: http://cmp.felk.cvu
t;
> As of now, indentation works, there is no bug to fix, and changing it
> will not improve nuttx.
>
> Sebastien
>
>
> On 19/03/2025 16:14, Alan C. Assis wrote:
> > But changing from GNU to Altman (removing 2 "half" indentation spaces)
> > could fall on thi
Hi Michal,
That makes sense, actually I think Altman is similar (but more elegant) to
GNU style:
https://en.wikipedia.org/wiki/Indentation_style
BR,
Alan
On Mon, Mar 17, 2025 at 7:32 PM Michał Łyszczek
wrote:
> Peter van der Perk:
> > The main issue I was facing with clang-format was the ind
university: http://control.fel.cvut.cz/
> > personal: http://cmp.felk.cvut.cz/~pisa
> > company:https://pikron.com/ PiKRON s.r.o.
> > Kankovskeho 1235, 182 00 Praha 8, Czech Republic
> > projects: https://www.openhub.net/accounts/ppisa
> > s
boot logo) to this should be relatively
> trivial and is something I'd like too - I'll look into it.
>
> For now, the remaining issue I have to solved is the decoding of the
> VT100_CURSORL(n) and once I have that cracked I will submit a PR and we
> can discuss it there too
Hi Tim,
About your progress with fbcon, just realized you created it as an
application, do you think it could be part of the kernel (like in Linux) ?
This way it could be used to print the initialization messages from the
kernel too.
Sometime ago we discussed the idea of adding a boot logo to Nu
allowed
>
> Single company commit, review, merge is not allowed. Each PMC Member,
> Committer, and Reviewer must report up-to-date Affiliation for clear
> identification.
>
> See: https://github.com/apache/nuttx/blob/master/INVIOLABLES.md
>
> Also -1 and 0 answers given here with prio
ig choice to either use this app as a simple stdout device, or a
> full blown console...much like nxterm but without the need of the nx
> server etc.
>
> On 08/03/2025 16:50, Alan C. Assis wrote:
> > Hi Tim,
> > Could you please try to run: "ls -l | hexdump"
> >
Hi Tim,
Could you please try to run: "ls -l | hexdump"
It could show if the '\n' is received correctly.
BR,
Alan
On Fri, Mar 7, 2025 at 3:47 PM Tim Hardisty wrote:
> I am writing a Framebuffer console app that takes stdout and stderr and
> renders the text to a framebuffer device. Based on ex
t;
> > > Related to that PR: Documentation in not software and does not belong
> to
> > > code changes in arch
> > >
> > > I think that this rule should be enforced even if we don't do LTS
> > releases
> > > for now but we will do them
f the same PE but in a separate commit
>
> Best regards
> Alin
>
> On Sat, 1 Mar 2025, 11:11 Alan C. Assis, wrote:
>
> > Hi Tomek,
> >
> > Nice work! Kudos!
> >
> > About Documentation I voted +1 to have Documentation, but later I
> realiz
Hi Tomek,
Nice work! Kudos!
About Documentation I voted +1 to have Documentation, but later I realized
it was required to be in a separate PR, which I don't agree with.
When I contributor submit a new feature that doesn't have Documentation I
ask them to include it to avoid creating hidden featu
ling list for voting as Alin noted :-)
> Tomek
>
>
>
> On Thu, Feb 27, 2025 at 3:46 PM Alan C. Assis wrote:
> >
> >
> >
> > Google forms confirmed that I voted on Fev 24, no idea why you didn't
> see it...
> >
> >
> > On Thu, Fe
Please find the form answers below.
I think it is better if everybody forwards the form to the mailing list,
this way it will be easier to review and re-count the votes.
BR,
Alan
-- Forwarded message -
From: Google Forms
Date: Mon, Feb 24, 2025 at 12:20 PM
Subject: NuttX Contri
If you find the first answered form, please use it.
BR,
Alan
On Thu, Feb 27, 2025 at 11:46 AM Alan C. Assis wrote:
> [image: image.png]
>
> Google forms confirmed that I voted on Fev 24, no idea why you didn't see
> it...
>
>
> On Thu, Feb 27, 2025 at 11:44 AM Alan
[image: image.png]
Google forms confirmed that I voted on Fev 24, no idea why you didn't see
it...
On Thu, Feb 27, 2025 at 11:44 AM Alan C. Assis wrote:
> Just did it again!
>
> On Thu, Feb 27, 2025 at 11:33 AM Alan C. Assis wrote:
>
>> Hi Tomek, it is strange, I vot
Just did it again!
On Thu, Feb 27, 2025 at 11:33 AM Alan C. Assis wrote:
> Hi Tomek, it is strange, I voted in this second round, but my vote didn't
> show up.
>
> BR,
>
> Alan
>
> On Thu, Feb 27, 2025 at 8:20 AM Tomek CEDRO wrote:
>
>> Dear NuttX Communit
Hi Tomek, it is strange, I voted in this second round, but my vote didn't
show up.
BR,
Alan
On Thu, Feb 27, 2025 at 8:20 AM Tomek CEDRO wrote:
> Dear NuttX Community please vote! Tomorrow we are closing the vote and
> we have only 4 votes for now, in the previous round we had 12 votes,
> so vo
I like the LTS idea, but I need to vote -1 too!
- We don't have enough staff to even review PRs, let alone create a new
burden to LTS support.
- The current LTS approach is forcing contributors to divide PRs in many
commits, although other projects with LTS are not requiring it.
- First we need to
...@sony.com <
alin.jerpe...@sony.com> wrote:
> Hi Alan,
>
> Thanks for sharing the information
>
> Best regards
> Alin
> ________
> Från: Alan C. Assis
> Skickat: den 25 februari 2025 1:35
> Till: dev@nuttx.apache.org
> Ämne: [
Hi NuttXers,
Last month Google/Fitbit released PlebbleOS source code (Apache License)
https://ericmigi.com/blog/why-were-bringing-pebble-back
The code is in GitHub and probably there are useful things that could be
interesting for NuttX community to explore (they used FreeRTOS but the C
code is
t;
> On Mon, Feb 24, 2025 at 4:25 PM Alan C. Assis wrote:
> >
> > Tomek,
> >
> > Single you are driving this discussion, could you please take care of the
> > management of the NuttX GSoC 2025?
> >
> > There is another suggest that could participate this ye
Tomek,
Single you are driving this discussion, could you please take care of the
management of the NuttX GSoC 2025?
There is another suggest that could participate this year:
https://github.com/ghaerr/microwindows/issues/85
BR,
Alan
On Wed, Feb 12, 2025 at 11:00 PM Lee, Lup Yuen wrote:
> Sor
Hi Kevin,
I think it is possible to create a generic audio using PWM and DMA, but it
will require two halves design (like many drivers in NuttX).
The top half will implement the high end driver to be present like an audio
codec to the application (this way we don't need to modify existing
applica
ports RS485"*
> So not really supported?
> Just for my own understanding and peace of mind, i dont really care - just
> seems a bit odd.
> But then again, lots of chips out there lacks features that it is supposed
> to include.
>
> Den tis 18 feb. 2025 kl 16:08 skrev Alan C
Hi Erik,
Do you want to implement it using the native HW from serial controller to
support RS485 or do you just want RS485 and it could be implemented as in
other MCUs where after detecting transfer complete we control the DE/RE pin?
If the later is OK for you, then please take a look how it was
nd, perhaps, guide the
> user through recovery procedures. The LCD is the only display available,
> as a serial console is not available to the user for this embedded
> device. But could be a generally useful thing?
>
> On 16/02/2025 10:45, Alan C. Assis wrote:
> > Hi Tim,
> &
ugh?
>
> > On 15 Feb 2025, at 13:42, Alan C. Assis wrote:
> >
> > Hi Tim,
> >
> > You can create a NuttX application with LVGL and display your message or
> > image.
> >
> > Actually you don't need to use a graphic library if you just want
Hi Tim,
You can create a NuttX application with LVGL and display your message or
image.
Actually you don't need to use a graphic library if you just want to write
in the framebuffer, you can convert image to display directly in the
/dev/fb0
BR,
Alan
On Sat, Feb 15, 2025 at 7:45 AM Tim Hardisty
e.
>
> On Thu, Feb 13, 2025, 20:26 Alan C. Assis wrote:
>
> > Hi Matteo and Matheusz,
> >
> > What I mean was the original driver doesn't have a direct read() as in
> the
> > old style sensors, and if you look usensor_read() is just return success
> >
;
> > > czw., 13 lut 2025 o 18:02 raiden00pl
> napisał(a):
> > >
> > >> Yes, mcp9600_uorb.c not support legacy implementation, but `uorb`
> > >> implementation
> > >> is also a character driver. The new sensor implementation also
> supports
> &
mcp9600_uorb.c` is just a character driver but with standardized
> interface, so other similar chips can be used with the same user-space
> code.
> You don't need `apps/system/uorb` to use it.
>
>
>
> czw., 13 lut 2025 o 17:11 Alan C. Assis napisał(a):
>
> > Hi Ma
t; should be forced to use it?
> >
> > Surely any NuttX sensor driver MUST have a character driver, but could
> > OPTIONALLY have a uORB variant? Or am I missing something?
> >
> >
> > > On 13 Feb 2025, at 14:02, Alan C. Assis wrote:
> > >
>
have a uORB variant? Or am I missing something?
>
>
> > On 13 Feb 2025, at 14:02, Alan C. Assis wrote:
> >
> > Good question Tim,
> >
> > Ideally all sensors should have char device and uorb support, but I don't
> > think we have this rule.
>
uses uORB" but perhaps you meant that was just
> an easy/easier way to test it if there's no BMI270 example app?
>
> Just looking for clarity for my interest but also to make sure the OP is
> given full information :-)
>
> On 12/02/2025 20:30, Alan C. Assis wrote:
>
Yes, we still have char driver sensors and uorb sensors
On Wed, Feb 12, 2025 at 5:05 PM Tim Hardisty
wrote:
> Ah - so something you choose to use or not? But still we'll have
> "traditional" drivers for new sensors as they're added?
>
> On 12/02/2025 19:29,
Hi Tim,
It came from PX4 and how it is used for our sensors.
BR,
Alan
On Wed, Feb 12, 2025 at 4:21 PM Tim Hardisty
wrote:
> Is uORB really just a PX4 thing? Not NuttX? Or did NuttX adopt uORB too
> and I missed it?
>
> Just curious :-)
>
> On 12/02/2025 18:51, Alan C. A
>
> On Wed, Feb 12, 2025, 11:43 PM Alan C. Assis wrote:
>
> > Hi Yashvi,
> >
> > Please describe the issue you are facing. BTW, did the i2c scan find your
> > BMI270?
> >
> > BR,
> >
> > Alan
> >
> > On Wed, Feb 12, 2025 at 2:41
Thank you!
>
> On Wed, Feb 12, 2025, 11:05 PM 175 yashvi shah
> wrote:
>
> >
> >
> > Hello,
> >
> > By applying this, I was able to successfully execute the I2C scanner.
> >
> > Thank you!
> >
> > On Wed, Feb 12, 2025, 9:16 PM Ala
The goal is not to automatically merge PR, but only to avoid that some PRs
that don't reach the maximum number of reviews be allowed to be merged.
Typically, those who are most eager to impose new rules are not the same as
those who are subject to them!
BR,
Alan
On Wed, Feb 12, 2025 at 2:5
PID GROUP PRI POLICY TYPENPX STATE EVENT
> SIGMASK D
> dump_task: 0 0 0 FIFO Kthread - Ready
> 00>
> dump_task: 1 0 240 RR Kthread - Running
> 00>
>
> On Wed, Feb 12, 2025, 7:12 PM Alan C. Assis wrote:
>
&
Hi Yashvi,
Please send the dump of this crash, using it you can find where the code is
crashing.
BR,
Alan
On Wed, Feb 12, 2025 at 2:51 AM 175 yashvi shah
wrote:
> Hello,
>
> I am attempting to retrieve data from a BMI270 sensor on an STM32H7 board.
>
> However, when using the I2C scanner, a p
Could someone using CAN Bus review this modification:
https://github.com/apache/nuttx/pull/15809
BR,
Alan
1. +1
2. +1
3. +1
4. +1
5. +1
6. +1
7. +1
8. +1
9. +1 // this is something we need to improve, HW CI should confirm if a
PR is working
10. -1
In some cases breaking previous compatibility is necessary to evolution of
the project, but these breaking need to be discussed further in the
mainling lis
NuttX has support to LibmCS that already fixed those (and other issues)
https://gtd-gmbh.de/libmcs
But maybe those corrections from the article you cited could be applied to
our standard libm functions.
BR,
Alan
On Mon, Feb 10, 2025 at 2:26 PM Tomek CEDRO wrote:
> Here goes interesting pape
Hi Tomek,
Normally we create entries in the GSoC and people interested in those
topics will contact us.
I think for this year we have two suggestions:
* Improving the NXBoot to evolve NuttX as Bootloader (maybe add commands
compatible with U-Boot)
* Syscalls Parameters Validation (not sure if it
Please follow these steps:
https://nuttx.apache.org/community/
On Fri, Feb 7, 2025 at 3:25 AM Daniel Byshkin wrote:
> Empty Message
>
Hi Tomek,
Try to compile using "make -j" it will reduce the time from minutes to
seconds (but will consume more power).
BR,
Alan
On Thu, Feb 6, 2025 at 10:54 PM Tomek CEDRO wrote:
> On Thu, Feb 6, 2025 at 7:30 PM Alan C. Assis wrote:
> > Something to keep in mind abo
I think we can ask people to suggest some names and we can select the best
name.
Something to keep in mind about this distributed (build) system:
Not everyone has free electricity (solar panels) to run a computer server
24/7. And a solution where the server owner only runs it occasionally won't
h
since we don't have to go back and re-read the
> code to document things.
>
> Matteo
>
> On Thu, Feb 6, 2025 at 10:10 AM Alan C. Assis wrote:
>
> > Hi Tomek,
> >
> > You missed that rule:
> >
> > * If one person approves a PR and no other revi
Hi Tomek,
You missed that rule:
* If one person approves a PR and no other reviews or objections after a
week, the person who approved the PR can assume a "lazy consensus" and go
ahead and merge.
BR,
Alan
On Thu, Feb 6, 2025 at 12:46 AM Tomek CEDRO wrote:
> Hello world :-)
>
> We have long d
I think we should test the most complete/complex boards from each arch. It
will cover most of the issues that could after other boards.
BR,
Alan
On Wed, Feb 5, 2025 at 4:23 AM raiden00pl wrote:
> As mentioned earlier, testing all boards is pointless, especially since the
> project
> has very l
nxboot is NuttX as Bootloader
On Tue, Feb 4, 2025 at 9:55 AM Tomek CEDRO wrote:
> On Tue, Feb 4, 2025 at 1:34 PM Alan C. Assis wrote:
> > Hi Tomek,
> > I think the support already exist:
> > https://nuttx.apache.org/docs/latest/applications/boot/nxboot/index.html
>
>
Dear NuttXers,
I think an issue when handling multiple boards is the physical peripherals
and connectors from a board to another. It makes the test more complicated.
Something we could explore is using a CPU card board format (such as
MicroMod: https://www.sparkfun.com/micromod or Raspberry
Syste
Hi Tomek,
I think the support already exist:
https://nuttx.apache.org/docs/latest/applications/boot/nxboot/index.html
BR,
Alan
On Tue, Feb 4, 2025 at 3:28 AM Tomek CEDRO wrote:
> How about to try out NuttX as bootloader for other OS as the idea for GSoC
> 2025?
>
> --
> CeDeROM, SQ7MHZ, http:/
Good idea! It is better to have all sensors tested in a single place, there
are many individual sensors applications inside apps/examples/, they also
need to be moved to apps/sensors/
BR,
Alan
On Wed, Jan 29, 2025 at 12:40 PM Xiang Xiao
wrote:
> On Wed, Jan 29, 2025 at 10:52 PM Matteo Golin
>
Hi Simon,
Yes, but it important to prove your point using a commercially available
development board.
NuttX (just like Linux) is a moving target. So one out of tree board always
will break because people are constantly changing the building system and
moving things of place.
There is no simple w
Hi Sebastien,
This is the last time that I will eat the bait!
I agree that all commits should have some proper git commit message and
that is something that normally I always ask for!
And as others already commented this is part of a bigger PR and this
specific commit is very intuitive.
So, inst
e sensors and GPS.
>
> Matteo
>
> On Fri, Jan 24, 2025, 6:25 PM Alan C. Assis wrote:
>
> > Hi Matteo,
> >
> > Nice to know you are doing processes!
> >
> > The diagnostic LEDs (CONFIG_ARCH_LEDS) is also "very board specific", the
> &
rs was actually very painless. They
> were well commented and I only had to change a few multipliers to make the
> frequencies line up.
>
> On Sat, Jan 25, 2025, 9:25 AM Alan C. Assis wrote:
>
> > Hi Matteo,
> >
> > Very nice! Great news!
> >
> > Could you s
Ds if I set
> them high in the `board_autoled_initialize` function though. In the
> menuconfig options I saw that I can also enable
> `CONFIG_ARCH_LEDS_CPU_ACTIVITY`. Is this needed to have
> `board_autoled_on(LED_STARTED)` to occur?
>
> Thanks again for all your help!
> Matt
Hi Matteo,
Congratulations for achieving it! I just posted about it on LinkedIn too!
We are grateful for all you have done for NuttX too! The Raspberry Pi 4
port for example will open new possibilities for NuttX!
BR,
Alan
On Fri, Jan 24, 2025 at 12:00 AM Matteo Golin
wrote:
> Hello everyone,
Hi Matesz,
Yes, LWL is slow because it is working using a polling approach (AFAIK ARM
DAP has support for interruption, but it is not implemented yet).
The main purpose of the LWL is to be the initial console before the real
serial driver is not implemented yet.
I think J-Link is a nice tool and
> more I did not consider. Good to know about the DFU at least!
>
> Thank you again,
> Matteo
>
> On Wed, Jan 22, 2025 at 10:39 AM Alan C. Assis wrote:
>
> > Hi Matteo,
> > You cannot use the firmware binary from some random STM32H743 board on
> your
> > c
Hi Matteo,
You cannot use the firmware binary from some random STM32H743 board on your
custom board, unless it is using the same clock frequency and same UART
console.
Looking at the board.h from weact-stm32h743 shows it is using a 25MHz
crystal, so I suppose you are using this same crystal value
nsh>
> nsh> nsh: nsh>: command ntfound
> nsh: nsh:: command not found
> nsh> nsh> ^[ s>^el(
> nsh: nsh>: command not found
> nsh> l
>
> Em qua., 15 de jan. de 2025 às 11:36, Alan C. Assis
> escreveu:
>
> > Hi Felipe,
> >
> > If you a
Hi Felipe,
If you are using one of these two UART as serial console (to NSH), then you
can see it using the USB Serial/JTAG interface:
https://docs.espressif.com/projects/esp-idf/en/stable/esp32c6/api-guides/usb-serial-jtag-console.html
This way you will have two real serials available to your p
Very nice Alin!!! Kudos!!!
BR,
Alan
On Monday, January 6, 2025, Alin Jerpelea wrote:
> The Apache NuttX project team is proud to announce:
>
> Apache NuttX 12.8.0 has been released.
>
> The release artifacts and Release Notes can be found at:
> https://nuttx.apache.org/download/
> https://nutt
t;>>>>>>>>>> 0800c1a8 t nsh_erroroutput
>>>>>>>>>>>>> 0800c1d8 t nsh_consolelinebuffer
>>>>>>>>>>>>> 0800c1ec t nsh_consoleclone
>>>>>>>>>>>>> 0800c20a t nsh_consolerele
t;> 08016b30 T sysinfo
>>> 08016ba4 T nxsched_waitpid
>>> 08016ca4 T waitpid
>>> 08016cdc t nxsched_cpu_scheduler
>>> 08016d0c t nxsched_process_scheduler
>>> 08016d6a T nxsched_process_timer
>>> 08016d84 t nxsem_wait_slow
>>> 08016f5c T nxse
Hi Yashvi,
Could you please confirm that Board LED Status support is not selected?
Normally this is the "trap" that prevent USERLED to work, more here:
https://embeddedrelated.com/showarticle/1633.php
I just tested here:
$ ./tools/configure.sh nucleo-f446re:nsh
$ make menuconfig
Board Select
llo,
> On 1/2/25 23:52, Alan C. Assis wrote:
>
> Hi Yousif,
>
> This is the kind of feedback we like to hear! Thank you for that!
>
> NuttX is used in many areas including critical real-time applications. So,
> if your question is: Is NuttX safe enough to be used in medical
&
Hi Yousif,
This is the kind of feedback we like to hear! Thank you for that!
NuttX is used in many areas including critical real-time applications. So,
if your question is: Is NuttX safe enough to be used in medical
application, the answer is YES!
It is used in drone, rockets (search for NuttX l
Hi Alin,
I don't have personal preference, since we are doing it every year since
2019, we always face different challenges every year and that is fine.
This is like taking vacation and facing some issues, after some years you
realize those issues were what enriched your experience.
BR,
Alan
O
Hi Sebastien,
I think you raised a legitime (and important) concern.
Who could tell us if this usage of the fediverse is fine or not?
Maybe some optimization could be done to avoid sending too many messages.
BR,
Alan
On Sat, Dec 28, 2024 at 6:31 PM Sebastien Lorquet
wrote:
> Hi,
>
> You kno
That is great!!! Kudos Alin!
BR,
Alan
On Tue, Dec 31, 2024 at 2:43 AM Alin Jerpelea wrote:
> Hi all,
>
> I would like to invite you to join us on the NuttX FOSDEM talk
>
> https://fosdem.org/2025/schedule/event/fosdem-2025-4528-sbom-journey-for-an-open-source-project-apache-nuttx-rtos/
>
> Bes
onfiguration (defconfig) outside of the
> nuttx folder while maintaining my nuttx folder free from changes so
> that I can keep the nuttx folder in sync with the repo. What is the
> best way to achieve this ?
>
> Kind regards,
>
> Jehudi
>
> Op do 19 dec 2024 om 09:28 s
Hi Aaron,
Nice to know you have previous experience with NuttX on Sony Spresense.
The process to support other boards is very similar, I suggest you to read
our official documentation:
https://nuttx.apache.org/docs/latest/quickstart/index.html
If you still have questions, please feel free to as
Hi Russel,
Please look at the schematics of both boards, sometimes ST change pins used
on different board revisions.
Also, if you discover some important detail about these boards, please
submit a PR updating the board Documentation/ this way you make the life of
the next developer/user easier.
t; thanks Alan,
> > I inherited the project from another developer and have been using his
> > settings - will start turning things off
> > right after I posted I built the Nuttx example for this board so I am
> > going to use this as basis for my project
> > russ
&
Hi Russell,
Question: if you use the original board nsh example, does it work?
About the out of memory, please try to run the "free" command, it could
return the amount of free memory.
I noticed you enabled many features (and debugging), also I noticed you are
enabling cu terminal, but you have
Hi Jehudi,
I just saw in the Discord channel that you got it working.
Please let's know what was the issue with our documentation and how did you
fix it?
Also I think your suggestion to move the mounting of procfs, tmpfs, etc
from boards to some common initialization makes sense to me.
Let's se
Hi Tiago,
I think the issue could be related to the GPIO RTC: the GPIO pins have
different interruption configurations in normal mode and low power mode
(called GPIO RTC mode).
Maybe it could be the root cause of the issue, but not idea why WiFi is
interfering on it (since it works when WiFi is n
1 - 100 of 713 matches
Mail list logo
