39 6 Kmem
20971520 720896 20250624 20250624 Page
StarPro64 Log:
https://gist.github.com/lupyuen/8f40ebacb22da08039be3b854d7837de
Lup
On Mon, Jun 30, 2025 at 7:22 PM Lee, Lup Yuen wrote:
> +1 for Avaota-A1, Milk-V Duo S, Ox64, Star64, PinePhone
>
>
+1 for Avaota-A1, Milk-V Duo S, Ox64, Star64, PinePhone
= Avaota-A1 Compiler
+ aarch64-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=aarch64-none-elf-gcc
COLLECT_LTO_WRAPPER=/home/luppy/arm-gnu-toolchain-13.2.Rel1-x86_64-aarch64-none-elf/bin/../libexec/gcc/aarch64-none-elf/13.2.1/lto-wrapp
+1
Hi Donny: Please remember to close the voting in 72 hours. Thanks :-)
Lup
On Mon, Apr 14, 2025 at 9:07 PM 董九柱 wrote:
> Hello Community,
>
> I submit some PRs about using system/dd app instead of dd command from
> nshlib.
>
> PR link:
> https://github.com/apache/nuttx-apps/pull/3057
> https:
+1 for Milk-V Duo S, Ox64, Star64, PinePhone
= Milk-V Duo S Compiler
+ riscv-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv-none-elf-gcc
COLLECT_LTO_WRAPPER=/Users/luppy/xpack-riscv-none-elf-gcc-13.2.0-2/bin/../libexec/gcc/riscv-none-elf/13.2.0/lto-wrapper
Target: riscv-none-elf
Confi
Hi YF: `rv-virt:python` builds OK with Ubuntu 24.04.2 LTS and the Official
NuttX Docker Image (containing xPack GCC 13.2.0). Here's the Build Log:
https://gist.github.com/lupyuen/21167fe02656b89632d3cce54aa23024
Hi Tiago: Is there a specific version of the toolchain that's needed for
`rv-virt:pyth
<< I can boot into NSH but when running python, it crashed. >>
Hi YF: QEMU 8.2.2 + NSH + Python works OK for me (I built `rv-virt:python`
with Docker + Ubuntu). Here's the QEMU Log:
https://gist.github.com/lupyuen/31db63ccfaf0e07c45ba0059814e0fd7
NuttShell (NSH) NuttX-12.9.0
nsh> uname -a
NuttX
+1 for Milk-V Duo S, Ox64, Star64 and PinePhone
= Milk-V Duo S Compiler
+ riscv-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv-none-elf-gcc
COLLECT_LTO_WRAPPER=/Users/luppy/xpack-riscv-none-elf-gcc-13.2.0-2/bin/../libexec/gcc/riscv-none-elf/13.2.0/lto-wrapper
Target: riscv-none-elf
Co
+1
Lup
On Mon, Apr 7, 2025 at 5:13 PM 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.
This article explains how we ported NuttX from QEMU Arm64 Kernel Build to
PINE64 Yuzuki Avaota-A1 SBC based on Allwinner A527 SoC ... Completed
within 24 Hours!
(1) Anyone porting NuttX from QEMU to Real SBC? This walkthrough shall be
mighty helpful!
(2) Avaota-A1 SBC is Open Source Hardware (CER
Earlier we created a PR Test Bot that will Build and Test the Pull Requests
for NuttX. Our Test Bot kicks into action when we post a PR Comment...
## For Oz64 SG2000 RISC-V SBC
@nuttxpr test oz64:nsh
## For QEMU Emulator: Arm64 and RISC-V
@nuttxpr test qemu-armv8a:netnsh
@nuttxpr test r
StarPro64 EIC7700X is the (literally) Hot New RISC-V SBC by PINE64. In this
article we chat about:
(1) ESWIN EIC7700X, the RISC-V SoC inside StarPro64
(2) Its Neural Processing Unit (NPU) that supports Large Language Models
(LLM)
(3) NuttX boots OK on StarPro64 and passes OSTest! (Multiple Harts
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 should filter out breaking code as much as possible also
on
> our side.
+1 Tomek
+1 Alin
+1 Tiago
+
ry
Pi). Without Manually Swapping the MicroSD! :-)
Lup
On Sun, Feb 23, 2025 at 9:16 AM Tomek CEDRO wrote:
> On Sat, Feb 22, 2025 at 10:27 PM Lee, Lup Yuen wrote:
> > Last week we saw our new Test Bot for NuttX Pull Requests. When we post
> this PR Comment, it will Build and Test the Pul
t; >
> > > > I think that we all should push the logs as they are on
> > > > https://gist.github.com/nuttxpr in separate folders containing
> > > > build target (ex: arm-01) with logs renamed : platform_buildtime.log
> > > > or
> > > > platform/board/config wi
Sorry I'm taking a break from GSoC this year :-) Last GSoC was horribly
stressful, this year I'll focus on NuttX CI.
I compiled some GSoC Tips here: https://github.com/apache/nuttx/issues/11957
Lup
On Thu, Feb 13, 2025 at 8:05 AM Tomek CEDRO wrote:
> On Wed, Feb 12, 2025 at 7:45 PM Tiago Medic
1: +1
2: +1
3: +1
4: +1
5: +1
6: +1
7: +1
8: +1
9: +1
10: +1
11: +1
12: +1
13: +1
14: +1
15: +1
16: +1
17: +1
Thanks :-)
Lup
On Tue, Feb 11, 2025 at 7:39 AM Tomek CEDRO wrote:
> Hello world :-)
>
> As discussed extensively in various mailing list threads we have
> gathered all additional ideas
for the resource!
> Matteo
>
> On Thu, Jan 16, 2025 at 6:01 PM Lee, Lup Yuen wrote:
>
> > Hi Matteo: Wonder if the NuttX Build History will help? For every past
> > build, it shows the Commit Hashes for the NuttX Repo and NuttX Apps:
> >
> >
> >
> https
Hi Matteo: Wonder if the NuttX Build History will help? For every past
build, it shows the Commit Hashes for the NuttX Repo and NuttX Apps:
https://nuttx-dashboard.org/d/fe2q876wubc3kc/nuttx-build-history?from=now-6M&to=now&timezone=browser&var-arch=$__all&var-subarch=$__all&var-board=w5500-evb-pi
tself with GitLab Community Edition.
Though it might be biased: https://forgejo.org/compare/
Lup
On Sun, Jan 12, 2025 at 8:01 AM Tomek CEDRO wrote:
> On Sat, Jan 11, 2025 at 11:02 PM Lee, Lup Yuen wrote:
> > What is Forgejo? Think GitHub… But Open-Source and Self-Hosted! Forgejo
> is
<< I was wondering if PR can be easily "forwarded from external mirror to
the upstream repo" or needs to be re-created manually based on git commits
>>
Hi Tomek: I'm guessing we could call the GitHub API? Needs more research
and testing :-)
I wrote about GitHub Coexistence:
https://lupyuen.org/ar
;s writable Git
repositories.
...
- ASF projects must house their project code in ASF supported services
(Subversion, GitBox).
>>
Lup
On Sun, Jan 12, 2025 at 11:06 AM Gregory Nutt wrote:
>
> On 1/11/2025 6:00 PM, Tomek CEDRO wrote:
> > On Sat, Jan 11, 2025 at 11:02 PM Lee, Lup Yu
What is Forgejo? Think GitHub… But Open-Source and Self-Hosted! Forgejo is
a Git Forge, the server code that will publicly host and share a Git Repo.
(Including our NuttX Repo)
In this article, we talk about Forgejo Git Forge, and whether NuttX could
possibly switch from GitHub to a self-hosted Gi
2 Weeks Ago: We saw a Runtime Bug in the NuttX CI Test. We think that the
Breaking Commit (causing the bug) falls somewhere between these “Good” and
“Bad” Commits...
That’s 468 Commits! Which one is the Breaking Commit?
In this article: We run Git Bisect to find the Breaking Commit
automatically,
+1 for Milk-V Duo S (SG2000), Ox64 (BL808) and PinePhone
= Milk-V Duo S Compiler
+ riscv-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv-none-elf-gcc
COLLECT_LTO_WRAPPER=/Users/luppy/xpack-riscv-none-elf-gcc-13.2.0-2/bin/../libexec/gcc/riscv-none-elf/13.2.0/lto-wrapper
Target: riscv-no
We’re on a 50 km overnight hike. NuttX Build Farm runs non-stop all day,
all night. Continuously compiling over 1,000 NuttX Targets.
Can we be 100% sure that NuttX is OK? Without getting spammed by Alert
Emails all night? In this article: Mastodon becomes a fun new way to
broadcast NuttX Alerts in
NuttX Dashboard has been flagging this CI Bug for a month: "rv-virt/citest:
test_helloxx FAILED"
The Bug Stops Here! In this article: We study the internals of the NuttX CI
Test as we stomp the bug:
(1) We run the CI Test on Docker
(2) Snoop and Study the CI Test Internals
(3) Locate and Dump the
Today we have a barebones port of NuttX to Sophgo SG2000 RISC-V SoC. But
many drivers are missing: GPIO, WiFi, Ethernet, MIPI CSI / DSI, ...
https://lupyuen.github.io/articles/sg2000
Pine64 has offered to sponsor some Oz64 SG2000 SBCs for porting these
drivers: https://pine64.org/documentation/Oz6
farm.. Your https://nuttx-dashboard.org/ is already working so we are
> > prepared now for worst case scenario.. I am sure this project will
> > grow and bring not only build but also functional testing soon and
> > this will result in even better NuttX implementations :-)
> >
; >
> > please add to the guide
> > "gh auth login" so that users can upload the results
> >
> > Best regards
> > Alin
> >
> >
> > On Mon, Oct 28, 2024 at 9:12 AM Lee, Lup Yuen wrote:
> >
> >> << please add to the guide
Jerpelea wrote:
> Hi Lup,
>
> please add to the guide
> "gh auth login" so that users can upload the results
>
> Best regards
> Alin
>
>
> On Mon, Oct 28, 2024 at 9:12 AM Lee, Lup Yuen wrote:
>
> > << please add to the guide "apt instal
> Best regards
> Alin
>
> On Mon, Oct 28, 2024 at 8:50 AM Lee, Lup Yuen wrote:
>
> > Thanks Alin, I think the fix is here:
> > https://github.com/apache/nuttx/pull/14527
> >
> > Lup
> >
> > On Mon, Oct 28, 2024 at 3:43 PM Alin Jerpelea
> wr
> > ARCH_CHIP_STM32 && ARCH_ARM with value n, but is currently being
> > y-selected
> > by the following symbols:
> >
> >- STM32_STM32F33XX (defined at arch/arm/src/stm32/Kconfig:1533), with
> > value y, direct dependencies ARCH_CHIP_STM32 &&
> > Building NuttX...
> > > /usr/bin/bash: line 1: genromfs: command not found
> > > make[3]: *** [Makefile:50:
> > > /awork/nuttx/NuttX/farm/apps/examples/posix_spawn/filesystem/romfs.img]
> > > Error 127
> > > make[3]: Target 'all' not remade b
]: *** [Makefile:52:
> /awork/nuttx/NuttX/farm/apps/examples/posix_spawn_all] Error 2
> make[1]: Target 'all' not remade because of errors.
> make: *** [tools/LibTargets.mk:232: /awork/nuttx/NuttX/farm/apps/libapps.a]
> Error 2
> make: Target 'all' not remade be
us?
>
> 3) Regarding M1 macs not being able to run the CI builds, I suggest to
> state that as a call to action, e.g., help wanted to make the build succeed
> on M1 macs, please see such-and-such issue on github...
>
> Otherwise looks good and thanks again!
>
> Cheers
Thanks Alin, that's great! Lemme know if you have any problems with the
build, Docker makes it really easy :-)
Lup
On Sun, 27 Oct 2024, 8:20 am Alin Jerpelea, wrote:
> Hi Lup,
> I offered to run all builds locally for us every day
> Best regards
> Alin
>
> On Sun, 27 O
Refurbished Ubuntu PCs have become quite affordable. Can we turn them into
a (Low-Cost) Build Farm for NuttX?
In this article we…
(1) Compile NuttX for a group of Arm32 Boards
(2) Then scale up and compile NuttX for All Arm32 Boards
(3) Thanks to the Docker Image provided by NuttX
(4) Why do this?
+1 for Milk-V Duo S, Ox64, Star64, PinePhone
= Milk-V Duo S Compiler
+ riscv-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv-none-elf-gcc
COLLECT_LTO_WRAPPER=/Users/luppy/xpack-riscv-none-elf-gcc-13.2.0-2/bin/../libexec/gcc/riscv-none-elf/13.2.0/lto-wrapper
Target: riscv-none-elf
Confi
ons Artifacts API
> v4, as earlier API versions will be removed after November 30th.
>
> I hope this helps other projects that face similar CI challenges as Pulsar
> has. Please let me know if you need any help in using a similar solution
> for your Apache project's CI.
>
&g
Hi All: We have an ultimatum to reduce (drastically) our usage of GitHub
Actions. Or our Continuous Integration will halt totally in Two Weeks.
Here's what I'll implement within 24 hours for `nuttx` and `nuttx-apps`
repos:
(1) When we submit or update a Complex PR that affects All Architectures
(A
Yep lemme do some analysis and make some recommendations. Thanks.
Lup
On Wed, 16 Oct 2024, 11:16 pm Alan C. Assis, wrote:
> Hi Lup,
>
> Please take a look.
>
> BR,
>
> Alan
>
> -- Forwarded message -
> From: Daniel Gruno
> Date: Wed, Oct 16, 2024 at 12:08 PM
> Subject: [WARNING
Hi All: We're rolling out enhancements to the CI Workflow, to skip the
unnecessary NuttX Builds for PRs. Right now we wait for the CI Builds to
complete across All Architectures (Arm32, Arm64, RISC-V, Xtensa), even
though our PR modifies a Single Architecture. With the enhancements, the CI
Workflow
+1 for Milk-V Duo S, Ox64, Star64 and PinePhone
= Milk-V Duo S Compiler
+ riscv-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv-none-elf-gcc
COLLECT_LTO_WRAPPER=/Users/luppy/xpack-riscv-none-elf-gcc-13.2.0-2/bin/../libexec/gcc/riscv-none-elf/13.2.0/lto-wrapper
Target: riscv-none-elf
Co
We're experimenting with an LLM Bot (Large Language Model) that will review
NuttX Pull Requests. This article explains how we created the LLM Bot in
One Week:
(1) We call GitHub API to fetch NuttX Pull Requests
(2) Append the PR Body to the NuttX PR Requirements
(3) Which becomes the LLM Prompt th
e plans to make many blogs using the Milk-V Duo S and Nuttx, because
> > one of company that i work is Milk-V Duo S seller in Brazil.
> >
> > I have some questions, (still not read the blogs, thanks again)
> >
> > Wifi Working ? Ble ? and Ethernet ?
> >
>
Hi Miguel: Here are the steps for booting NuttX on Milk-V Duo S SBC (Sophgo
SG2000 SoC):
https://nuttx.apache.org/docs/latest/platforms/risc-v/sg2000/boards/milkv_duos/index.html
Please see below for the articles I wrote about NuttX on Milk-V Duo S.
Lemme know if you have any questions thanks :-)
Job for Build and
Test. Please check out the discussion below.
Lup
On Wed, Sep 11, 2024 at 11:02 PM Lee, Lup Yuen wrote:
> << For PRs, depending on the directory (directories) of the modified
> file(s), pick and choose which tests to run. >>
>
> Thanks Nathan for the
emains to be seen how much impact that could actually cause. This can be
> addressed in various ways, which we can discuss if it becomes a problem in
> practice.
>
> Thoughts?
>
> Cheers,
> Nathan
>
> On Tue, Sep 10, 2024 at 9:51 AM Lee, Lup Yuen wrote:
>
> > Thi
This article explains how we're running Continuous Integration with GitHub
Actions. Every NuttX Pull Request will trigger 1,594 NuttX Builds!
https://lupyuen.codeberg.page/articles/ci.html
In my next message: I'll discuss how we might cut down the NuttX Builds for
Continuous Integration. Stay Tun
My student Rushabh Gala has just completed his project for Google Summer of
Code, on creating Safer Rust Apps for NuttX.
In this article we walk through Rushabh’s contributions, and understand how
we’re evolving Rust Apps for NuttX:
(1) Blinking the LED in Rust
(2) Handling Errors returned by Nutt
Hi Yanfeng and Alan: I have been running Daily OSTest for NuttX QEMU
RISC-V, hosted on GitHub Actions:
(1) OSTest for 32-bit QEMU RISC-V runs OK on GitHub Actions:
32-bit Flat Build (rv-virt:nsh):
https://github.com/lupyuen/nuttx-riscv64/actions/workflows/qemu-riscv-nsh.yml
32-bit Kernel Build (r
ss to learn how to
> initialize the CPU properly, and then apply that knowledge to boot
> NuttX. I can't seem to find it right now, but definitely look through
> the blog because you'll find a lot of helpful techniques there.
>
> Cheers,
> Nathan
>
> On Thu, Jul 25, 2024
Hi Matteo: Please lemme know if you have any questions about NuttX on
PinePhone (Arm64 Cortex-A53)
(Thanks Nathan :-)
Lup
On Thu, Jul 25, 2024 at 9:34 PM Nathan Hartman
wrote:
> Hi Matteo,
>
> The blog of Lup Yuen LEE is a very valuable resource. Lup did a port of
> NuttX to PinePhone, which i
+1 for Milk-V Duo S, Ox64, Star64 and PinePhone
= Milk-V Duo S Compiler
+ riscv-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv-none-elf-gcc
COLLECT_LTO_WRAPPER=/Users/luppy/xpack-riscv-none-elf-gcc-13.2.0-2/bin/../libexec/gcc/riscv-none-elf/13.2.0/lto-wrapper
Target: riscv-none-elf
Co
+1 for Milk-V Duo S, Ox64, Star64 and PinePhone
= Milk-V Duo S Compiler
+ riscv-none-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv-none-elf-gcc
COLLECT_LTO_WRAPPER=/Users/luppy/xpack-riscv-none-elf-gcc-13.2.0-2/bin/../libexec/gcc/riscv-none-elf/13.2.0/lto-wrapper
Target: riscv-none-elf
Co
Hi All: I'm very sorry for the delay. Let me explain what Rushabh is doing,
under my close supervision. He listed these GSoC Tasks in his post:
<< Ported the LED Blinky App from C to Rust >>
The means Rushabh took the `leds` Example in C, and created a New Example
in Rust called `blink_rust`: htt
Hi Rushabh: Thank you so much for your kind words, excellent feedback and
awesome contributions to NuttX Kernel and Apps!
I'll definitely work harder to make NuttX Onboarding easier for new
learners :-)
Lup
On Mon, Jul 8, 2024 at 6:37 PM RUSHABH GALA wrote:
> Greetings everyone!
>
> I am Rusha
nice Lup!
>
> Another great article! I want to test my Milk-V Duo S soon!!!
>
> BR,
>
> Alan
>
>
> On Sat, Jul 6, 2024 at 7:18 PM Lee, Lup Yuen wrote:
>
> > Earlier this year we made a RISC-V Emulator for Ox64 BL808 SBC. Every day
> > we run it for tes
Earlier this year we made a RISC-V Emulator for Ox64 BL808 SBC. Every day
we run it for testing the Daily NuttX Build for Ox64, thanks to our
customised TinyEMU RISC-V Emulator. (Not the small flightless bird)
Now that NuttX supports Sophgo SG2000 SoC: Let’s create a similar emulator
for Pine64 Oz
Last week we upstreamed Milk-V Duo S SBC to NuttX Mainline. (Based on
Sophgo SG2000 RISC-V SoC) But NuttX Mainline changes every day. Will Milk-V
Duo S suffer “Software Bit Rot”? And fail to boot NuttX someday?
Let’s do Daily Automated Testing for NuttX on a Milk-V Duo S. Yep on the
Actual Physica
Hi Mark: Thanks for watching my presentation! To show the Heap Logs, I
enabled "Build Setup > Debug Options > Enable Debug Features > Memory
Manager Debug Features". Here's the complete definition (I hope it's
applicable to your platform)...
<<
Symbol: DEBUG_MM_INFO
Type : boolean
Prompt: Memory
Thanks YF! That's a very cool concept for RISC-V code: 64-bit architecture
with 32-bit pointers. In case we need to use RV64ILP32 for NuttX, do you
happen to have the patched source code to support RV64ILP32?
Your recent PRs are very interesting, perhaps other folks here might like
to comment:
Cl
gt; Kudos Lup!
>
> Fantastic work! And nice board to run NuttX
>
> On Sat, May 18, 2024 at 7:50 PM Lee, Lup Yuen wrote:
>
> > Soon we’ll see many new 64-bit RISC-V SBCs based on the Sophgo SG2000
> > RISC-V SoC. Will they boot NuttX? Let’s find out…
> >
>
Soon we’ll see many new 64-bit RISC-V SBCs based on the Sophgo SG2000
RISC-V SoC. Will they boot NuttX? Let’s find out…
(1) We boot Linux on Milk-V Duo S (with SG2000)
(2) Peek inside SG2000 Linux and observe how it boots
(3) Then we take NuttX for RISC-V (Ox64 BL808)
(4) Tweak NuttX Kernel to
Will Rust Apps run on a 64-bit RISC-V SBC? Like Ox64 BL808 SBC? Let’s find
out!
(1) We take a Barebones Rust App (“Hello World!”)
(2) Compile it for QEMU RISC-V Emulator (64-bit)
(3) Run it on QEMU Emulator with NuttX
(4) Do the same on Ox64 BL808 SBC (via MicroSD)
(5) We’ll discuss the Quirky
Thank you so much Greg! I'll copy and paste the relevant sections into the
NuttX Docs.
Lup
On Fri, May 3, 2024 at 10:04 PM Gregory Nutt wrote:
> On 5/3/2024 2:12 AM, Lee, Lup Yuen wrote:
> > https://lupyuen.github.io/articles/pr#check-coding-style
> Nice article. This would b
Hi Janardhan: I have an article that explains the "nxstyle" tool, maybe
this will help?
https://lupyuen.github.io/articles/pr#check-coding-style
I'm not aware of a script that does auto-formatting for NuttX Code. I do it
manually in VSCode :-)
Lup
On Fri, May 3, 2024 at 3:24 PM Janardhan Silwal
Please welcome Mr Rushabh Gala to the NuttX Community!
He's a Third-Year Student at Mumbai University (Computer Science and
Engineering). For Google Summer of Code, I'll work with him on Rust Apps
for NuttX.
(Which includes the Rust Wrapper for the POSIX Functions in NuttX)
He's new to NuttX, so
een phosphor effect, how did you do it?
>
> Best Regards,
>
> Alan
>
> On Sat, Apr 20, 2024 at 7:41 PM Lee, Lup Yuen wrote:
>
> > Last article we were compiling Rust Apps for NuttX QEMU (RISC-V 32-bit).
> > And we hit a baffling error…
> >
> > "C
Last article we were compiling Rust Apps for NuttX QEMU (RISC-V 32-bit).
And we hit a baffling error…
"Can't link Soft-Float modules with Double-Float modules"
Let’s solve the problem! In this article we dive inside the internals of
C-to-Rust Interop…
(1) Rust compiles for Soft-Float, NuttX expe
Hi Pavel: I'm sorry the GSoC Proposal Submission has closed last week.
Though Shijo is still keen to do NanoX on NuttX in his spare time.
I asked Shijo to bounce some ideas with you. If you could help him, that
would be great. Thanks :-)
Lup
On Tue, Apr 9, 2024 at 1:48 PM Pavel Pisa wrote:
> H
+1 for Ox64, Star64 and PinePhone
= Ox64 Compiler
+ riscv64-unknown-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv64-unknown-elf-gcc
COLLECT_LTO_WRAPPER=/Users/Luppy/riscv64-unknown-elf-toolchain-10.2.0-2020.12.8-x86_64-apple-darwin/bin/../libexec/gcc/riscv64-unknown-elf/10.2.0/lto-wrapper
es a kind of rosetta stone to interop basic rust with
> C and the usual toolchains, which I did not see anywhere else (I did not
> search for long).
>
> I'll keep it as a reference doc.
>
> Thanks,
>
> Sebastien
>
> Le 07/04/2024 à 00:56, Lee, Lup Yuen a écrit :
2024 at 8:39 PM Alan C. Assis wrote:
> Very nice article!
>
> I think it should be nice to take a look at the Rustix project again, it
> will avoid these 'extern "C" ' for each function on NuttX.
>
> BR,
>
> Alan
>
> On Sat, Apr 6, 2024 at 7:57 PM L
This article explains the current steps for running barebones Rust Apps on
NuttX and the challenges we faced:
(1) How we compile Rust Apps for NuttX
(2) Running NuttX and Rust Apps on QEMU RISC-V Emulator
(3) Console Input and Output for Rust on NuttX
(4) Software vs Hardware Floating-Point and wh
+1 for Ox64, Star64 and PinePhone
= Ox64 Compiler
+ riscv64-unknown-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv64-unknown-elf-gcc
COLLECT_LTO_WRAPPER=/Users/Luppy/riscv64-unknown-elf-toolchain-10.2.0-2020.12.8-x86_64-apple-darwin/bin/../libexec/gcc/riscv64-unknown-elf/10.2.0/lto-wrapper
Pine64's new PineVox Smart Speaker looks interesting, it runs on Bouffalo
Lab's BL606P 64-bit RISC-V SoC. Which is very similar to Ox64 BL808, so it
might boot NuttX!
https://www.hackster.io/news/pine64-enters-the-home-automation-sector-with-the-privacy-preserving-pinevox-smart-speaker-ac4d6e01460
While porting QuickJS to Ox64 BL808 SBC, we hit a Baffling Crash Dump on
NuttX. Which made us ponder...
Is there a better way to analyse a NuttX Crash Dump? Without scrolling
pages and pages of logs?
In this article, we create a real-time NuttX Log Parser that will:
(1) Extract the RISC-V Excepti
ocky to create NuttX
> applications!
>
> Best Regards,
>
> Alan
>
> On Sat, Feb 24, 2024 at 7:03 PM Lee, Lup Yuen wrote:
>
> > Remember MakeCode? BBC micro:bit and its Drag-n-Drop App Builder?
> MakeCode
> > for BBC micro:bit is an awesome creation that’s way
Remember MakeCode? BBC micro:bit and its Drag-n-Drop App Builder? MakeCode
for BBC micro:bit is an awesome creation that’s way ahead of its time (7
years ago!)
- TypeScript Compiler and Arm Assembler in the Web Browser (in JavaScript!)
- Custom Embedded OS (CODAL + Mbed OS)
- micro:bit Simulator in
QuickJS is a small JavaScript Engine that supports POSIX Functions. Can we
run QuickJS on NuttX? And Blink the LED in 4 lines of JavaScript?
const ULEDIOC_SETALL = 0x1d03;
const fd = os.open("/dev/userleds", os.O_WRONLY);
os.ioctl(fd, ULEDIOC_SETALL, 1);
os.ioctl(fd, ULEDIOC_SETALL, 0);
I
NuttX has an awesome driver for ROM FS Filesystem. What if we could
transplant the NuttX Driver and run it in a Web Browser, embedded in any
WebAssembly App?
Today we solve a hefty headache in our port of TCC Compiler to WebAssembly:
Missing C Header Files...
(1) We host the C Header Files in a RO
ld be nice if we could get TCC integrated on apps/ to run inside MCUs
> with much memory (like STM32 with external SDRAM), ESP32, BL808, etc.
>
> Best Regards,
>
> Alan
>
> On Sat, Feb 3, 2024 at 8:08 PM Lee, Lup Yuen wrote:
>
> > Today we're running NuttX Emul
Today we're running NuttX Emulator inside a Web Browser. What if we could
build and test NuttX Apps in the Web Browser? Learning NuttX becomes so
cool!
Let's explore with TCC (Tiny C Compiler) for 64-bit RISC-V, compiled to
WebAssembly with Zig Compiler...
(1) Zig Compiler compiles TCC Compiler t
> Congratulations, I think it could be very useful if integrated with CI.
>
> We could find many issues that aren't detected currently.
>
> Best Regards,
>
> Alan
>
> On Sat, Jan 27, 2024 at 8:05 PM Lee, Lup Yuen wrote:
>
> > Every day we’re auto-building
Every day we’re auto-building NuttX for Ox64 BL808 RISC-V SBC... Can we
test NuttX on Ox64 automatically after building?
Yes we can! With a little help from the Ox64 BL808 Emulator that we created
last week. In this article, we fill in the missing pieces of our Ox64
Emulator and run it for Automat
In olden times we had Computer Games (plus Operating Systems) on 5.25-inch
Floppy Disks. And we’d boot the Floppy Disks (clackety-clack) on Apple II
Computers with 64 KB RAM.
Today (40 years later) we boot microSD Cards (clickety-click) on Ox64 BL808
RISC-V Single-Board Computers with 64 MB RAM.
tigating it further!
> >
> > BR,
> > Alan
> >
> > On Mon, Jan 15, 2024 at 2:34 AM Lee, Lup Yuen wrote:
> >
> > > << Do you think it is possible to find an alternative to use the users'
> > > browser connection to communicate to the In
ver hosting the emulator.
>
> Do you think it is possible to find an alternative to use the users'
> browser connection to communicate to the Internet?
> This way it avoids users' consumption of all internet limits on the server
> side.
>
> BR,
>
> Alan
>
&g
tecture in future.
>
> [
> https://opengraph.githubassets.com/4259c40e0ffc51679b0d2f48e65e04e9821afb513a3d978f91a3fb2ceb8bb188/lupyuen/nuttx-ox64/releases/tag/nuttx-ox64-2024-01-11
> ]<https://github.com/lupyuen/nuttx-ox64/releases/tag/nuttx-ox64-2024-01-11
> >
> Release n
uctsim.com/login/
>
> Is it possible to get network enabled and use it to communicate? It could
> open new possibilities!
>
> BR,
>
> Alan
>
>
> On Sat, Jan 13, 2024 at 8:30 PM Lee, Lup Yuen wrote:
>
> > NuttX now boots and runs inside a Web Browser! (With We
NuttX now boots and runs inside a Web Browser! (With WebAssembly)
Try "ostest" here: https://lupyuen.github.io/nuttx-tinyemu
This article explains how we…
(1) Boot NuttX in the Web Browser with TinyEMU RISC-V Emulator
(2) Modify NuttX for HTIF Console (Berkeley Host-Target Interface)
(3) Explore
+1 for Ox64, Star64 and PinePhone
= Ox64 Compiler
+ riscv64-unknown-elf-gcc -v
Using built-in specs.
COLLECT_GCC=riscv64-unknown-elf-gcc
COLLECT_LTO_WRAPPER=/Users/Luppy/riscv64-unknown-elf-toolchain-10.2.0-2020.12.8-x86_64-apple-darwin/bin/../libexec/gcc/riscv64-unknown-elf/10.2.0/lto-wrapper
Happy New Year! 2024 is here and we’re running NuttX on Single-Board
Computers with plenty of RAM. Like Pine64 Ox64 BL808 SBC with 64 MB RAM!
In this article, we create a Blinky LED app with a Python-like,
Garbage-Collected Language that compiles to C: Nim Programming Language.
Garbage-Collected
on.
>
> I had intended to support 6LoWPAN with Bluetooth radios too, but never
> got around to it.
>
> On 12/16/2023 5:03 PM, Lee, Lup Yuen wrote:
> > Pine64 Ox64 BL808 (64-bit RISC-V SBC) is now supported in NuttX Mainline!
> > (Many thanks to my reviewers)
> >
> >
Pine64 Ox64 BL808 (64-bit RISC-V SBC) is now supported in NuttX Mainline!
(Many thanks to my reviewers)
Ox64 BL808 is an affordable $8 SBC with:
- 3 x RISC-V Cores (T-Head 64-bit / 32-bit)
- Networking: Ethernet, WiFi, Bluetooth LE, Zigbee
- Peripheral Interfaces: UART (Serial), I2C, SPI, USB, MIP
Hi yf: Kendryte K230 sounds really cool! (Dual-core T-Head C908 64-bit
RISC-V with NPU)
I'm now upstreaming to NuttX Mainline a similar board (Pine64 Ox64 SBC with
Bouffalo Lab BL808 SoC and T-Head C906). These links might be helpful:
PR for BL808 SoC: https://github.com/apache/nuttx/pull/11371
ards,
> yf
>
>
>
>
> Original
>
>
>
> From:"Lee, Lup Yuen"< lu...@appkaki.com >;
>
> Date:2023/12/10 7:11
>
> To:"dev"< dev@nuttx.apache.org >;
>
> Subject:[Article] NuttX on Ox64 BL808 RISC-V SBC: Fixed the UART
> Inter
gt;
> Unfortunately Pine 0x64 doesn't ship to Brazil (probably many buyers let
> the boards return after getting notified of higher taxes from Brazilian
> Customs).
>
> Best Regards,
>
> Alan
>
> On Sat, Dec 9, 2023 at 8:11 PM Lee, Lup Yuen wrote:
>
> >
Last week we walked through the Serial Console for Pine64 Ox64 BL808 64-bit
RISC-V Single-Board Computer. And we hit some illogical impossible problems
on NuttX for Ox64:
(1) Console Input is always empty. (Can’t enter any Console Commands)
(2) Interrupt Claim is forever 0. (Ox64 won’t tell us whi
1 - 100 of 207 matches
Mail list logo
