Research window: 2026-11-06 08:00 ~ 2026-11-09 08:00 (Beijing time, 72 hours, covering the weekend)

Sources: RT-Thread official news API and official website news page, GitHub main repository commits / PR / Issue / releases / tags, RT-Thread org repository push list (both the rt-thread and env repos had pushes this period), three sets of Google News queries in Chinese and English (via proxy), HN Algolia, Electronic Engineering Album RT-Thread column, club.rt-thread.org forum (still restricted by the site’s WAF this period)


Index for This Issue

  • I. Kernel and Version Updates
    • K230D merged: 128MB DDR variant gains ext4 and ptyfs (11-06)
    • STM32F1/H7 input capture lands: 746 lines complete four-channel timers (11-06)
    • Correction of non-SMART CPU time accounting (11-07)
    • Format specifier fix in GIC print function (11-08)
  • II. Security and libc Fixes
    • Two timerfd validation fixes merged the same day (11-08)
    • picolibc prototype alignment: array parameters of asctime_r and ctime_r (11-08)
    • RISC-V FPU context switch defect: fix proposal four hours after report (11-07)
    • Pending review queue: 142 proposals, 363 issues (11-09)
  • III. Official and Community Events
    • Official website news API backfills seven articles at once: from elexcon to the Wuzhen Summit (11-06)
    • Wuzhen Summit: heterogeneous converged edge intelligence AIOS foundation selected for the “Xinguang” list (11-02)
    • RISC-V China Summit: edge AI full stack, automotive-grade software already in vehicle testing (10-18)
    • elexcon Shenzhen: 2.5 billion installations and triple functional safety certification (09-09)
  • IV. Ecosystem and Vendor Adaptation
    • QEMU virtual device list advances: SPI loopback, CAN, SDIO, DAC/I2C enter CI (11-06)
    • Two WCH lines: Qingke fast interrupt configuration and CH32V208 low power (11-07)
    • Renesas RH850 G4KH port proposal: a third architecture beyond ARM and RISC-V (11-06)
    • Env adds “format changed files only” command (11-06)
    • New community-side repositories: CarPlay receiver, Wi-Fi/Bluetooth host driver, and quadruped robot dog (11-07)
  • V. Industry Applications and Industry-Education
    • Ruiqing enters PLC: the “1+X+N” and microsecond-level metrics at the Vinaro salon (11-06)
    • Automotive software salon: AI-empowered development, core initiating member of the Lingang alliance (09-16)
    • Industry Expo AI car Workshop: breaking edge AI into a hands-on process (10-12)
    • Southeast Asia university outreach: WOU Malaysia signing and contact with six universities (11-06)
  • VI. Summary and Trend Observations
    • Eleven commits in three days: test infrastructure becomes the main thread this period
    • Two new boundaries for security topics: device input and architectural state
    • Version cadence still stuck at v5.3.0
    • Catching up on external communications: seven backfilled articles and three industry narratives

I. Kernel and Version Dynamics

1.1 K230D merged: 128MB DDR variant gains ext4 and ptyfs (11-06)

Date: 2026-11-06 09:37 (merge time) Source: PR #11897, PR #11892

15 files, 398 insertions, 198 deletions, submitted by maintainer BernardXiong, opened on October 18 and merged this issue. The content is a complete BSP fill-in: adds a choice between SOC_K230 and SOC_K230D, rearranges the default memory layout for 128MB DDR; registers GPIO as an RT-Thread pin device, adding 140 lines to the driver in one go, plus GPIO tests; enables the ext4 root filesystem, mounting ptyfs and procfs; removes a batch of unused board-level peripheral definitions. The toolchain remains the K230 SDK’s riscv64-unknown-linux-musl, and the ABI is still lp64d.

The weight of this one lies in its dependencies: it requires the RISC-V MMU and XuanTie architecture fixes from #11892 first (the item in section 1.2 of the previous report), and also needs the lwext4 package; the ptyfs and procfs mount points are precisely the prerequisites for the RT-Smart terminal and device tree export. In other words, K230D is not an isolated board addition, but rather strings together the batch of Smart fixes from 11-05 on a real RISC-V board with 128MB of memory. CI has not yet given a build conclusion; the author only compiled locally with the K230 SDK toolchain.

1.2 STM32F1/H7 input capture lands: 746 lines complete four timer channels (11-06)

Date: 2026-11-06 09:20 (merge time) Source: PR #11975, Issue #11967

9 files, 746 insertions, zero deletions. The issue was raised on November 2; previously the forum had only a personal implementation, and four days later the driver entered mainline. The implementation uses STM32 HAL’s TIM1 through TIM4 as input capture devices, with configurable channels, filters, and initial capture polarity; it handles three platform differences: APB timer clock multiplication, TIMPRE, and 32-bit counters; pending capture and over-capture flags are cleared before restarting a capture channel.

CI covers two boards: the STM32F103 battleship board runs the inputcapture snippet, and the STM32H743 Nucleo runs the full configuration. For users, filling in this kind of peripheral framework expands applicability more than fixing kernel defects—input capture is a common path for motor control, encoders, and pulse measurement.

1.3 Correction of CPU time accounting for non-SMART builds (11-07)

Date: 2026-11-07 21:39 (merge time) Source: PR #12001

Only two lines changed in src/clock.c: the user-mode time accounting branch is wrapped in RT_USING_SMART. Previously non-SMART builds also went through this logic, so thread time was counted as user-mode time, and system time and idle time statistics were correspondingly understated. A two-line change that affects the CPU usage readings of all non-Smart projects.

1.4 Format specifier fixes in GIC print functions (11-08)

Date: 2026-11-08 16:20 (merge time) Source: PR #11914

3 files, 71 insertions, 48 deletions, modifying gic.c, gicv3.c, and gicv3.h. Four categories of issues: printing 32-bit physical addresses with %p, where passing a non-pointer to %p is undefined behavior; printing unsigned quantities with %d; a missing type cast for the GIC version number; and a signed left shift in the GIC RWP macro. The PR was opened on October 21 and merged on November 8; the author is Wei-beep, with maintainer Rbb666 as co-author. Compiling Cortex-A BSPs with -Wall -Wformat no longer spews warnings. This kind of cleanup does not affect functionality, but it directly affects the compilation cleanliness of vendor BSPs.

II. Security and libc Fixes

2.1 Two timerfd Checks Merged the Same Day (11-08)

Date: 2026-11-08 14:12 / 14:11 (merge time) Source: PR #11996, Issue #11984, PR #11997, Issue #11980

Two commits landed one minute apart, each touching a single file.

The first is fd type validation in timerfd_settime and gettime: the original implementation dereferenced the private data of any file descriptor as a timer struct, so passing in an ordinary file or pipe caused the kernel to read the struct as the wrong type. The fix compares the file operations table first and only fetches the private data once confirmed to be a timerfd — DFS v2 checks df->fops, v1 checks vnode->fops; 25 lines added.

The second is an array out-of-bounds in POSIX timers: timer_gettime and timer_settime indexed _g_timerid directly with the user-supplied timer_t, while timer_delete already had a bounds check. The fix adds a check that id must be less than TIMER_ID_MAX; 19 lines added.

Both defects appeared in the security lists of the previous two reports; this issue they move from reported to fixed. timerfd and POSIX timer are both user-controllable handles, and the failure pattern is identical: dereference first, then check type or range.

2.2 picolibc Prototype Alignment: Array Parameters in asctime_r and ctime_r (11-08)

Date: 2026-11-08 14:01 (merge time) Source: PR #11999

ctime.c: 13 lines added, 3 deleted. picolibc declares the buffer as a restricted array of length 26, while RT-Thread declared it as a pointer, producing both array-parameter and null-pointer-comparison warnings; other C libraries still use the pointer form, so the fix switches the declaration per library via conditional compilation. Author: Parthiban Nallathambi of Linumiz.

This is listed separately because it unblocks another thread: the Renesas RH850 port proposal explicitly states that utest CI must wait for this ctime.c fix — see 4.3.

2.3 RISC-V FPU Context Switch Defect: Fix Proposal Four Hours After Report (11-07)

Date: 2026-11-07 23:10 (report) / 2026-11-08 03:14 (proposal) Source: Issue #12005, PR #12006

The one to watch this issue. Reporter boa-z, while porting ArtInChip D213 (C906, M-mode), found fs1 incorrect after a thread switch. To rule out BSP factors, they reproduced it on the official qemu-virt64-riscv: QEMU 10.0.13, OpenSBI 1.6, RV64D, single hart, master c63d7bc9. They wrote a test case that checks floating-point registers across switch types, confirming two problems.

The first is voluntary switching, i.e. rt_thread_yield: SAVE_CONTEXT and RESTORE_CONTEXT save only integer callee-saved registers, so two threads using floating point overwrite each other’s fs0 through fs11. The report gives measured values: expected 0x3ff0000100000000, got 0x3ff0000000000000. The second is timer preemption: SAVE_ALL saves f0 through f31 but not fcsr, so the floating-point rounding mode and exception flags are silently altered. This class of bug does not crash — it just makes results drift slowly.

Maintainer BernardXiong proposed #12006 four hours later: append fs0 through fs11 and fcsr to the switch frame, add fcsr save/restore to the trap frame, round the switch frame size up to guarantee 16-byte alignment, and initialize fcsr for frames constructed for interrupt switches; offset and layout macros are added to context_ext.h and stack.h accordingly. The proposal is still under review with no on-hardware verification recorded. Given RISC-V’s weight in RT-Thread, this one should be merged with priority.

2.4 Review Queue: 142 PRs, 363 Issues (11-09)

Date: 2026-11-09 (check) Source: PR list, Issue list

Among the pending PRs updated in the window, six are worth watching:

  • APLIC level-interrupt MSI retrigger (#11966): under QEMU 8.2.2 with AIA configured, the counter print stops after test: 0; root cause is an unconditional write of setipnum_le at EOI, generating a spurious MSI even after the device has withdrawn the interrupt. The fix reads in_clrip first to check whether the interrupt is still valid before writing; it also changes main.c to a 0–9 counting loop to reproduce and observe delayed recovery.
  • Terminal tty ioctl user pointer (#11937, reported October 28, still unfixed): all RT-Smart boards affected since v5.1.0; this is arbitrary kernel read/write level and the highest-risk item in the queue.
  • RT-Smart mailbox fake object (#11960, reported October 31): present since v5.0.0, reproduced on QEMU AArch64 full-system, verified on RP2350 board.
  • ivshmem window validation (#11993, updated November 6): adds a fallback switch, off by default, validating size, address overflow, and pointer representable range before mapping. Still under review.
  • Touch framework tests (#12002), Bouffalo ADC channel validation (#12003), dlmodule regression (#11989), utest multi-round runs (#11983), and ulog output call sites (#11987) are all under review; the first four belong to the test infrastructure thread — see 4.1.
  • WCH fast interrupt configuration (#12004) and CH32V208 low power (#12007) depend on each other — see 4.2.

III. Official and Community Activities

3.1 Official news feed releases seven articles at once: from elexcon to the Wuzhen Summit (11-06)

Date: 2026-11-06 09:52 ~ 15:54 (publish time) Source: Official news list, Wuzhen Summit, RISC-V China Summit

The previous issue concluded that the official news feed was still stuck in June, with the latest entry being the June 17 Abu Dhabi Investment Forum. Starting on the morning of November 6 this issue, the feed released seven articles over the course of six hours, all bylined RT-Thread小师弟, but covering events from September through early November. In order of publish time: 09:52 Wuzhen Summit selected for “Xinguang”; 09:59 the 6th RISC-V China Summit; 10:18 the Industry Fair AI Car Workshop; 10:25 the Lingang Automotive Software Salon; 10:53 Southeast Asia university expansion; 13:03 the Vinaro Industrial PLC Salon; 15:54 elexcon Shenzhen Electronics Exhibition full-stack capabilities.

The common thread across the seven is obvious: the narrative is unified around AIOS hybrid deployment, edge AI, and the industrial/automotive three lines, with shipment figures uniformly stated as 2.5 billion units, 300,000 developers, and 17 million software package downloads. After more than four months of silence in external communications, everything was filled in at once, indicating the content team was consolidating activity drafts from the second half of the year. For the daily briefing, the value of these articles lies in stringing together the industry activities since September into a complete timeline; the events themselves are not new, and below they are labeled by activity date.

3.2 Wuzhen Summit: Heterogeneous Converged Edge Intelligence AIOS Base selected for “Xinguang” list (11-02)

Date: 2026-11-02 (event) / 2026-11-06 09:52 (publish) Source: Official news

On November 2, the 2026 World Internet Conference Wuzhen Summit opened under the theme of openness, openness, and shared building; the concurrent Light of the Internet Expo gathered more than 670 companies from 54 countries and regions. RT-Thread Ecosystem Director Li Yan presented “Virtualized Hybrid Deployment Embodied Intelligence Solution · AI Kit” at the expo, and the company’s self-developed RT-Thread Heterogeneous Converged Edge Intelligence AIOS Base was selected for this year’s “Xinguang” product recommendation list.

The technical description of the base still follows hybrid deployment: AI inference runs on the Linux side, real-time control on the RT-Thread side, with the two sides running independently so that anomalies on the AI side do not affect the control side, and control precision reaching the microsecond level; it is paired with the vmRT-Thread virtualization platform and the AI Kit toolchain. Embodied intelligence is explicitly named as the deployment scenario—multiple systems hybrid-deployed on the same hardware, respectively handling the brain’s compute elasticity and the cerebellum’s temporal determinism.

3.3 RISC-V China Summit: edge AI full stack, automotive-grade software already tested on vehicles (10-18)

Date: 2026-10-18 to 10-20 (event) / 2026-11-06 09:59 (publish) Source: Official news

The 6th RISC-V China Summit was held at the Futian venue of the Shenzhen Convention and Exhibition Center, featuring 1 main forum, 7 parallel sub-forums, and a Member Day. RT-Thread technical expert Zhang Bingru spoke at two sub-forums—Embedded IoT Intelligent Hardware and Automotive Electronics/Industrial Robots—with the titles “From Models on Chips to Agents Entering the Scene: RT-Thread’s RISC-V Edge AI Full-Stack Practice” and “RT-Thread and RISC-V in Real-Time Control for Automotive and Robotics” respectively.

The core judgment of the first talk is a shift in focus: edge AI has moved from whether models can run to whether agents can reside stably under constrained compute and real-time constraints. The approach is to shield kernel differences downward with a unified BSP and driver framework, carry offline wake-up, voice interaction, and multimodal inference upward with a lightweight runtime, and place AI tasks and real-time tasks within a single scheduling system to prevent AI from preempting real-time performance.

The second talk delivered two hard advances: automotive-grade base software has been applied to RISC-V chips and completed on-vehicle testing, and is now moving toward mass production; the Chengxuan vehicle control system can provide RISC-V with complete AUTOSAR CP base software, covering system services, storage, communication, diagnostics, calibration, and information security, along with configuration and code generation tools. On the robotics side, RT-Thread Smart has completed adaptation of dozens of ROS2 C/C++ software packages on SoC-level chips. The adaptation scope is stated as having started in 2018, covering more than 100 chips and BSPs licensed by IP vendors such as Nuclei, XuanTie, and Andes, with the kernel natively supporting SMP and AMP.

3.4 elexcon Shenzhen: 2.5 billion shipments and triple functional safety certification (09-09)

Date: 2026-09-09 to 09-11 (event) / 2026-11-06 15:54 (publish) Source: Official news

At the 23rd Shenzhen International Electronics Exhibition and Embedded Exhibition, RT-Thread Ruisaide exhibited its full-stack capabilities. The figures given in the article: founded in 2006, 300,000 developers, cumulative shipments of 2.5 billion units; for industrial and automotive markets it launched the Ruiqing Industrial Platform and the Chengxuan Vehicle OS, with customers named as State Grid and CRRC.

The hardest item is functional safety: Safety OS simultaneously obtained triple certification of IEC 61508 SIL3, EN 50128 SIL4, and ISO 26262 ASIL-D, and the article claims it is the only embedded operating system in China holding all three certificates at once. The AI side is consistent with previous statements: AIOS hybrid deployment has been validated in wafer fab overhead crane and six-axis robot scenarios, AI KIT provides one-stop development, and the AI flight control platform jointly developed with Infineon has performed AI fault detection on drones; during the exhibition it won the Edge AI Solution Innovation Award.

IV. Ecosystem and Vendor Adaptation

4.1 QEMU Virtual Device Checklist Advances: SPI Loopback, CAN, SDIO, DAC/I2C Enter CI (11-06)

Date: 2026-11-06 to 11-08 (merge time) Source: Issue #11972, PR #11979, PR #11990, PR #11752, PR #11758

This is the most systematic thread of the period. Issue #11972 is a checklist of QEMU virtual devices and coverage, and its background is stated plainly: per the release plan in #11955, Z releases rely mainly on QEMU plus CI to automatically test the kernel, components, and drivers within the scope of emulation support, aggregating coverage, pass rates, and known issues so maintainers can decide whether to release. The checklist lists utest and QEMU checkboxes item by item per framework, covering more than twenty items including adc, dac, i2c, spi, can, pwm, rtc, watchdog, timer, touch, audio, usb, sdio, flash, ethernet, wlan, pin, serial, and ipc.

Four PRs landed within the window:

  • SPI virtual loopback bus (#11979, 6 files, 154 lines): registers a pure-software SPI bus, default name spi2, using memory copies for loopback transfers, so qemu-vexpress-a9 can run SPI loopback cases even without a PL022 model; adds a matching utest configuration and CI matrix entry.
  • QEMU jobs for DAC and I2C (#11990): adds one utest configuration each, split into two independent jobs in the workflow.
  • CAN transmit/receive test (#11752, 1792 lines): a 1572-line test case file with 22 host stub scenarios, covering timeout renewal, tick wraparound, empty reads, error propagation, and normal reception; the author reproduced the original duplicate-frame and mismatched-frame hangs using a 50-tick timeout plus a 1000-tick watchdog.
  • SDIO block device read/write test (#11758, 438 lines): 372 lines of test cases, with validation limited to formatting and whitespace changes, without a full BSP build.

Two more PRs still under review belong to the same thread: the touch framework test (#12002) makes interrupt enable and disable return error codes and runs two consecutive rounds in QEMU using simulated operations; the dlmodule regression (#11989) generates real ARM ELF modules at build time, with 10 test cases covering relocatable objects, shared objects, symbol import/export, and repeated load/unload. Test infrastructure is shifting from scattered case additions to a checklist organized around the release process—a prerequisite for the Z release cadence.

4.2 Two WCH Threads: Nuclei Fast Interrupt Configuration and CH32V208 Low Power (11-07)

Date: 2026-11-07 to 11-08 (PR time) Source: PR #12004, PR #12007

WCH’s RISC-V Nuclei cores are inconsistent on fast interrupts: support varies by model, and models with only two hardware interrupt levels should not use fast interrupts. PR #12004 configures the corresponding core capabilities per chip series, adds a fast interrupt switch, and unifies the interrupt attribute macros, so supported chips use fast interrupts while the rest fall back to normal interrupts; it also updates the SDK and adjusts the CH32V203 startup file. Validation boards are CH32V208W-R0 and CH32V307V-R1.

#12007 adds PM component support for CH32V208 and depends on the previous PR being merged. Both remain open. WCH is one of China’s largest RISC-V MCU vendors by shipment volume, and a BSP’s power management and interrupt configuration directly determine usability in low-power scenarios.

4.3 Renesas RH850 G4KH Port Proposal: A Third Architecture Beyond ARM and RISC-V (11-06)

Date: 2026-11-06 20:41 (PR time) Source: PR #11998

libcpu/rh850 uses TRAP0 for thread switching, including nested interrupts, FPU context, and fault dumps; bsp/renesas/rh850 provides startup, interrupt controller, OSTM and RLIN3 serial drivers, plus the qemu-rh850-u2c board; CI covers both hard-float and soft-float builds plus kernel utest. The validation record is concrete: GCC 14.3 with picolibc toolchain v1.1.0, qemu-rh850 v1.0.0, msh starts, kernel_basic 22/22, and memory and ipc cases pass.

The PR is still marked draft because the utest CI needed ctime.c fixed under picolibc first; #11999 merged this period, removing that prerequisite. RH850 is a common architecture in automotive-grade MCUs, and RT-Thread has previously focused on ARM and RISC-V—if this PR merges, it amounts to validating the utest and libcpu abstractions on a third architecture.

4.4 Env Adds “Format Changed Files Only” Command (11-06)

Date: 2026-11-06 16:56 (commit time) Source: env commit c0081683

The env repository had only one commit in the window: adding the cmd_format_changed command, with README, command registration, pyproject, and entry point updated together. Its purpose is to format only the files changed in this round, working with the repository’s clang-format flow to avoid whole-repo formatting introducing unrelated diffs. A small tool, but a direct help for commit cleanliness.

4.5 New Community Repositories: CarPlay Receiver, Wi-Fi/Bluetooth Host Driver, and Quadruped Robot Dog (11-07)

Date: 2026-11-07 to 11-08 (repository update time) Source: rt-carplay, rtt-wifi-bt-host-driver, Mambo-dog-Riscv, ra8d1-vision-sorting

Four of the nine new repository candidates in the window are worth noting; all have very few stars and are recorded only as ecosystem observation: boa-z/rt-carplay builds a modular CarPlay receiver framework on RT-Thread; Aerolynq adds Wi-Fi and Bluetooth host drivers for a board based on an Infineon combo module; Mambo-dog-Riscv migrates a desktop quadruped robot dog from STM32F103 to CH32V303, retaining RT-Thread and fully offline voice control; ra8d1-vision-sorting uses RA8D1 plus RA6M5 for edge AI visual sorting, with a stack of LVGL, Edge Impulse, and Modbus RTU. These projects do not represent official direction, but they show the community’s spontaneous investment in three branches: in-vehicle connectivity, wireless connectivity, and RISC-V robotics.

V. Industry Applications and Industry-Education Integration

5.1 Ruiqing Goes into PLC: The “1+X+N” and Microsecond-Level Metrics at the Vinaro Salon (11-06)

Date: 2026-11-06 13:03 (published) Source: Official News

The Vinaro technical salon on industrial control and PLC, hosted by the Shanghai Open Processor Industry Innovation Center and guided by the Shanghai Municipal Commission of Economy and Informatization, was held at Chuangxin Tiandi in Pudong. Qiu Yi, co-founder of RT-Thread and head of its Industrial Business Unit, presented “RT-Thread Ruiqing Industrial Development Platform Accelerating Industrial Equipment Evolution,” outlining the “1+X+N” architecture: one unified foundational software platform including hardware abstraction, real-time scheduling, and toolchains; X is reusable industrial components, including protocol stacks, edge computing frameworks, and security modules; N is segmented industry solutions for power, industrial control, rail transit, and others.

The metrics are stated concretely: based on a hard real-time kernel, task response of no more than 1 microsecond and interrupt jitter of no more than 5 microseconds; already adapted to EtherCAT, Profinet, Modbus, CANopen, and OPC-UA; in mass production on three-electric control, industrial gateways, and PLC controllers. On the RISC-V side, the track record is adaptation work begun in 2018, more than 30 BSPs, and over a thousand chips, covering vendors such as Nuclei, GigaDevice, and XuanTie.

5.2 Automotive Software Salon: AI-Empowered Development, Core Initiating Member of the Lingang Alliance (09-16)

Date: 2026-09-16 (event) / 2026-11-06 10:25 (published) Source: Official News

The fifth technical salon of the Lingang Automotive Software Alliance was held at Horizon Robotics’ Lingang headquarters, guided by the High-Tech Division of the Lingang New Area Administrative Committee and organized by Lingang Qingchuanghui, the alliance, and Horizon Journey. Li Tianyi, technical development director at RT-Thread, presented “AI-Empowered Software Development,” arguing that deeply integrating AI capabilities with the operating system is the direction for breaking through bottlenecks in automotive software. The same event featured Horizon’s intelligent driving developer ecosystem, Drip Zhixing’s full-vehicle OS, Shangyan Zhilian’s compliance for overseas markets, and Zhizong Technology’s dual safety-and-security solution covering functional safety and information security.

RT-Thread’s role in the article is as a core initiating member of the alliance, with stated future directions covering automotive-grade OS adaptation, hardware-software co-design, safety and compliance, and local talent cultivation. This item and the automotive-grade on-vehicle testing in 3.3 are two expressions of the same business line: one describes technical progress, the other describes industry positioning.

5.3 CIIF AI Car Workshop: Breaking End-Side AI into Hands-On Steps (10-12)

Date: 2026-10-12 to 10-13 (event) / 2026-11-06 10:18 (published) Source: Official News

The 26th China International Industry Fair was held in Shanghai, and on October 13 RT-Thread ran an on-site hands-on workshop on AI end-side intelligent cars: teams of two, dozens of hardware teaching kits, covering everything from hardware detection, system boot, peripheral debugging, real-time control, SLAM mapping, autonomous navigation, camera calibration, multimodal visual following, and AR exercises, with debugging targets including LiDAR, IMU, and depth cameras.

The pedagogical significance of this item outweighs its product significance: it turns AIOS hybrid deployment into operable steps—AI inference on the Linux side, real-time control handed to RT-Thread, and AI anomalies not affecting device control. For university and research institute audiences, this demonstrates the engineering boundaries of end-side intelligent robots better than a booth demo.

5.4 Southeast Asia University Footprint: WOU Signing in Malaysia and Outreach to Six Universities (11-06)

Date: 2026-11-06 10:53 (published) Source: Official News

Domestically, partnerships already cover about 200 universities; overseas, the starting point is Southeast Asia: in 2025, cooperation was established in Thailand with Thammasat, Mahidol, King Mongkut’s, Rajamangala Thanyaburi, and other institutions as well as the Royal Society of Thailand; in early August this year, a trip to Malaysia included signing a university-industry cooperation agreement with Wawasan Open University, along with discussions with Universiti Malaya, Universiti Sains Malaysia, Universiti Tenaga Nasional, Xiamen University Malaysia, UCSI, and Universiti Malaysia Perlis on joint course development, application development, and joint laboratories.

The accompanying methodology is a five-dimensional industry-education integration model: joint course development, joint laboratory development, faculty training, certification bases, and talent pipeline. For RT-Thread, this is replicating the domestic university cooperation template overseas; for the domestic embedded talent market, there is no direct short-term impact, but once the certification system takes hold in Southeast Asia, it will in turn influence the overseas adoption path of domestic operating systems.

VI. Summary and Trend Observations

  • Eleven commits in three days, test infrastructure becomes the main thread: five on 11-06 (K230D, STM32 input capture, CAN and SDIO test cases, DAC and I2C CI), one on 11-07 (CPU time accounting), five on 11-08 (GIC, two timerfd, picolibc, SPI loopback). Compared with the single-day clearing peak of 31 commits on 11-05, this period is wrap-up plus infrastructure: the only genuinely new features are K230D and input capture, while more than half of the rest are filling in tests and fixing compiler warnings.

  • The security topic has shifted boundaries: previous periods focused on user pointers at the syscall layer, and this period merges two of those timerfd fixes; new reports turn to two categories, device-provided input (ivshmem, Bouffalo ADC channels) and architectural state (RISC-V’s fcsr and fs0 through fs11). The latter is more insidious: it won’t crash, it will only make floating-point results drift.

  • Version cadence remains at v5.3.0: no new tags or releases within the window, v5.4.0 is still on the development line, and defect reports reference master’s c63d7bc9. However, two programmatic documents for Z-version CI have appeared—the version management process in issue #11956 and the QEMU virtual device list in #11972—both ending in manual approval for release. The next observation point is whether these two lists can actually run end-to-end on QEMU.

  • Catching up on external communications: after a hiatus of more than four months, the official news feed published seven articles at once, stringing together September’s elexcon, mid-September’s automotive salon, October’s CIIF and RISC-V Summit, and early November’s Wuzhen Summit into a single line. The narrative is unified around AIOS hybrid deployment plus end-side AI, landing on industry, automotive, and robotics. The events are not new, but the messaging is now consistent.

Limitations and deduplication notes: This period’s window is 72 hours, covering content after 11-06 08:00; the five commits from 11-06 09:20 to 13:10 fall after the window start but belong to the same 11-06 merge batch as the previous report, and have been checked item by item for no duplication. The seven official news articles were published on 11-06, with events dating back to September 9; event dates are noted in the text and are not treated as new events in this period. Three Google News queries (RT-Thread three-day, Ruiqing Pi and Ruiqing three-day, RT-Thread three-day) only turned up an 11-03 reprint by Electronic Engineering Album and an 11-02 piece from the Shanghai Commission of Economy and Informatization, both outside the window and not included. The club forum still returns a WAF page, so posts could not be verified. The GitHub anonymous API was just sufficient for this period; no topic-level full repository search was performed.

Appendix: Source Verification Table

Source Verification Result
RT-Thread official news API Seven posts backfilled on 11-06, all included; event dates 9-09 to 11-02
Official website news page Consistent with the API; list page is client-rendered, so the API is authoritative
GitHub main repo commits 11 commits in the window, all verified by committer time
GitHub PRs and Issues 142 proposals and 363 issues pending review; 13 key items this issue had their bodies checked
RT-Thread org repos 35 repos checked; pushes in rt-thread and env only
releases and tags No additions; latest remains v5.3.0, released September 10
Google News Chinese Zero hits in the three-day window; 2 hits in the seven-day window, both outside the window
Google News English Zero valid hits
HN Algolia 2 hits, both networking or mailing-list discussions, excluded
EET China RT-Thread column 11-03 Wuzhen Summit repost, outside the window, used as corroboration only
club.rt-thread.org forum Still returns a WAF page; could not be verified
Community repo search 9 candidates; 4 included as ecosystem observations

Full Source List