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

Re: Extending UORB for thermocouples

available for this purpose yet. > > > sob., 18 sty 2025 o 04:05 董九柱 napisał(a): > > > hello Matteo Golin: > > > > I'm Donny. About these questions, i have some suggestions. > > > > Regarding the first question, we first need to clarify what data

Re: Extending UORB for thermocouples

ouple values in `sensors/ioctl.h`? Thanks again, Matteo On Thu, Jan 16, 2025 at 10:15 PM Matteo Golin wrote: > Hello everyone, > > I am working on writing drivers for some of InSpace's new sensors for our > hybrid control system. Of these sensors, one > of them is the MCP9600 t

Extending UORB for thermocouples

e any other suggestions for me, please let me know. I'll probably reach out again in this thread once I get started with the implementation. Thank you! -- Matteo Golin signature.asc Description: PGP signature

Re: Bisecting with NuttX to find bugs

istorical data is kept only for the past 16 days > (2) I need to provide a scriptable way to export the data > > Lup > > On Fri, Jan 17, 2025 at 5:49 AM Matteo Golin > wrote: > > > Hello everyone, > > > > I am working on this issue about the W5500-EVB-Pico: &

Bisecting with NuttX to find bugs

problem because this board depends on the Pico SDK being of a certain version, but that is much easier since I am able to just check out to a specific version like 1.4.0 and rebuild. Anyone who regularly bisects on NuttX, can you tell me how you get around this issue? -- Matteo Golin

Re: Raspberry Pi 4B Preliminary Support

cessary in actuality, like the `bcm2711-rpi-4-b.dtb`, but I haven't tested that yet. Good point! Matteo On Tue, Dec 17, 2024 at 09:09:46PM +0100, Tomek CEDRO wrote: > On Tue, Dec 17, 2024 at 7:35 PM Matteo Golin wrote: > > Hi Tomek, > > Although some of the specs between the two b

Re: Raspberry Pi 4B Preliminary Support

nying I/O board with things like HDMI and Ethernet ports, and my guess would be that HDMI/Ethernet drivers for the Pi 4 would also work on the Compute 4, although that would need testing! On Tue, Dec 17, 2024 at 02:32:32PM -0500, Nathan Hartman wrote: > On Tue, Dec 17, 2024 at 11:32 AM Matt

Re: Raspberry Pi 4B Preliminary Support

isible tomorrow when the next build runs. On Tue, Dec 17, 2024 at 06:22:47PM +0100, Tomek CEDRO wrote: > On Tue, Dec 17, 2024 at 5:32 PM Matteo Golin wrote: > > Yesterday my PR was merged to add preliminary support for the BCM2711 chip > > and Raspberry Pi 4B board. > > You can

Raspberry Pi 4B Preliminary Support

Hello everyone, Yesterday my PR was merged to add preliminary support for the BCM2711 chip and Raspberry Pi 4B board. You can take a look here if you'd like to see the changes: https://github.com/apache/nuttx/pull/15188 Thanks again to all the reviewers who helped me learn some of the build pro

Carleton University InSpace Preliminary Design Review

tro - 6:10PM - Avionics Deployment Electronics - 6:20PM - Telemetry System - 7:50PM - Hybrid Rocket Motor Control System Thank you for your consideration and InSpace hopes to see some of you there! We're very excited to be using NuttX! -- Matteo Golin Avionics Lead Carleton University InSpace

Re: Re: Power safe file systems for NuttX

were created you can format it from the NSH> command > line. > > BR, > > Alan > > On Tue, Oct 29, 2024 at 6:17 PM Matteo Golin > wrote: > > > While we try to get that working, this would require that the SD card be > > formatted in advance, right? I would

Re: Re: Power safe file systems for NuttX

t; > > > > > > https://github.com/apache/nuttx/blob/master/include/nuttx/fs/partition.h#L81 > > > to register partitions as block devices again, so you can mount the > > > different file systems on these new block devices. > > > > > > Thanks >

Re: Power safe file systems for NuttX

I got my hands on a SPI SD card adapter and managed to try out SD/MMC support for it through NuttX on my Pico. FAT file systems worked with no problem, and after a little configuring I managed to get littlefs going as well. Now I'm wondering if NuttX has support for multiple partitions on the sa

Power safe file systems for NuttX

Hello everyone, Matteo from InSpace again with more questions. We are currently in the process of selecting some non-volatile memory for our telemetry system so that we can log our flight data while our rocket is in the air. We're having some trouble settling on an option because of a few uncom

USB serial communication for RP2040

Hello everyone, I am attempting to create an embedded device for a school project where I need to send some text data over USB on power-up. It is a constant stream of serial data. For this, I am setting my own application as the entry point instead of NSH, which requires me to instantiate the U

Re: [WARNING] All NuttX builds to be turned off by October 30th UNLESS...

ly that branch / tag that changed, no need to rebuild all > > the documentation all the time including older releases that did not > > change. > > 2. Improve artifacts upload to the web server. > > > > Tomek > > > > > > On Wed, Oct 16, 2024 at 7

Re: [WARNING] All NuttX builds to be turned off by October 30th UNLESS...

Matteo On Wed, Oct 16, 2024 at 1:09 PM Alan C. Assis wrote: > Exactly! > > I think if no file at nuttx/Documentation/ was modified we don't need to > compile it. > > BR, > > Alan > > On Wed, Oct 16, 2024 at 1:25 PM Matteo Golin > wrote: > > > I also thin

Re: [WARNING] All NuttX builds to be turned off by October 30th UNLESS...

I also think we can use the "paths" filter to only rebuild docs when the documentation files are changed, similar to how it is done in the Docker-Linux workflow. On Wed, Oct 16, 2024 at 12:20 PM Matteo Golin wrote: > It may not be ideal, but would it be possible to change the

Re: [WARNING] All NuttX builds to be turned off by October 30th UNLESS...

It may not be ideal, but would it be possible to change the documentation builds to only occur periodically? I noticed that the doc builds take roughly ~13 minutes, and if they run on each PR merge that will add up quickly. GitHub actions appears to allow scheduled actions: https://docs.github.

Re: [VOTE] Apache NuttX 12.7.0 RC0 release

Hello, I am not entirely clear how to participate in the release vote, I will have to review the linked information again, but I have noticed that the Pico W is not able to connect to a wireless network because of an issue that was previously encountered a few releases ago. I am investigating this

Re: UART based peripheral driver

a virtue; creative > inconsistency is destructive to the integrity of the OS. Please do not > go the naive way that you are considering. That kind of change would > certainly be rejected (I hope). > > On 10/1/2024 7:33 AM, Matteo Golin wrote: > > Thank you for the help everyon

Re: UART based peripheral driver

Thank you for the help everyone! I have some follow-up questions: > You should use the struct file instance to access the driver, not the raw > driver interface. Greg, can you clarify what you mean? My understanding is that it would be preferred that I use `file_open()` to get the struct file

Re: Questions about STM32 support/programming

Thank you everyone for the responses, lots to consider. I'll have some of our members look into reading the STM32 datasheets to check for information about whether or not the particular chip(s) we're interested will ship with DFU support or not. We're trying to make the use of this board as easy

UART based peripheral driver

Hello, InSpace uses a radio module for our telemetry systems called the RN2483, which is a LoRa radio chip that has a UART interface. I would like to have a device driver on NuttX for this module, so I am having some of the students try experimenting with creating one to get an idea of how to w

Re: Amateur Rocketry Team Contributors

Thank you everyone for the support! Regarding the blog posts, we will be sure to record lots of media material throughout the year for us to include if that is something to be pursued. Alan, thank you for the link to PSAS! Some of our members have told me they have heard of this team; their wor

Questions about STM32 support/programming

Hello all, InSpace is considering using an STM32 chip as the MCU for our flight computer this year. We're building a custom board around the chip for our specific application. We're considering the STM32 family because it's popular among rocketry teams and is often used in flight computers. In

Amateur Rocketry Team Contributors

Hello everyone, My name is Matteo, and I am a lead on Carleton University's rocketry engineering design team (called CU InSpace). We're based out of Ottawa, Canada and we design and build high powered sounding rockets every year. We typically fly two rockets each year, one at the Spaceport Ameri

Re: Help wanted!

Hello Nathan, I'd be interested in helping out where I can. Is there a list of steps/processes that normally go into a PR review so that I could reference something while reviewing to make sure I don't miss anything important? Or is the review process more on a per-PR basis of deciding what to che

Re: RP2350 port

Thanks for getting it working! I'd like to try out NuttX on the new Picos, so I'm excited development has started so quickly! Not much advice for the other questions, but for number 2 maybe there could just be a raspberry-pi-pico2 board and the selection between ARM and RISCV is done via Kconfig?

Re: aarch64 boot crash when printing non-static string

r the Raspberry Pi. I could have sworn I had tried this address already, but must have forgotten a 0. Thank you for your help again, -- Matteo Golin B. Eng Computer Systems Student signature.asc Description: PGP signature

Re: aarch64 boot crash when printing non-static string

try to add "static" to your strings that you are trying to print, so those > will be not placed on stack (not sure if they are now). If you confirm that > the issue is with printing strings located on stack then you can focus on > making sure that stack pointer is pointing

aarch64 boot crash when printing non-static string

Hello all, I've been working on this problem for a while now and I'm not quite sure how to progress in my troubleshooting. I am trying to port NuttX to the Raspberry Pi 4B, which has been going well thanks to the documentation suggestions from my previous email (especially Lup's blogs which have

Re: Guides for understanding the kernel

; > > > > The blog of Lup Yuen LEE is a very valuable resource. Lup did a port > of > > > > NuttX to PinePhone, which is a 64-bit architecture that could be said > > to be > > > > on a similar level to RPi 4B. > > > > > > > > Th

Guides for understanding the kernel

Hello all, I am working on a port for NuttX to the Raspberry Pi 4 Model B, for which I am using Gregory's previous port to the BCM2708 as a reference. I've read through the documentation available here to get a better grasp of how NuttX works "under the hoo

Re: Improving NuttX Awareness

s and people that could be interested in > embedded systems. > > BR, > > Alan > > On Wed, Jul 10, 2024 at 5:47 PM Matteo Golin > wrote: > > > Maybe we could consider creating a Reddit community? It's a nice forum > for > > discussion and very easily sear

Re: Improving NuttX Awareness

Maybe we could consider creating a Reddit community? It's a nice forum for discussion and very easily searchable on Google. That would help in accumulating solutions to common difficulties people encounter. On Tue, Jul 9, 2024, 4:20 PM Alan C. Assis wrote: > I used a "tutorial" / documentation l