NuttX is a POSIX compliant UNIX-like RTOS with a bunch of features:
https://nuttx.apache.org/docs/latest/introduction/about.html
It has been ported (partially?) to the Duo S:
With possible support for SG2002 boards and the 700MHz C906 core:
" * We might run NuttX on the SG2000 Co-Processor (Plus SG2002 with its upsized TPU / NPU)"
Very exciting!
NuttX has devices like Linux doesn’t it? /dev/…
I have not done any NuttX development. Would it would be easy to create device streams between the Linux core and the NuttX (Co-Processor) core?
I’m thinking you could offload GPIO functions and protocols like 1-Wire, and ModBus to NuttX, then communicate back to Linux via device drivers.
A couple of questions for and thanx to Lup Yuen
I’ve been slowly working background on baremetal for SG2000. I’ve got a very simple bootloader that bypasses the need for U-Boot. it uses a FAT based uSD that is easy to create and modify.
I had planned using FreeRTOS but with my need for powerful Ethernet and USB i’m pretty sure NuttX will be a better base. Both would require R&D on drivers for those two devices along with SDMMC.
I’m pretty confident I can solve the technical issues with time but not sure my skills will be in tune with NuttX mainstream integration.
Any other info on these peripherals and NuttX would be appreciated.
I finally got NuttX to compile today on a Fedora Server running in VirtualBox on Windows 11. I’d like to move it over to development under VS Code on Windows 11.
I have Lep Yuen’s daily build downloaded and also the compiled and built image from the mainline.
I’m a little confused on some of the steps/needs for the U-Boot TFTP solution. Is it POSSIBLE to load the image directly from MMCSD into 0x80200000 and then “go 0x80200000”.
I’ve done the load, examined some memory with u-boot and tried the “go”. no joy. i’m setting up tftp now to test that. The initrd is inside the image. Do i still have to load the fdt to satisfy u-boot?
Any other gotcha’s anyone’s aware of?
Thanx,
Ed