Architecture : anax and hzn binaries for RISC-V microprocessor architecture

[johnwalicki]

Open a issue in the Anax repo to update the agent-install.sh with the new microprocessor architecture.

Feature Request: Update agent-install.sh to support the RISC-V microprocessor architecture #4122

Open a issue in the Anax repo to update the Makefiles with the new microprocessor architecture.

Feature Request: update the anax Makefiles to support the RISC-V microprocessor architecture #4123

Open a issue in the Anax repo to add the agent binaries to edgeNodeFIles.sh so they publish to CSS

Feature Request: Add risc-v agent binaries to edgeNodeFIles.sh so they publish to CSS #4124

Open a issue in the Anax repo to update the Dockerfiles to build on the new microprocessor architecture.

Let's skip the Dockerfiles in the initial bootstrap of RISC-V edge support.

Open a issue in the Anax repo to add the build pipelines so it arrives in GitHub Releases

This is dark magic that @bencourliss knows how to do.

Open a issue in the Documentation repo to update the docs for this new microprocessor architecture.

Documentation: RISC-V documentation updates #223

New microprocessor architecture Support Checklist

• [X] Update the agent-install.sh
• [X] Update the Makefiles
• [X] Update the agent binaries
• [X] Update the Dockerfiles
• [X] Update the build pipelines
• [X] Validate Examples on this new microprocessor architecture
• [X] Documentation updates to support this new microprocessor architecture
• [X] Test / Validate and modify existing tests for the anax binary on this microprocessor architecture

[johnwalicki]

As discussed on the July 29 2024 Open Horizon TSC meeting, Intensivate and others are interested in Open Horizion support of RISC-V. Support starts with compiling the anax and hzn binaries for riscv64

The above tickets will drive the required changes needed to bootstrap new microarchitecture support.

[johnwalicki]

@joewxboy @dlarson04 This will be an interesting investigation!

[joewxboy]

From Intensivate:

I don't think there is a particular board or device that would need to be tested on, if you're able to get it running on a SiFive or other SBC, we shouldn't have issues having it run on our hardware. One thing is that we're using Fedora 38 and Ubuntu 24.04 with 6.8.10 kernel based on popularity and feedback we've been given. There may be compatibility tweaks we would need to do if the distro is different and something we need to evaluate.