Changing the default value of CONFIG_BOARD_LOOPSPERMSEC

Hello everyone, I have proposed a change wherein the default value for CONFIG_BOARD_LOOPSPERMSEC is no longer "5000" but instead "-1", such that it throws a compilation error if not changed. This is because most users do not know about this configuration value, and wildly incorrect values may cau

Re: RPI 4B Roadmap

core details, but could give you more > understanding about internal block of the SDIO controller (its FIFO, > initialization diagram, etc) > > You can also try to find the original > SD3.0_Host_AHB_eMMC4.4_Usersguide_ver5.9_jan11_10.pdf cited in Raspberry > documentation. > > BR,

Re: RPI 4B Roadmap

egisters, maybe it is based on some SD/MMC core IP already supported by > NuttX. > > BR, > > Alan > > > > On Mon, Sep 15, 2025 at 6:34 PM Matteo Golin > wrote: > > > Hi everyone, > > > > Now that I2C has been tackled, I am moving on to SDIO interf

Re: RPI 4B Roadmap

s the STM32 one that is linked in the docs), resources to read (any blog posts from when you ported SDIO) or advice in general? It would be much appreciated. Thank you, Matteo On Fri, Sep 5, 2025, 11:15 AM Matteo Golin wrote: > Got another response from my earlier request to Raspberry Pi

Re: Changing the default value of CONFIG_BOARD_LOOPSPERMSEC

ight-Check-List may be a nice a nice to add to the > documentation, it can be a table or bullet points with just short > sentence reminders on what is important before firmware launch? Each > reminder would be a hyperlink to a detailed description if someone > sees it for the first time? What d

Re: Developing the NuttX Standard Board

Just a small idea: A couple storage devices could be on there for testing various file systems. I'm thinking NOR flash, NAND flash and an EEPROM would be good additions. They can just be small in size for testing purposes. If you want to save on pins, you could use a single spi bus & CS line for a

Re: git going rust

I honestly don't think it's terrible. I really like how explicit you can be when defining interfaces in Rust. However, I will say that I prefer C. It's stable, ubiquitous and very simple. When I've written Rust I also find there are so many functions/helpers to remember. There are sometimes so many

Re: RPI 4B Roadmap

ivers to get a closer understanding of how the > HW works. Not ideal, but the best I can offer. So I guess everyone is telling us the same thing! On Mon, Sep 1, 2025 at 3:49 PM Tomek CEDRO wrote: > Sure! Public now :-) > Tomek > > On Mon, Sep 1, 2025 at 9:24 PM Matteo Golin > wro

Re: NuttX Hardware Survey 202508

Unfortunately the way the file is named for GitHub to detect it requires it to be called "code owners". But we would not be using it as true "owners", rather as a manifest of which reviewers should be requested for changes to certain files. On Mon, Sep 1, 2025 at 5:36 PM Nathan Hartman wrote: >

Re: NuttX Hardware Survey 202508

Here is my draft PR for a CODEOWNERS file in our repository: https://github.com/apache/nuttx/pull/16962 Already got some good feedback. If you could please take a look and see what you think about the layout/proposed use case, I will then auto-populate it from the git logs and prune it by hand to

Re: RPI 4B Roadmap

they go to the page it might help. Thanks, Matteo On Mon, Sep 1, 2025 at 3:02 PM Tomek CEDRO wrote: > Thank you Linguini, good luck and have fun! :-) > Tomek > > On Mon, Sep 1, 2025 at 8:48 PM Matteo Golin > wrote: > > > > To update the community, we've been told

Re: NuttX Hardware Survey 202508

ore data. > > > > Regarding the documentation, which seems like one of the biggest issues, > we can start formatting a new version of it. I will try and contribute to > the API docs, which are more on the kernel side and it definetely needs > some love. > > _

Re: RPI 4B Roadmap

l set (I2C, SPI, UART) are supported. Matteo On Sun, Aug 31, 2025 at 6:10 PM Matteo Golin wrote: > Very interesting Sebastian. I got that impression from Broadcom when I was > initially trying to port NuttX to the Pi. The inability to submit forms on > their website seems like it might

Re: RPI 4B Roadmap

e :-) > > >> > > >> For a good start you can contact Broadcom and RaspberryPi Foundation, > > >> introduce yourself as Apache NuttX RTOS developer that want to port > > >> NuttX to rPI boards, and just ask if DataSheets are available :-) We > >

Re: RPI 4B Roadmap

Thank you for the insights everyone! I reached out to the RPi foundation this morning. I tried to reach out to Broadcom but every single form on their website that I tried gave me a submission error, so I'm not sure I'll have any luck there. They don't seem very open-source focused. My primary mo

Re: RPI 4B Roadmap

SoC documentation these seems > most popular nowadays :-) > > Thanks :-) > Tomek > > > > On Thu, Aug 28, 2025 at 8:45 PM Matteo Golin > wrote: > > > > Hi Tomek, > > > > Thanks so much! I actually hadn't thought of that, maybe we could ask for

Re: RPI 4B Roadmap

ce code, because it is GPL license, but we > can look at the FreeBSD code: https://wiki.freebsd.org/arm/Raspberry%20Pi > > BR, > > Alan > > On Thu, Aug 28, 2025 at 3:45 PM Matteo Golin > wrote: > > > Hi Tomek, > > > > Thanks so much! I actually hadn

Re: RPI 4B Roadmap

rs. Matteo On Thu, Aug 28, 2025, 12:42 PM Tomek CEDRO wrote: > On Tue, Aug 26, 2025 at 10:05 PM Matteo Golin > wrote: > > I2C still needs some work unfortunately. However, I agree with you > > generally. Personally, I think HDMI, networking (including WiFi and BLE) > > an

Re: RPI 4B Roadmap

tures might be useful too, but I've never used them yet so I'd have to play around. Matteo On Tue, Aug 26, 2025, 8:05 PM Tomek CEDRO wrote: > On Wed, Aug 27, 2025 at 1:56 AM Tomek CEDRO wrote: > > > > On Tue, Aug 26, 2025 at 5:15 PM Matteo Golin > wrote: > &

Re: RPI 4B Roadmap

; For end users probably audio and video are the most important thing to > have. > > For industrial applications probably emmc and ethernet are the most > important. > > What do you think? > > BR, > > Alan > > On Tue, Aug 26, 2025 at 12:15 PM Matteo Golin >

RPI 4B Roadmap

ounded for testing audio and graphics implementations on NuttX. I would love to see more students get involved using NuttX and I think supporting mid-range hobbyist boards is a great step. Let me know what you think! -- Matteo Golin signature.asc Description: PGP signature

uORB questions

x27;t seem very efficient. Thank you, -- Matteo Golin signature.asc Description: PGP signature

Re: NuttX International Workshop 2025

Hello, I would be interested in joining (likely online). If possible, I could present a short talk about using NuttX for rocketry. Matteo On Fri, Jul 18, 2025 at 7:40 AM Alin Jerpelea wrote: > Hi all, > > several developers are working on organizing the the NuttX International > Workshop 2025

Re: [BREAKING] bch/mtd/ftl/fs: Update API with new flags for more granular control.

Are there any test cases that could be used to verify the PR? It's a large change but I don't see any testing logs in the PR. I think this should be tested with a few different devices before getting merged, and the results recorded. Matteo On Thu, Jul 10, 2025 at 1:25 PM Tomek CEDRO wrote: > H

Re: New type of input idea: an action button

I believe the GPIO system does in fact trigger a signal event. I've used this for a project before. However, I think it would be nice to be able to register a callback instead of blocking for a signal, since that introduced A LOT more delay. This would probably need to be done with the low priorit

Re: Documentation in nuttx-apps repository?

I really like this idea, it will make it much easier to enforce documentation with PRs. When I wrote the syslogd app I'm fairly sure my kernel changes (nuttx repo) got merged with the docs a few days before the application was actually merged, which meant that for a few days there was documentation

Re: Sensor fusion on NuttX

Hello, Any updates on the migration? If you need help I can, I would just like to be able to start on writing some fusion implementations with the files migrated properly. Matteo On Wed, Jun 18, 2025 at 4:26 PM Matteo Golin wrote: > Thank you for the explanation! > > That sounds li

Re: Sensor fusion on NuttX

ed to asynchronously perform fusion or if they want to do it synchronously, so I'll have to come up with some kind of standard way to generate fused data with function calls. Thanks again, Matteo On Wed, Jun 18, 2025 at 12:04 AM 董九柱 wrote: > Hi Matteo Golin： > > I see under `uorb

Re: Sensor fusion on NuttX

some light on why the `uorb/sensor` declarations are necessary, and if it would be possible for me to create user space fusion drivers in `uorb/fusion` with their own Kconfig file? Matteo On Fri, Jan 31, 2025 at 5:52 PM Tomek CEDRO wrote: > On Fri, Jan 31, 2025 at 10:56 PM Matteo Golin &

Re: [OT] NuttX Standard Board

Hey Tomek, I added a template for new boards here actually: https://github.com/apache/nuttx/pull/16405 I agree about the STM32 docs though, I'd like to help tackle those once the legacy READMEs are ported and the application docs are closer to being filled out. Matteo On Mon, Jun 9, 2025, 5:22 

Re: SYSLOG over the network

ecuted. I've only been able to achieve that by running the command in NSH with a trailing `&`. Best, Matteo On Sat, Jun 7, 2025 at 11:46 PM Xiang Xiao wrote: > On Sun, Jun 8, 2025 at 7:52 AM Matteo Golin > wrote: > > > > > The central collection that passes on fur

Re: SYSLOG over the network

s. I'll play around with modifying this a little and open a draft PR for RFC5424 lots to get some early review. Matteo On Sat, Jun 7, 2025, 7:51 PM Matteo Golin wrote: > Mainly my concern is that the current implementation of syslog (from my > understanding reading the NuttX so

Re: SYSLOG over the network

Mainly my concern is that the current implementation of syslog (from my understanding reading the NuttX source code) is to `sprintf` the logs into the syslog stream that was configured (gleaned from `nx_vsyslog` in drivers/syslog/vslog.c). This has always worked since logs have only really been con

Re: SYSLOG over the network

ocs/latest/components/drivers/special/syslog.html#syslog-channels> (from what I can tell anyways). Best, Matteo On Wed, Jun 4, 2025 at 9:58 PM Gregory Nutt wrote: > > > ⁣Get BlueMail for Android ​ > > On Jun 4, 2025, 12:29 PM, at 12:29 PM, Matteo Golin < > matteo.go...@gmail.c

Re: SYSLOG over the network

approach is simple, but consumes more memory and can't send out > the final panic log. On the other hand, the second needs to improve the > netdev driver model and NIC driver adaptation, but fix all shortcomings in > the first one. > > On Wed, Jun 4, 2025 at 5:01 AM Matteo Go

SYSLOG over the network

I might not be considering (like setting up a connection, using UDP/TCP, etc)? There would probably have to be a decently large buffer to avoid slowing down code with blocking send calls. What do you think? -- Matteo Golin signature.asc Description: PGP signature

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

Hello KR, Mildly related (about serial on AVR): I've noticed that the serial implementation between avr chips (atmega, at90usb, etc) have almost identical implementations besides the #define names of the IRQ numbers and how many UART interfaces they implement. I'm under the impression that all AVR

Re: NuttX for a critical system

Here's some new footage from yesterday's test, hoping to do one with real fire soon! https://www.linkedin.com/posts/matteo-golin-94118021b_im-very-proud-to-have-been-part-of-cu-inspaces-activity-7335063937069023232-eOEz?utm_source=social_share_send&utm_medium=a

Re: NuttX Logo for rocket/PCBs

Alan, do you still have the file from that PCB? The NX portion would be good for a rocket if I could add the diamond around it. Matteo On Thu, May 29, 2025, 7:16 PM Matteo Golin wrote: > That's a really good idea! I might have to research how well that would > show up in a vinyl sti

Re: NuttX Logo for rocket/PCBs

ginal logo. > > In the past (about 10 years ago) I used a simple NX with the phrase > Empowered by NuttX. My idea was to use Powered by NuttX, but Greg suggested > using Empowered instead of Powered. > > See the old image on the board. > > BR, > > Alan > >

Re: NuttX Logo for rocket/PCBs

Okay this is a very rough example, but this is what I was thinking (also, I would probably make the staggered outline of "NX" a little thicker so it's more visible). What do you think? On Thu, May 29, 2025 at 11:14 AM Matteo Golin wrote: > Maybe that shadowed area could

Re: NuttX Logo for rocket/PCBs

ve 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: >> >>>

Re: Comment for AVR GitHub issue 16444 and PR 16443

arts working this way, that might suggest that the > >> initialization data are placed incorrectly in the image? Anyway, the > >> linker script is pretty much identical to linker script of > >> mega1284p-xplained and that one works out of the box without need to > >>

Re: NuttX Logo for rocket/PCBs

gt; > Alan > > On Wed, May 28, 2025 at 11:20 PM Matteo Golin > wrote: > >> Hello everyone, >> >> CU InSpace would like to feature the NuttX logo among our sponsors' logos >> on our rocket(s) this year. >> >> I saw the logos here: >> htt

NuttX Logo for rocket/PCBs

Hello everyone, CU InSpace would like to feature the NuttX logo among our sponsors' logos on our rocket(s) this year. I saw the logos here: https://nuttx.apache.org/docs/latest/logos/index.html Typically we do all of our sponsor logos in a solid colour since it lends itself better to using vinyl

Re: Comment for AVR GitHub issue 16444 and PR 16443

Managed to find a fix here: https://github.com/apache/nuttx/pull/16457 On Tue, May 27, 2025 at 11:24 PM Matteo Golin wrote: > Thank you for your help KR! > > I also noticed this CONFIG_RAM_START=0x800100. Unfortunately, changing > that value to the proper 0x800200 did not really he

Re: Comment for AVR GitHub issue 16444 and PR 16443

Thank you for your help KR! I also noticed this CONFIG_RAM_START=0x800100. Unfortunately, changing that value to the proper 0x800200 did not really help the issue. I went ahead and generated the disassembly like you suggested, and it does appear that the .text section starts with jump instruction

Re: NuttX for a critical system

ce.. but definitely a > project to share on the NuttX International Workshop! :-) > > Tomek > > On Mon, May 26, 2025 at 5:01 PM Matteo Golin > wrote: > > > > Hello everyone, > > > > Just wanted to share a fun success story with NuttX here! > > > >

TCP keep-alive

or(errno)); if (errno == ECONNRESET) { // TODO: this should trigger an abort because it happens when TCP keep-alive is done herr("Lost connection! ABORT!\n"); } break; } else if (bread == 0) { herr("Control box disconnected.\n"); break; } total_read += bread; ``` Does anyone have any suggestions about how to resolve this? -- Matteo Golin signature.asc Description: PGP signature

RP2040 dual PWM support: one channel not working

26 and 27. Best, -- Matteo Golin signature.asc Description: PGP signature

Raspberry Pi 4B SPI driver

ng the web more than I already have. On the off-chance that anyone here has written bare-metal programs for the Pi 4B or knows about firmware initialization for the BCM2711, I would appreciate any help I can get in understanding how to set up the peripherals better! Best, -- Matteo Golin sig

Re: NuttX releases and release notes

Tue, May 20, 2025 at 11:47 PM Tomek CEDRO wrote: > > > Hey there Matteo :-) > > > > On Tue, May 20, 2025 at 10:24 PM Matteo Golin > > wrote: > > > Hello everyone, > > > While making changes to some of the documentation here on NuttX, I > > noti

NuttX releases and release notes

ther location where they can be exposed to the RC and read about the testing procedure instead of having to find it themselves in the docs. Is there any interest in setting up some of these release options on our GitHub? I can maybe look into it further, starting with generating release notes aut

Re: Enhancing documentation

ality and consistency! Best, -- Matteo Golin signature.asc Description: PGP signature

Re: USB console issues

; On Fri, May 9, 2025 at 12:22 AM Matteo Golin > wrote: > > > Hello, > > > > I am working on making an application run on the W5500-EVB RP2040 boards > > on its own instead of via NSH. I've noticed > > that the moment I turn off the USB console optio

Re: Enhancing documentation

're not native speakers. That's why we are > where we are. It's far from perfect but it's getting better. > > On Wed, May 7, 2025, 14:10 Tomek CEDRO wrote: > > > Great work and Big Thank You Matteo! :-) > > Tomek > > > > On Wed, May 7,

USB console issues

tputting. Is there a way I can make it non-blocking? Thank you for your help, -- Matteo Golin signature.asc Description: PGP signature

Enhancing documentation

ssue similar to #11077 just for tracking. Might be an easy task for new contributors to tackle as well. -- Matteo Golin signature.asc Description: PGP signature

Re: NSH network initialization outside of NSH main

> A better approach is splitting the general initialization functionality > from nsh to init like other POSIX operating systems. > But, the second approach needs more work. > > On Thu, May 1, 2025 at 10:19 AM Matteo Golin > wrote: > > > Hello everyone, > > > >

NSH network initialization outside of NSH main

init()`? I can't access the `netutils` library from board code, and it appears that networking is one of the few initialization tasks without a `boardctl` call. Any help is appreciated! Thank you, -- Matteo Golin signature.asc Description: PGP signature

Re: How frequently is the NuttX documentation updated?

Hello, To my knowledge, the documentation website as whole is updated whenever a change is made to the docs, up to once (or maybe twice?) a day via a CI/CD pipeline. I don't know if there are any automated changes made to the documentation, but that is the workflow when a PR is made by a developer

Re: [VOTE] Change setlogmask behavior to POSIX standard

+1 from me! On Tue, Apr 29, 2025, 2: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

Re: RP2040 multiple GPIO interrupts

l and when that > > interrupt happens I change the GPIO to detect falling edge. Look at > > hcsr04_start_measuring() and hcsr04_int_handler(). > > > > BR, > > > > Alan > > > > On Tue, Mar 18, 2025 at 5:07 PM Matteo Golin > > wrote: > > > >

Re: Documentation tags for boards

[Tested 12.3] or [Tested] and if you hover over it with your mouse "Last > updated: V12.3, {date}". > > These features could improve confidence of the tags. > If these get outdated or loosely used, people will ignore them. As > documentation is not always up to date. Rendering th

Re: Documentation tags for boards

r graphics capable systems), etc. I also think it might be a good idea to add "stable" tags to boards which are regularly tested, but that might have to wait until we're able to really commit to maintaining the stability of those boards. If this gets accepted I can work on tagging mo

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

I quite like these ideas! I've just finished school for the year and have more free time on my hands to help NuttX. Earlier I emailed about tags for boards to help identify peripherals and chips used, it seemed to be accepted well. I will start working on that and include a "stable" tag to use for

Re: Documentation tags for boards

board could have its own tag, mcu would have its own mcu, and > supported peripherals (i.e. wifi), right? > > Thanks :-) > Tomek > > > > On Thu, Apr 17, 2025 at 2:49 AM Matteo Golin > wrote: > > > > Hello everyone, > > > > I am starting a new drone

Re: Documentation tags for boards

assigning tags based on checking defconfig files might be difficult. Some boards just don't have a lot of defconfigs. I think that is a better approach than parsing the many Kconfig files though. Thanks for the help! -- Matteo Golin signature.asc Description: PGP signature

Re: Documentation tags for boards

o filter by "has FPU, has SDMMC, has WiFi", etc. It would be useful to narrow down chip selections based on what NuttX has support for. -- Matteo Golin signature.asc Description: PGP signature

Documentation tags for boards

for a chip in NuttX, please let me know if you have any tips to get started or if you've happened to write a guide. I might decide to spend some time on adding support for wireless chips to learn more about it. Thanks! -- Matteo Golin signature.asc Description: PGP signature

Re: RP2040 multiple GPIO interrupts

g? Thanks again for the suggestions, I'll have to do some thinking but maybe the polling approach is the safest bet. Matteo On Tue, Mar 18, 2025 at 8:23 AM Nathan Hartman wrote: > On Mon, Mar 17, 2025 at 5:18 PM Matteo Golin > wrote: > > > Hello everyone, > > > &

RP2040 multiple GPIO interrupts

r issue or has suggestions about how I can resolve this. Thanks, -- Matteo Golin signature.asc Description: PGP signature

Re: [PROPOSAL] New nxstyle tool roadmap

Hello, I have tried to make a clang format configuration to use, but I have the same problem where there are a couple style items that clang format has no options for. Things like enforcing lowercase hex or putting curly braces indented on a separate line after static initializers. On Mon, Mar 17

Re: [VOTE] ROUND2 NuttX Contributing Guidelines update 202502.

On Fri, Feb 28, 2025 at 1:45 AM Dmitri Shilov wrote: > > > > > > 1. Contributing Guidelines with hints for Reviewers. > > > > > > > We are adding additional section for Reviewers to Contributing > > > > Guidelines in order to provide checklist and complementary set of > > > > rules that s

Re: RP2040 clock speed increase

gt; On Sat, Feb 22, 2025 at 7:02 AM Matteo Golin > wrote: > > > > It appears this is selected at compile time using a #define in the SDK. I > > would certainly assume increased power consumption, however the Picos are > > definitely able to handle this increased consumpti

Re: RP2040 clock speed increase

o not know how much of an increase in power is required for the speed increase, but I do know that the speed increase is rated for any board with >1.15V supply. On Fri, Feb 21, 2025, 10:12 PM Tomek CEDRO wrote: > On Fri, Feb 21, 2025 at 7:53 PM Matteo Golin > wrote: > > Rec

RP2040 clock speed increase

to update every single RP2040 board page with the new version when we upgrade on the NuttX side. That way each board page can simply link to the installation procedure (afaik none of them have a different procedure). Regards, -- Matteo Golin signature.asc Description: PGP signature

Re: Regarding bmi270

Hello, The MCP9600 was a new driver, I moved it to uORB very shortly after it was suggested by reviewers. I don't see any value in keeping it in the legacy format. I believe the user can still read data from uORB sensors with `read()` (unless I'm misunderstanding the driver structure), just the bu

Re: Best way to go about generic driver

ok my transmitter for a walk and got some successful long range test results! Any feedback is appreciated before I add the finishing touches and unmark as draft. Thanks, -- Matteo Golin signature.asc Description: PGP signature

Re: [VOTE] NuttX Contributing Guidelines update 202502.

1. +1 2. +1 3. +1 4. +1 5. +1 6. +1 definitely shouldn't put runtime logs in the commit description 7. +1 8. +1 9. +1 10. -1, breaking changes shouldn't be unwelcome so long as they are discussed an agreed upon by the community via the mailing list first. Some criteria on what is considered suffic

Best way to go about generic driver

ename the device registration functions or #include file name when I add support for the RN2903. Are there any suggestions for what would be the best way to go about this? Thanks, -- Matteo Golin signature.asc Description: PGP signature

Re: [DRUNX] Distributed Runtime and bUild for NuttX

I've got: - Raspberry Pi Pico - Raspberry Pi Pico W - XIAO RP2040 - XIAO SAMD21 - Raspberry Pi 4B And would also be willing to help test, provided it's easy enough for me to automate. On Thu, Feb 6, 2025 at 2:33 PM Tiago Medicci Serrano < tiago.medi...@gmail.com> wrote: > Hi! > > I wonder if tha

Re: NuttX Code Quality Improvement 2025Q1

Hello, If I may add to the proposed contributing guideline changes: all changes affecting behaviour/APIs or adding features should be properly documented, not just within the PR. NuttX has many features and lots of apps for using them, but a lot of them are left undocumented outside of inline comm

Re: Explanation request about a the merging of an unacceptable pull request

I like this plan of requiring hardware testing. Also, even if the PR may contain enough information to be justified, it becomes really difficult for anyone debugging to track down changes if the PR body doesn't have a description of any testing or the change impact. If all the PRs follow the enforc

Re: Sensor fusion on NuttX

s/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 > > wrote: > > > > > Hello Xiang, > > > > > > Thank you for the links! What do you think abo

Re: Sensor fusion on NuttX

this without registering fusion nodes in board startup code with something like `orb_advertise`? Matteo On Wed, Jan 29, 2025 at 12:17 AM Xiang Xiao wrote: > On Wed, Jan 29, 2025 at 6:34 AM Matteo Golin > wrote: > > > Hello again everyone, > > > > I was going through som

Re: Sensor fusion on NuttX

to collaborate or help in any way on what > would be possible with uORB inside NuttX. > > Looking forward to hearing thoughts from the community. > > Best regards, > Ludovic Vanasse > ludovicvana...@gmail.com > +1(514) 475-0447 > > > On Tue, Jan 28, 2025 at 5:34 PM Matte

Sensor fusion on NuttX

mething like this be beneficial for NuttX? -- Matteo Golin signature.asc Description: PGP signature

Re: Questions about STM32 support/programming

hts it here: > > > https://nuttx.apache.org/docs/latest/reference/os/led.html > > > > > > Also, the board_autoled_on/off depends on how your LED is physically > > > connected on your board: common cathode / common anode. > > > > > > You need to k

Re: Questions about STM32 support/programming

ithout any UART. > > > > Also there are more powerful tools for Segger debuggers in NuttX, > like > > > > SystemView. > > > > > > > > Last time I tested LWL it was terribly slow and heavily loaded the > CPU > > - > > > > incompara

Re: L1 Flight Computer for NuttX

e 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, > > > > I just wanted to share that I have finished developing a

Re: Questions about STM32 support/programming

LINK if possible with > > > > > https://www.segger.com/products/debug-probes/j-link/models/other-j-links/st-link-on-board/ > > or even investing in a dedicated tool from Segger. It's really money > worth > > investment. > > > > śr., 22 sty 2025 o 22:45

Re: L1 Flight Computer for NuttX

Thanks Tomek! Also it appears I posted the wrong link to the design files and instead put the Telemetrum page. Here they are: https://github.com/linguini1/pygmy On Thu, Jan 23, 2025, 10:04 PM Tomek CEDRO wrote: > On Fri, Jan 24, 2025 at 4:00 AM Matteo Golin > wrote: > > Hello eve

L1 Flight Computer for NuttX

7;t know how many boards have been built with the intent to run NuttX specifically, but here is another that will hopefully gain some popularity in the rocketry community. -- Matteo Golin signature.asc Description: PGP signature

Re: Questions about STM32 support/programming

see the > "activity" coming from it. > > BR, > > Alan > > > On Wed, Jan 22, 2025 at 12:59 PM Matteo Golin > wrote: > > > Hello Alan, > > > > Thank you for the insights, I will take a look at the video resource you > > mentioned. Would th

Re: Questions about STM32 support/programming

Thank you as well Sebastien! We are planning to do an out-of-tree build, I was just hoping to minorly modify an existing build locally to see about booting NSH first. Perhaps it's more worthwhile to just start by doing it the right way. On Wed, Jan 22, 2025 at 10:57 AM Matteo Golin

Re: Questions about STM32 support/programming

ope these suggestions help you to fix the issue. If you are still facing > issues, compile NuttX with debug symbols enabled and use OpenOCD + GDB to > see where it is stopping. > > BR, > > Alan > > On Wed, Jan 22, 2025 at 11:26 AM Matteo Golin > wrote: > > >

Re: Questions about STM32 support/programming

boards! I might read into that if I have success with the UART later. On Wed, Jan 22, 2025, 4:02 AM Tomek CEDRO wrote: > On Wed, Jan 22, 2025 at 2:48 AM Matteo Golin > wrote: > > I have attempted flashing the chip with an STLink using the openocd > > commands suggested here, an

Re: Questions about STM32 support/programming

n 0 at 0x0801d5f8 with 8 bytes (bank write end alignment) Warn : Adding extra erase range, 0x0801d600 .. 0x0801 ** Programming Finished ** ** Verify Started ** ** Verified OK ** ** Resetting Target ** shutdown command invoked On Tue, Jan 21, 2025 at 8:47 PM Matteo Golin wrote: > Hello every

Re: Questions about STM32 support/programming

. Wondering if anyone with experience porting to new STM32 boards has some debugging tips for us to try. Thank you for all your help so far! Matteo On Tue, Oct 1, 2024 at 9:36 AM Matteo Golin wrote: > Thank you everyone for the responses, lots to consider. > > I'll have some of our mem

  1   2   >