Research window: 2026-11-06 05:00 ~ 2026-11-09 05:00 (Beijing time, 72 hours, covering Saturday and Sunday).

Sources: Google News aggregation (30+ query sets in Chinese and English, via proxy), Hacker News, Phoronix, CNX Software, LinuxGizmos, Hackaday, the openRuyi official news page and main repository, website inspections of member companies of RISC-V International (391 companies), riscv100.top leaderboard inspections, WeChat official accounts and vendor websites, as well as commit and release searches on GitHub for organizations and key repositories including XiangShan, NEMU, GEM5, XSCache, difftest, CORE-V CVW/CVA6, DAMO XuanTie, ESWIN, Sophgo, Nuclei, Espressif, SpacemiT and spacemit-robotics, Sipeed, RevyOS, openRuyi-Project, and Radxa Linkr.


This Issue’s Index

  • Today’s Focus: Visinex Technology debuts the RISC-V edge vision chip VS815V — dual-core RISC-V plus fully domestic 22nm, targeting affordable 4K (announced 11-03, reported 11-06)
  • Today’s Focus: ESP32-S31 closes the “board” and “OS” gaps within a week — the Waveshare Zero board goes on sale, and full-featured Linux with MMU now runs (11-06/11-07)
  • I. Open Source Community and Software Ecosystem
    • openRuyi main repo kernel jumps to 7.3.3 and LTS 6.18.62, glibc upgraded to 2.44 with x86_64 added to testing (11-08)
    • CORE-V CVW merges 20 commits: removes two local branch predictors and BTB parameters, publishes RV32GC CoreMark/MHz of 4.33 (11-07)
    • XiangShan difftest wraps up five commits around matrix extensions: async verification draining, cycle scheduling moved down to the backend, matrix fingerprint switched to CRC32C (11-07/11-08)
    • RevyOS lands 20 kernel commits at once: debian_defconfig unifies six platforms, adds cross-architecture and native build CI (11-09)
    • Specula: an undergraduate writes an out-of-order RV32I core from scratch in Bluespec and turns the pitfalls into a long-form writeup (11-06)
  • II. Product and Ecosystem Developments
    • AMD Zen 6’s PMF trusted application moves to run on a RISC-V TEE, replacing the Arm core in the PSP (11-07)
    • Two SparkFun ESP32-P4 IoT RedBoards: one with a Wi-Fi 6 companion chip, one with PoE Ethernet (11-06)
    • LocalDot turns three generations of Echo Dot into Home Assistant voice terminals using ESP32-S3 plus ESP32-P4 (11-06)
  • III. Deep Dives on Domestic Teams
    • Espressif: the fifth Global Developer Conference held in Milan; MicroPixel brings an AI-native application system to low-cost chips (11-06)
    • SpacemiT: K3 heterogeneous multi-core self-test scripts enter the 7.3 branch, K3 power domain driver enters the wip branch (11-06/11-07)
    • Sophgo: sophon-tools’ se-rag-core ships four versions in a row, offline BM25 and registry retrieval take shape (11-07)
    • Nuclei: nuclei-sdk fixes evalsoc SMP boot synchronization, build system addresses REUSE and Windows path issues (11-06)
    • DAMO XuanTie: zero pushes to the open-source repo during the window; the community runs MicroPython on the T527’s E906 core (written 10-31, circulated 11-06)
    • Sipeed: NanoKVM merges the storage file manager UI, completing image and file exchange for KVM over IP (11-06)
  • IV. Special Chapter on Embodied Intelligence and Robotics
    • spacemit-robotics creates the ros2_spacemit_vslam repo and registers it in the manifest, giving K3 visual SLAM an official entry point (11-06/11-07)
    • perception adds an ExternalStereo SDK backend for las2, with stereo extrinsics going through the vendor SDK rather than a generic driver (11-07)
    • unitree-go2 refreshes calibration photos and USB wiring instructions, pushing the quadruped platform’s barrier further toward “follow the steps and it runs” (11-06)
  • V. Summary and Trend Observations
  • Appendix: Complete Source List and Source Verification Table

Today’s Focus: Visinex Technology Debuts the RISC-V Edge Vision Chip VS815V — Dual-Core RISC-V Plus Fully Domestic 22nm, Targeting Affordable 4K (announced 11-03, reported 11-06)

At the 2026 China International Public Security Products Expo (Security China), held in Beijing from November 3 to 6, Shanghai Visinex Technology debuted the edge AI vision chip VS815V. This is the company’s first chip built on the RISC-V architecture, and the official positioning is not about setting computing power records but about “affordable 4K”: a fully domestic, mainstream-price 4K edge AI vision chip.

In terms of specifications, the CPU portion is a purely domestic dual-core RISC-V core, paired with a self-developed dedicated small core for system control and scheduling; the NPU delivers 1.6T@INT8 (3.2T@A8W4) of compute, with emphasis on strengthening support for small models on the order of 0.3B (about 300 million parameters), enabling natural language interaction on the edge while leaving complex reasoning to the cloud. On the imaging side, it supports up to 4 MIPI camera inputs in parallel without an external Switch chip, and hardware PDAF phase detection autofocus maintains 4K@30 without frame drops, with motion stabilization aligned to drone and action camera scenarios. For manufacturing, per the vendor’s account, the process, wafer foundry, packaging and testing, and key IP are all domestic, using a fully domestic 22nm process.

Worth noting separately is its approach to plugging into the RISC-V ecosystem. Visinex only joined the China RISC-V Industry Consortium (CRVIC) as a core member in September 2026, yet this time it defined the product on the premise that “mature RISC-V IP suppliers already exist in China,” while also offering secondary-development customization support and a complete toolchain to help customers migrate existing algorithms. The company’s stated timeline is that end products in mass production will be visible in 2027; for robotics, VS815V is positioned as a visual perception module supporting stereo depth and multi-camera stitching, building on its quadruped and humanoid robot deployment cases.

Placed in this week’s coordinates, its significance lies in this: “the two tracks that care most about supply security — automotive-grade and security — are starting to treat RISC-V as a deliverable option rather than a fallback.” Zijing M100 takes the automotive-grade MCU route, while Visinex VS815V takes the vision SoC route; what they share is full-chain domesticization and toolchain support, not single-point performance. The real test comes in 2027: whether customers are willing to bear the algorithm migration cost of “switching architectures” depends on whether the toolchain can turn migration into a single compile configuration rather than a rewrite.

Date: Announced 2026-11-03, reported 2026-11-06 Sources: RFID World report, Jiwei report (NetEase reprint), Visinex Technology news updates

Espressif’s ESP32-S31 is a dual-core RISC-V chip released in April this year, clocked at up to 320MHz, with 2.4GHz Wi-Fi 6, Bluetooth 5.3, and 802.15.4, up to 32MB of on-chip PSRAM, plus a gigabit Ethernet MAC (RGMII pins multiplexed with GPIO8 through GPIO19). Over the past six months it has been more of a “new product with impressive specs”; in this window two things landed at once, pushing it into the position of a usable platform.

The first is the board. Waveshare launched the ESP32-S31-Zero, continuing the Zero series’ tiny form factor, with USB-C for power and flashing, 18 through-holes and half-holes breaking out GPIO and power, plus a 40-pin high-density connector for LCD, touchscreen, SD card, USB 2.0, and extra GPIO. In the same series there is also LILYGO’s ESP-Mosaico, which tucks the S31 behind a 2.16-inch square AMOLED. The second is the OS. On November 7, Hackaday reported under the headline “Proper Linux, On An ESP32”: the S31 has an MMU and runs full-featured Linux rather than a nommu version; Espressif has already opened the espressif/linux repository on GitHub, and the community has a separate esp32-s31-linux project working on a 6.x kernel port.

Together, the two developments show that this chip’s positioning has moved beyond “MCU plus wireless”: with an MMU it can run general-purpose user space, with PSRAM and a gigabit MAC it can serve as a gateway and lightweight edge node, and the board price brings it down to the level where you can buy one on a whim to try. Its relationship with the ESP32-P4 is also clearer — the P4 takes the high-performance MCU plus display and audio route, while the S31 takes the “boundary between MCU and SoC” route. For teams building RISC-V gateways, industrial HMIs, and edge boxes, this is a new low-cost option; for Espressif, it is a probe into extending the same ESP-IDF ecosystem toward Linux.

Date: Board released 2026-11-06, Linux reported 2026-11-07 Sources: CNX Software board report, Hackaday report, espressif/linux repository

I. Open-Source Community and Software Ecosystem

openRuyi main repo bumps kernel to 7.3.3 and LTS 6.18.62, upgrades glibc to 2.44 and brings x86_64 into testing (11-08)

The openRuyi main repo landed ten substantive commits in a row on November 8. On the kernel side, two lines advanced simultaneously: the mainline package was bumped to 7.3.3 with refreshed patch sets and configs, and the LTS package was bumped to 6.18.62, likewise with refreshed patch sets and configs. On the toolchain side, glibc was bumped to 2.44 (commit c5c6fc6), and the full test suite was run on x86_64. The same day also saw an rpm-config-openruyi commit adding x86_64 architecture macros and compiler flags.

Reading “x86_64 architecture macros” together with “running the full glibc test suite on x86_64” points to the build side rather than a distro port: openRuyi is an RPM-based, RISC-V-oriented rolling distribution, and treating x86_64 as a first-class build and test target gives cross-builds and host-side toolchains a unified validation baseline. This is consistent with the main repo’s direction over the past two weeks—continuously adding documentation-format import libraries and office-suite dependency closures—namely, first making “it builds and it tests” solid before talking about releases.

The remaining commits are routine maintenance: adding clonezilla, adding a python-clang package to llvm-defaults, bumping tmux to 3.8, fixing build errors in qt6-qtwebengine, and removing the architecture qualifier from dbus-common’s Requires. The official news page’s latest items are still the two from October 2026 (the Ruyi Firmware firmware solution and RISC-V ecosystem public infrastructure); the November release has not shipped yet, so today’s items count only as repo-side progress.

Date: 2026-11-08 Source: openRuyi-Project/openRuyi main repo, openRuyi official news page

CORE-V CVW merges 20 commits: removes two local branch predictors and BTB parameters, publishes RV32GC CoreMark/MHz of 4.33 (11-07)

CORE-V Wally (cvw) merged 20 commits in a burst on November 7, which can be grouped into three directions. The branch-prediction group did subtraction: it removed the two local branch predictors BP_LOCAL_AHEAD and BP_LOCAL_REPAIR while also removing the BTB_ADDR_BITS parameter; static-prediction cleanup came alongside. The peripheral-and-bus group fixed timing: centered PWM sticky and deglitch behavior, an APB read strobe fix, and removal of the AHB/APB bridge unit tests. The benchmarking group tightened methodology: the README now states RV32GC CoreMark/MHz of 4.33 and extracts the common CoreMark compiler options for reuse; there are also UART tests, a counter-mask shift fix, and uncached wide accesses.

Removing predictors is unusual on a core aimed at teaching and research. Local branch predictors are structurally complex and their benefit is workload-dependent; removing them usually means the team is converging toward “simple structure, timing that closes easily, interpretable results” rather than chasing IPC. Combined with the CoreMark/MHz of 4.33 published the same week, CVW is putting both “reproducible scores” and “synthesizable RTL” on the table at once, which is more practical for teams using it for teaching, pre-tapeout validation, and CORE-V ecosystem chip prototypes.

Date: 2026-11-07 Source: openhwfoundation/cvw repo

Five XiangShan difftest commits converge on matrix extension: drain async checks, push cycle scheduling down to backends, switch matrix fingerprint to CRC32C (11-07/11-08)

The XiangShan main repo’s kunminghu-v3 branch had no new commits in this window (the most recent stopped at the November 5 MissQueue store merge fix), with activity falling on the verification toolchain. difftest merged five commits: draining MMA async checks before termination traps (#1031), pushing cycle-scheduling logic down to each backend (#1030), adding an ILA window-size parameter for the FPGA target (#1026), compressing the event payload of matrix DiffTest (#1029), and switching the matrix completion fingerprint from the original scheme to CRC32C (#1028). On the NEMU side, a corresponding AME performance change likewise uses CRC32C to compute the matrix completion hash (#1280).

What these five commits share is engineering “how to verify the matrix extension”: if async checks aren’t drained, events are lost at termination traps; if cycle scheduling stays in the common layer, timing semantics diverge across backends; and CRC32C fingerprints are used for low-overhead comparison across large numbers of tile-completion events. Matrices differ from vectors—one operation produces an entire block of results, so element-by-element comparison is too costly and only digest comparison works, with the digest algorithm directly determining the false-positive rate and overhead. XiangShan’s recent cadence on this line is clear: first get the matrix extension’s verification infrastructure right, then talk about benchmarks.

Date: 2026-11-07, 2026-11-08 Source: OpenXiangShan/difftest, OpenXiangShan/NEMU

RevyOS kernel lands 20 commits at once: debian_defconfig unifies six vendors’ platforms, adds cross-arch and native build CI (11-09)

RevyOS’s linux repo (revyos/7.3.y branch) pushed 20 commits in one go in the early hours of November 9. The most informative is the config layer: a new debian_defconfig consolidates the config options for six platforms—ESWIN EIC7700, UltraRISC DP1000, SpacemiT K3 and K1, T-Head TH1520, and Sophgo SG2042/SG2044—into a single defconfig, plus a Picoheart errata switch and a set of common options; CI for both cross-arch and native builds was added at the same time.

The driver side carries fixes across several lines: SpacemiT UFS enters FASTAUTO before switching to FAST mode, SpacemiT DRM’s shmem GEM mapping switches to writecombine, panel detection and hotplug interrupt recovery after the DP adapter, and silencing connector work before shutdown; on the T-Head side, USB power retention during Lichee Pi 4A handover is fixed and USB is enabled for Milk-V Meles. On the packaging side there is compatibility handling for “major version number as package name” and linux-image providing wireguard-modules.

The value here is that “one kernel image covering six platforms” finally has a unified entry point. The long-standing problem for RISC-V distributions is one config and one patch set per board, so upgrading the kernel means redoing the porting; folding six platforms into one defconfig means subsequent kernel upgrades can be validated on a single baseline instead of running six branches separately. For downstream teams building products, this matters more than one more feature.

Date: 2026-11-09 Source: revyos/linux repo

Specula: an undergraduate writes an out-of-order RV32I core from scratch in Bluespec and turns the pitfalls into a long-form writeup (11-06)

Developer Pranav published a long-form article on November 6 about Specula, a dual-issue out-of-order RV32I processor he implemented from scratch in Bluespec SystemVerilog starting in his first semester of senior year. The article doesn’t stop at “I built a core” but breaks down the parts of out-of-order execution most prone to error: register renaming and retirement, reservation stations and issue, store forwarding and speculation, comparison trees and register ports squeezing timing, and the debugging path for “when the hardware just won’t converge.”

The value of this kind of content to the RISC-V community isn’t in lines of code but in pulling the “barrier to entry for out-of-order cores” out of the black box of papers and commercial IP. Teams in China doing RISC-V teaching and pre-tapeout validation have long lacked an intermediate textbook “from in-order to out-of-order,” and Specula’s repo and writeup fill exactly that gap: the RV32I subset is small enough, and Bluespec’s rule-based description makes pipeline control explicit, so students can understand why each cycle happens.

Date: 2026-11-06 Source: Specula writeup, Specula repo

II. Product and Ecosystem Updates

AMD Zen 6’s PMF Trusted Application Moves to a RISC-V TEE, Replacing the Arm Core in the PSP (11-07)

On November 6, Phoronix noticed a linux-firmware commit: it adds AMD PMF (Platform Management Framework) trusted application firmware v4 for the 1AH_M80H platform, and the commit message states that “the TA now runs on a RISC-V-based trusted execution environment, uses a larger shared memory layout, and supports extended policy conditions, including up to 20 custom BIOS inputs.” 1AH_M80H corresponds to the upcoming Zen 6 client processors.

The technical significance here lies in “what was replaced.” AMD’s security processor (PSP) has long been based on an Arm Cortex-A5 plus TrustZone, handling platform security and firmware execution; moving a trusted application like PMF—which manages power, temperature, and system behavior—to a RISC-V TEE means AMD has switched instruction sets on its security core. For the RISC-V industry, this marks an x86 major vendor putting RISC-V on the security-critical path of its own production platform, rather than using it as a sideband controller.

What needs restraint is the scope of interpretation: a single firmware commit only proves that this one TA, PMF, runs on a RISC-V TEE; it cannot be inferred that the entire PSP has switched cores across the board, nor that AMD will license the core externally. What can be confirmed is the timing—Zen 6 has not yet been officially released, and the firmware has landed first—and the direction—RISC-V has taken another step forward in the “invisible core” market.

Date: Committed 2026-11-06, reported 2026-11-07 Source: Phoronix report, linux-firmware commit

SparkFun’s Two ESP32-P4 IoT RedBoards: One with a Wi-Fi 6 Companion Chip, One with PoE Ethernet (11-06)

On November 6, SparkFun released two ESP32-P4 IoT RedBoards. Both boards share the same core: the dual-core RISC-V ESP32-P4, 32MB PSRAM, 16MB flash, MIPI camera and display interfaces, and Arduino-style expansion headers; the difference is in connectivity—one is paired with an ESP32-C5 companion chip providing dual-band Wi-Fi 6, while the other uses wired Ethernet with PoE power support.

This product form factor is worth noting because it clarifies the positioning of the ESP32-P4: the P4 is not a “high-performance MCU with wireless,” but rather an application processor for cases that need display, camera, and a certain amount of compute, but where wireless can be external. Using the C5 as a Wi-Fi 6 companion chip effectively strips the RF and protocol stack away from the main core, letting the main core focus on imaging and HMI; using PoE directly targets the wiring realities of industrial and commercial scenarios. For teams building RISC-V edge panels, access control, and machine vision front ends, these two boards can serve directly as reference designs.

Date: 2026-11-06 Source: LinuxGizmos report

LocalDot Uses ESP32-S3 Plus ESP32-P4 to Turn a Third-Gen Echo Dot into a Home Assistant Voice Terminal (11-06)

Crowd Supply has launched a crowdfunding campaign for LocalDot, an open-hardware board developed by AAElectronics that converts a third-generation Amazon Echo Dot into a Home Assistant voice device. The board measures 83×37mm, with an ESP32-S3 handling Wi-Fi connectivity and device control, and an ESP32-P4 handling audio processing, including microphone input and voice signal processing; the original unit’s four-microphone array, speaker, buttons, and LEDs are all retained, with beamforming on the P4 side for directional pickup and a TAS5805 amplifier driving the original speaker.

This is a typical case of “RISC-V taking over existing hardware”: the Echo Dot’s compute is tied to the cloud, and after LocalDot swaps the main controller for two RISC-V chips, the device becomes a fully localized voice terminal. The P4’s audio subsystem and PSRAM bandwidth are well suited to multi-microphone beamforming, while the S3 adds wireless and low-power standby. For teams working on smart home and voice hardware, this kind of retrofit approach demonstrates RISC-V’s competitiveness on both cost and privacy better than building a new device from scratch.

Date: 2026-11-06 Source: LinuxGizmos report

III. In-depth Look at Domestic Teams

Espressif: Fifth Global Developer Conference Held in Milan, MicroPixel Brings AI-Native Application System to Low-Cost Chips (11-06)

The fifth Espressif Global Developer Conference was recently held in Milan, Italy, under the theme “Building the Next Generation of Innovative Connectivity,” with topics covering AI and edge intelligence, security, developer tools, and ecosystem collaboration; a Technology Ecosystem Day was held concurrently in Shanghai. At the event, ShiFangRongHai Chairman Huang Guan gave a talk titled “MicroPixel: The Harness for Embedded Development, Bringing AI into the Physical World,” discussing his second open-source project after XiaoZhi AI (xiaozhi-esp32).

MicroPixel positions itself as “an AI-native embedded application operating system for low-cost chips,” splitting its capabilities into four layers: the system layer encapsulates display, touch, audio, storage, and application management; the creation layer connects to coding agents via natural language; the experience layer provides installation, switching, and application-level sandbox isolation; the closed-loop layer feeds real-device logs, screen feedback, and debugging channels back into the AI development workflow. According to public data, XiaoZhi AI has accumulated over 30,000 GitHub stars, connected to over 2 million hardware units, attracted 150,000 developers and makers, and handles 9 million daily conversations.

The relevance to Espressif is not “what Espressif released” but ecosystem spillover: projects like MicroPixel push the ESP32 from “writing firmware” toward “installing applications,” and the chips it relies on are precisely the RISC-V models in the ESP32 series. For domestic teams building low-cost smart hardware, this is a reusable path—don’t wait for chips to get stronger; first turn application installation, isolation, and updates into system-level capabilities.

Date: 2026-11-06 Source: ZAKER report, Jiemian News report, Espressif official website

SpacemiT: K3 Heterogeneous Multi-Core Self-Test Script Enters 7.3 Branch, K3 Power Domain Driver Enters wip Branch (11-06/11-07)

SpacemiT’s kernel work is advancing on two branches. The k3/hmp-on-7.3 branch added an on-chip self-test script for K3 heterogeneous multi-core (HMP) on November 6, turning HMP validation from “reading logs” into “running scripts on the board”; the wip/k3-pm-v2.5 branch landed two commits on November 7: the SpacemiT power domain (pmdomain) driver, and the corresponding device tree binding adding the power domain controller ID. This is a standard move to align K3’s power management with the upstream driver model.

Putting these two together with concurrent user-space actions reveals SpacemiT’s current rhythm: on the kernel side, filling in “platform foundations” like HMP and power management; on the user-space side, pushing Bianbu Agentic’s componentization—on November 6, the bianbu-agentic main repo updated submodules, pulling bianbu-agent-memory and bibit-memory-plugin to the same version, bringing agent memory and plugins from their separate repos into umbrella repo management.

Date: 2026-11-06, 2026-11-07 Source: spacemit-com/linux, spacemit-com/bianbu-agentic

Sophgo: sophon-tools’ se-rag-core Ships Four Versions in a Row, Offline BM25 and Registry Retrieval Take Shape (11-07)

Sophgo’s sophon-tools repository merged four PRs (#228 to #231) on November 7, pushing se-rag-core from 1.6.0 to 1.8.1. 1.6.0 added offline pure BM25 indexing and multi-index merged retrieval; 1.7.0 added exact-match boosting for identifiers and titles, fixed top-n truncation, and added doc-type filtering; 1.8.0 added registry mode, with entity-based routing, indexing, and retrieval; 1.8.1 fixed “no longer tagging types when a single index has no doc-type” and path mode rejecting registry-specific parameters.

This is a toolchain-leaning development, but the direction is noteworthy: RAG is sinking from “vector database plus embedding model” to “offline index plus rule-based boosting,” and the latter is the form edge devices can afford—BM25 needs no GPU, and registry mode lets one tool serve multiple knowledge domains simultaneously. Sophgo’s TPU product line primarily targets combinations of lightweight retrieval like BM25 with local inference, and this toolset determines whether customers can put private knowledge to use in offline environments.

Date: 2026-11-07 Source: sophgo/sophon-tools

Nuclei: nuclei-sdk Fixes evalsoc SMP Boot Synchronization, Build System Addresses REUSE and Windows Path Issues (11-06)

Nuclei’s nuclei-sdk develop branch saw consecutive commits from November 5 to 6. On the boot side: evalsoc SMP hart synchronization was changed to be driven by the boot hart with one MSIP interrupt per hart; _start was pinned to the reset vector using the startup section; documentation for boot layout, reset vector, and boot flow was added; and assembly object files were ordered before C/C++ objects. On the build side: REUSE=1 was added to reuse existing configuration in the output directory, absolute Windows O= paths causing corrupted object file paths were fixed, buildtodir build system regression tests were added, and make help was tidied up. There was also one NMSIS/Core commit fixing cluster cache command register writes.

None of these commits are “sexy,” but they all point to the same thing: the SDK is starting to be treated as a long-term maintained product rather than a collection of examples. SMP boot ordering and reset vector pinning are the two areas most prone to problems and hardest to reproduce after multi-core chips enter mass production; REUSE and Windows path fixes directly affect customers’ experience of repeated builds in CI. For an IP vendor, this kind of engineering investment retains customers better than shipping one more core.

Date: 2026-11-06 Source: Nuclei-Software/nuclei-sdk

DAMO XuanTie: Zero Pushes in Open-Source Repos During Window, Community Runs MicroPython on T527’s E906 Core (Written 10-31, Circulated 11-06)

DAMO XuanTie’s GitHub organization (XUANTIE-RV, 73 repos) had zero pushes during this window, with the most recent commit still at November 4 on damo-rv-priv-ats, torq-tile at October 29, and llvm-project at October 27. There were also no new product releases this week, so this XuanTie section can only find increments from the ecosystem side.

The increment comes from the community. Developer tcmichals published the fifth article in a series on October 31, explaining how to run MicroPython on the 200MHz XuanTie E906 core in Allwinner’s T527: the T527’s eight Cortex-A55 cores run Linux, while the E906 sits outside Linux; the author ported MicroPython onto it, then used Python on the Linux side to drive it over an inter-core link to read an I2C compass and UART GPS—changing one line of code to verify, without recompiling firmware or rebooting. The accompanying AbstractX Studio uses non-intrusive binary telemetry to display the E906’s CPU usage, per-interrupt microsecond overhead, and line-by-line source profiling. This was brought to the Hacker News front page on November 6, making it the most widely circulated XuanTie-related item this week.

The significance for XuanTie is that “how to use heterogeneous cores” finally has a reproducible template. SoCs like the T527—”an A55 cluster plus a small RISC-V core”—are common in automotive infotainment and industrial boards, but the small core has long been used only for bare-metal control; turning it into an interactive, profilable coprocessor amounts to providing a usage pattern for such designs that doesn’t depend on vendor SDKs.

Date: Written 2026-10-31, circulated 2026-11-06 Source: All things embedded long-form article, Hacker News discussion

Sipeed: NanoKVM Merges Storage File Manager UI, KVM over IP Image and File Exchange Completed (11-06)

Sipeed’s NanoKVM merged PR #982 on November 6, adding a storage file manager interface. NanoKVM is an open-source KVM over IP device based on the SG2002 (RISC-V), which previously had multi-user permissions, read-only image mounting with a single-writer model, and terminal and video stream optimizations; this addition fills in the interface layer for “browsing media in the browser and exchanging files with the target machine.”

The competitive point for KVM over IP devices has long ceased to be “can it remotely view the screen” and become “can it replace a site visit.” With file exchange, image mounting, and multi-user permissions all in place, operations teams can complete system reinstallation and configuration distribution without touching the target machine. NanoKVM achieves this with a low-cost RISC-V SoC, making it a directly referenceable open-source baseline for domestic teams working on out-of-band management and edge operations.

Date: 2026-11-06 Source: sipeed/NanoKVM

IV. Embodied Intelligence and Robotics Special Section

spacemit-robotics opens the ros2_spacemit_vslam repo and registers it in the manifest, giving K3 visual SLAM an official entry point (11-06/11-07)

spacemit-robotics created the ros2_spacemit_vslam repository on November 6 and completed its first commit; on November 7, manifest repo PR #32 registered it in the full-system manifest. The repository is positioned as a ROS 2 wrapper for spatial visual SLAM running on the K3 platform; previously the organization’s vision capabilities were scattered across components such as planar, superpoint, and lightglue in the perception repo, lacking a ROS 2 interface friendly to upper-layer navigation.

From an engineering perspective, making SLAM a separate repo and adding it to the manifest means it is now treated as “a component that can be assembled into a full system” rather than “part of some demo.” The manifest is spacemit-robotics’ full-system assembly list; being on the list means entering the CI and version-alignment process. For downstream teams building complete robots, this is more useful than one more algorithm, because it determines whether an upgrade will break someone else’s dependencies along the way.

Date: repo created 2026-11-06, registered 2026-11-07 Source: spacemit-robotics/ros2_spacemit_vslam, spacemit-robotics/manifest

perception adds an ExternalStereo SDK backend for las2, with stereo extrinsics going through the vendor SDK instead of a generic driver (11-07)

spacemit-robotics’ perception repo merged #12 on November 7, adding an ExternalStereo SDK backend for las2; on November 6, #11 separately added result-screenshot documentation. las2 is the repo’s lidar-vision fusion line; the ExternalStereo backend’s role is to hand stereo camera extrinsics, synchronization, and depth computation to the vendor SDK, rather than guessing with a generic V4L2 plus OpenCV combination.

This step is critical to putting stereo vision into production on robots. The hardest part of stereo is not the algorithm but “time synchronization and extrinsic calibration of the two cameras”; generic drivers often cannot obtain the vendor’s calibration data and hardware sync signals, so the depth map is good one moment and bad the next. Bringing in the vendor SDK as an optional backend amounts to acknowledging that “hardware differences must be the hardware vendor’s responsibility,” while retaining the generic path for standardized devices. This is a pragmatic engineering trade-off and a common choice on domestic robot platforms.

Date: 2026-11-07 Source: spacemit-robotics/perception

unitree-go2 refreshes calibration photos and USB wiring instructions, pushing the quadruped platform’s barrier further toward “follow the steps and it runs” (11-06)

spacemit-robotics’ unitree-go2 repo merged #5 on November 6, updating calibration photos and simplifying the USB wiring instructions. The repo is the porting and deployment project for the Unitree Go2 quadruped robot on the K3 platform; it had previously completed work including IMU snapshot read optimization, terrain-walking policy V2 with pinned model downloads, and SBUS dependency and hardware guide fixes.

The success of a robot porting project often hinges not on the algorithm but on “whether it lights up the first time.” Calibration photos and wiring instructions look like the most inconspicuous documentation, yet they determine whether a new team needs a day or two weeks to get the robot standing. Nearly all of this repo’s commits over the past two months are on engineering details of this kind: IMU reads that don’t copy motor state, reproducible model downloads, SBUS dependencies that can be regression-tested in CI. Making the quadruped platform “reproducible by following the docs” is the layer the domestic RISC-V robotics stack most lacks and most needs.

Date: 2026-11-06 Source: spacemit-robotics/unitree-go2

V. Summary and Trend Observations

  • The focus of edge vision is shifting from “compute competition” to “supply security plus toolchain”: VeriSilicon’s VS815V uses a dual-core RISC-V plus fully domestic 22nm for affordable 4K, with specs that don’t chase the high end and selling points placed on a fully domestic chain and algorithm migration support. This follows the same logic as last week’s Zijin M100 automotive-grade path, showing that domestic RISC-V, in the two tracks that most value controllability—security and automotive—has begun to define products by “deliverable” rather than “demonstrable.”

  • The boundary between MCU and SoC is erased on the ESP32-S31: with an MMU, the ability to run full-featured Linux, up to 32MB PSRAM, and a gigabit MAC, plus a Zero-sized board and 40-pin expansion. Espressif extending the ESP-IDF ecosystem toward Linux amounts to offering a third path for low-cost gateways and HMIs—neither a pure MCU nor a full application processor.

  • Verification infrastructure becomes the main battleground of the open-source core race: all five XiangShan difftest commits are on verification methods for matrix extensions, while CVW removes the predictor and publishes CoreMark/MHz 4.33; the two go in opposite directions but share the same goal—making scores reproducible and structures explainable. Once matrix extensions land, “how to compare an entire block of results” is more lacking in engineering answers than “how to compute faster.”

  • Distributions begin to converge platform fragmentation: RevyOS uses a single debian_defconfig to cover six platforms and adds cross-architecture and native CI, while openRuyi brings x86_64 into its build and test matrix. The past problem with RISC-V distributions was “one config per board”; now the two main distributions are simultaneously working on “one baseline covering multiple platforms,” which lowers downstream costs more than shipping one more release.

  • Security cores and coprocessors are RISC-V’s two quietest incremental markets: AMD moves Zen 6’s PMF trusted applications to a RISC-V TEE, and the community turns the Allwinner T527’s E906 into an interactive coprocessor with MicroPython. Neither is in the spotlight, yet both are real use cases of “a RISC-V core alongside the main core,” and both produced verifiable engineering details within this window.

Limitations note: This issue covers a Monday 72-hour window, from 05:00 on November 6 to 05:00 on November 9. On the Google News side, this week was dominated by secondary coverage of Infineon’s AURIX RC1 and ESP32 board news; the former was already included as a today’s focus in the November 5 report and is not counted again here. On the Chinese-language side, queries such as “XiangShan,” “XuanTie,” and “ESWIN” had high noise, and content on scenery, ski resorts, steel large models, and listed-company announcements was filtered out by headline semantics. In the member-site inspection, 66 of 391 sites failed to fetch (including the Institute of Software of the Chinese Academy of Sciences, Tencent, and Ingenic); 72 were judged to have content changes but were all homepage marketing rotations or security-block pages, with no substantive product releases, so they were not included as entries. riscv100.top showed no changes this issue.


Appendix: Full Source List

Full Source List

Source Verification Table

Source Verification Result
Google News aggregation (30+ Chinese and English query sets, via proxy) 6 valid new items within the window: Visinex VS815V, Waveshare ESP32-S31-Zero, Hackaday full-featured Linux, AMD Zen 6 RISC-V TEE, SparkFun ESP32-P4 dual-board, Espressif Developer Conference and MicroPixel; Infineon AURIX RC1 is a re-circulation of old news from 11-04, already included on 11-05, not duplicated
Hacker News 2 valid: full-featured Linux on ESP32, MicroPython on E906; the rest are unrelated discussions
Phoronix 1: AMD Zen 6 RISC-V TEE (11-06)
CNX Software 1: Waveshare ESP32-S31-Zero (11-07); Olimex CH390 module is unrelated to RISC-V, excluded
LinuxGizmos 3: SparkFun ESP32-P4 dual-board, LocalDot, ESP32-P4 compute module; all involve RISC-V
Hackaday 1: Proper Linux on an ESP32 (11-07)
openRuyi dual sources (official news page + main repo) The official news page’s latest entries are still the two from October 2026; the November release has not been published; 10 substantive commits in the main repo within the window, kernel and glibc upgrades included
GitHub organizations and key repositories check (72 hours) Organizations with pushes within the window: Espressif 41 repos, openRuyi-Project 12 repos, SpacemiT 8 repos, Sophgo 7 repos, spacemit-robotics 4 repos, Nuclei 2 repos, Sipeed 4 repos, RevyOS 1 repo, CORE-V 2 repos; DAMO XuanTie and ESWIN had zero pushes
XiangShan mainline Zero commits on the kunminghu-v3 branch within the window (most recent 11-05); NEMU and difftest have commits, explained in the main text
RISC-V member company website inspection 391 companies: 253 unchanged, 72 changed, 66 failed; all changes were homepage marketing rotations or security block pages, with no substantive product or architecture releases
riscv100.top leaderboard inspection No changes
WeChat official accounts and vendor websites Supplementary checks of Visinex, Espressif, HPMicro and other official sites found no other substantive releases within the window