Research window: Past 24 hours (2026-09-09 11:18 ~ 2026-09-10 11:18 Beijing Time) Sources: RT-Thread official news API, GitHub (org: RT-Thread main repo commits / PR / package index repo, topic:rt-thread ecosystem repos), Google News aggregation (zh-CN / en-US, via proxy), Chinese industry media (EE Times China / Breadboard Community, etc.; see appendix source verification table for details)

Index

  • I. Kernel and Version Updates
    • Renesas RZ/N2L interrupt duplicate dispatch fix merged: Cortex-R52 trap layer and FSP vector table double dispatch caused serial interrupt misattachment after CANFD enable (PR #11765) (09-10)
    • Rust component build script removes toml dependency in clean phase (PR #11791) (09-09)
    • Review queue observations: Renesas SCI SPI fix PR newly opened, QEMU documentation PR newly opened, Copilot-submitted FinSH console hardening PR closed without merge (09-09 ~ 09-10)
  • II. Official and Community Events
    • elexcon 2026 Shenzhen International Electronics Show enters second day, RT-Thread “AI Hardware Full Stack” booth continues exhibition (09-09 ~ 09-10)
    • Official news API sees no new additions for the twenty-first consecutive day (09-10)
  • III. Ecosystem and Vendor Adaptation
    • GigaDevice ecosystem repo merges four GD32 BSPs in batch: 103c / 107c / 205r / e503v upgraded to new BSP architecture (09-09)
    • Package index adds STM32N6 HAL SDK package index (PR #2037) (09-09)
    • Ecosystem verification: recent awtk pushes are general GUI improvements, not RT-Thread-specific, excluded (09-09)
  • IV. Industry Applications
    • No new deployment case reports; AI industrial quality inspection challenge and elexcon booth remain the current industry-side activities (09-09 ~ 09-10)
  • V. Summary and Trend Observations
    • Three-day trend (09-08 ~ 09-10)
  • Appendix: Source Verification Table

I. Kernel and Version Updates

1.1 Renesas RZ/N2L duplicate interrupt dispatch fix merged: Cortex-R52 trap layer and FSP vector table double dispatch caused UART interrupt misrouting after CANFD enable (PR #11765)

Date: 2026-09-10 (merged 10:09 Beijing time)　Source: RT-Thread/rt-thread commits (PR #11765)

The only functional merge in the main repository during the window, and the most significant kernel-level fix of the day. PR #11765 [libcpu][cortex-r52] Fix duplicate interrupt dispatch on Renesas RZ (submitted by CYFS, merged by Rbb666) entered master on the morning of 09-10, with changes concentrated in libcpu/arm/cortex-r52/trap.c (+25/-27, single file).

The root cause was clearly described by the submitter: the RZ/N2L platform uses Renesas FSP (Flexible Software Package) to manage interrupt vectors, but the current Cortex-R52 trap handling, after calling bsp_common_interrupt_handler(), also treats the GIC INTID as an FSP vector table index and dispatches it again through RT-Thread’s isr_table—forming a double dispatch. After enabling CANFD, UART RX’s GIC INTID 321 incorrectly hits the CANFD TX ISR at g_vector_table[321], manifesting as entering the wrong interrupt and triggering a data abort as soon as Enter is pressed on the console. The fix removes the redundant dispatch, letting interrupts flow through a single path.

The PR was created on 08-28 and merged on 09-10 after roughly two weeks of review, marking another platform-level correctness fix in the Renesas BSP direction. Related observation: the long-standing PRs #11228 (hardware fault caused by klibc byte-aligned access) and #11313 (Renesas clock_timer divider settings), also in the Renesas and low-level direction, both received updates on the morning of 09-10 and remain in the review queue, indicating an accelerating review pace on the Renesas/KLIBC line.

1.2 Rust component build script removes toml dependency from clean phase (PR #11791)

Date: 2026-09-09 (merged 13:31 Beijing time)　Source: RT-Thread/rt-thread commits (PR #11791)

Another merge in the main repository during the window, affecting components/rust/examples/modules/SConscript (+3/-2), titled [rust][build] Avoid toml dependency during clean. Executing the clean target no longer depends on toml parsing, allowing the cleanup process to complete in environments without the relevant Python dependencies installed. The PR was created at 12:56 on 09-09 and merged at 13:31, taking about 35 minutes total—the fastest turnaround of the day; submitted by CYFS, merged by Rbb666.

The change itself is small, but viewed alongside two other Rust-related actions in the window, it shows that RT-Thread’s Rust component (the rust component example module) is in a period of continuous refinement: build script robustness optimization is a typical “housekeeping” maintenance task, usually appearing as support for a new language moves from “it runs” to “daily usable.”

1.3 Review queue observations: Renesas SCI SPI fix PR newly opened, QEMU documentation PR newly opened, Copilot-submitted FinSH console hardening PR closed without merge

Date: 2026-09-09 ~ 2026-09-10　Source: RT-Thread/rt-thread pulls

  • [bsp/renesas][drivers] Fix SCI SPI runtime configuration and transfer errors (PR #11792, CYFS3, created 09-09 17:25, 2 commits, +254/-193): While investigating SCI SPI loopback issues on the RZ/N2L EtherKit, several defects were found in the shared SCI SPI driver—the RZ divider interface passes false as the divider result pointer and does not use the actual clock source from the FSP configuration; runtime configuration is not reliably passed to FSP, and repeated configuration does not properly close the old instance; the configuration process mistakenly changes RT-Thread’s bit width unit from bit to byte; and after a send/receive wait times out or errors, the transfer length is still returned, causing the caller to misjudge success. The PR still received updates on the morning of 09-10 and is the next key review target on the Renesas driver line (same RZ/N2L EtherKit platform as 1.1).
  • [docs] point QEMU Linux quick start at qemu-nographic.sh (PR #11793, shiptux, created 09-09 23:53, +12/-0): Points out that the quick start documentation only mentions ./qemu.sh, but that script passes -serial stdio without -nographic, so QEMU attempts to open a GTK window and hangs at gtk initialization failed in display-less environments or over SSH; the BSP itself already provides qemu-nographic.sh and recommends it in the README for server scenarios, so the documentation is supplemented. This continues the same contributor’s documentation-fixing pace from the two documentation PRs on 09-08 (#11789/#11790).
  • Harden FinSH console switching against unsafe output devices (PR #11455, Copilot, closed 09-10 09:26, not merged): Created 06-09 with 5 commits total (+290/-18), this PR aimed to add device validation to rt_console_set_device(), allowing only devices that provide the console-safe-open flag or have interrupt/DMA asynchronous send capability to be switched to console, and retaining the old console until the new device passes validation, in order to eliminate crash paths caused by printing to blocking devices in ISR or fault-handling contexts. Closed unmerged after three months open, judged as a rejected approach (the other Copilot submission in the same batch, #11454 sys_getaddrinfo pointer hardening, is still under review). During the window, the main repository also had 3 newly opened PRs, 2 merges, and 0 new issues.

II. Official and Community Activities

2.1 elexcon 2026 Shenzhen International Electronics Show enters its second day, RT-Thread’s “AI Hardware Full Stack” booth continues exhibiting (09-09 ~ 09-10)

Date: 2026-09-09 ~ 2026-09-10　Source: elexcon official show overview (EE Times China event preview)

The 23rd elexcon Shenzhen International Electronics Show and Embedded Expo opened on 09-09 at the Shenzhen World Exhibition & Convention Center (Bao’an), running 09-09 to 09-11, held concurrently with CIOE (China International Optoelectronic Exposition) and the IC Innovation Expo, with a total scale of 340,000 square meters and the theme “All for AI, All for Green,” covering key segments including chips, storage, embedded and edge AI, power and power semiconductors, and automotive electronics. The concurrently held 8th China Embedded Technology Conference takes the form of a main forum plus three themed sub-forums on edge AI, robotics innovation, and industrial and energy management.

RT-Thread, positioning itself under “more than an operating system,” is exhibiting an “AI Hardware Full Stack” at the show, with its booth in Hall 16. No post-show official press release or on-site report landed during the window; coverage remains dominated by the event preview published on 08-30, so this item is rated as “show in progress” and is not counted again as new news. The show closes on 09-11, and further new product and signing information is expected to be released in the latter half of this week.

2.2 Official news API sees no new additions for the 21st consecutive day (09-10)

Date: 2026-09-10　Source: RT-Thread official news API (RT-Thread official website news center)

The latest entry returned by the official news API remains the 2026-06-17 “RT-Thread invited to attend the 2026 Abu Dhabi Investment Forum,” and the RT-Thread official website news center list likewise shows 06-17 as the latest, marking the 21st consecutive day with no new additions. This gap is consistent with the overall pace from 08-10 to 09-10: official external press releases are infrequent, community and engineering-side developments are mainly reflected through GitHub repositories and third-party media, and this report’s collection accordingly uses GitHub as the primary source.

III. Ecosystem and Vendor Adaptation

3.1 GigaDevice Ecosystem Repository GD32: Four BSPs Merged in Bulk — 103c / 107c / 205r / e503v Upgraded to New BSP Architecture (09-09)

Date: 2026-09-09 (13:52 ~ 19:56 Beijing Time)　Source: GD32-MCU-IOT/gd32_rt-thread commits

topic:rt-thread In the ecosystem repository, the GD32 downstream repository (GD32-MCU-IOT/gd32_rt-thread) merged four BSP branch PRs in bulk within the window — the largest set of ecosystem-side actions for the day:

  • gd32103c-eval (PR #69, merged at 13:52, 26 files +4783/-2341): Completes BSP board-level initialization and IDE project templates for the GD32F103VCT6 (Cortex-M3), enabling compilation, flashing, and passing utest under all three toolchains — Keil (AC6) / GCC / IAR — and adds F10x driver configuration headers and board-level initialization.
  • gd32205r-start (PR #65, merged at 15:09, 18 files +6294/-6283): Adds board_msd_init.c to complete UART GPIO initialization, removes UART RX DMA-related Kconfig and rtconfig.h options, and updates project files to chip family GD32F20xxE.
  • gd32107c-eval (PR #66, merged at 19:38, 15 files +4213/-2439): Upgrades to the new GD32 BSP architecture, adding f10x dma/uart/spi/i2c configuration headers, SOC_SERIES_GD32F10x series support, and board_msd_init.c.
  • gd32e503v-eval (PR #67, merged at 19:56, 35 files +10876/-2525): Adapts the e503v system and common peripherals, covering GPIO, I2C, SPI, USART, and DMA.

The common thread across all four changes is “migration to the new GD32 BSP architecture”: uniformly adding board_msd_init.c board-level initialization, uniformly rearranging Kconfig/.config options, and uniformly refreshing Keil/IAR project files. Contributors are junying2025 and yuanshuo0, representing vendor-led submissions from GigaDevice’s ecosystem side. This repository is an RT-Thread downstream repository rather than the main repository; its content is board-level adaptation of the GD32 device family (all ARM Cortex-M cores in this case) on RT-Thread, included as an observation window into vendor ecosystem progress.

3.2 Package Index Adds STM32N6 HAL SDK Package Index (PR #2037)

Date: 2026-09-09 (merged at 15:26 Beijing Time)　Source: RT-Thread/packages commits (PR #2037)

The RT-Thread package index repository added one entry within the window: [hal_sdk] add stm32n6 package repository index (submitted by yans6666, created 09-09 14:10, merged 15:26, reviewed by Rbb666). This lands the package repository index for the STM32N6 series HAL SDK, enabling developers to directly reference STM32N6 HAL support in the package manager. STM32N6 is STMicroelectronics’ high-end MCU series with a proprietary NPU; the index landing means RT-Thread integration for this platform has entered the packaging stage, forming the same vendor line as recent STM32-oriented driver adaptations (BDMA for SPI, Ethernet driver adaptation to the new HAL API).

3.3 Ecosystem Verification: Recent awtk Pushes Are General GUI Improvements, Not RT-Thread-Specific, Not Included (09-09)

Date: 2026-09-09　Source: zlgopen/awtk commits

topic:rt-thread Under the tag, zlgopen/awtk still had pushes within the window (09-09 17:47). Item-by-item verification of the commit contents shows general GUI component optimizations such as remove duplicated bsearch code, improve combo_box, and improve emitter_dispatch_log, with no involvement of the RT-Thread adaptation layer. Per established practice, these are marked as “ecosystem reference, not specific” and not counted as news items for the day.

IV. Industry Applications

4.1 No New Deployment Case Reports; AI Industrial Quality Inspection Competition Topic and elexcon Booth Are Existing Industry-Side Actions (09-09 ~ 09-10)

Date: 2026-09-09 ~ 2026-09-10　Source: Full source verification for the day (see appendix)

No new industry deployment case reports were found within the window (zero new additions across industrial, automotive, and robotics/embodied intelligence directions). The existing substantive industry-side actions remain two: first, the 2026 Shanghai Open Source Software Application Innovation Competition features an “AI Industrial Quality Inspection” topic with a total prize pool of 1 million yuan; RealSyde (睿赛德) already livestreamed an interpretation of the competition topic on 09-08, and registration and submission channels remain open; second, elexcon 2026 features embedded and edge AI and robotics innovation as sub-forum themes on-site, with the RealSyde booth displaying a product portfolio for AI hardware — usable as an industry-side observation window, though neither has new public materials within this window.

V. Summary and Trend Observations

Key Points of the Day

  • During the window, org: RT-Thread had 3 total commits (2 in the main repository + 1 in the package index), with 3 new PRs and 0 new Issues in the main repository, making it a typical low-news day; content quality was concentrated on the Renesas platform.
  • The most significant item of the day was PR #11765: a fix for CANFD/serial false interrupts caused by duplicate interrupt dispatch on Renesas RZ/N2L, a kernel-level correctness fix with a review cycle of about two weeks.
  • The package index landed the STM32N6 HAL SDK index, advancing package-based onboarding for a high-end MCU platform by one step.
  • The official news API showed no new additions for the twenty-first consecutive day, leaving external communications still in a quiet period; the elexcon exhibition period (09-09 to 09-11) is the only confirmed event window this week.

Three-Day Trend (09-08 to 09-10)

  • 09-08: The main repository merged the NXP FRDM-MCXC162 BSP (PR #11785, landed after three days of review) and a Keil include path order fix (PR #11741); 4 new PRs were opened (Eclipse hidden directory exclusion, 2 QEMU documentation PRs, ch32 framework adaptation closed the same day); the package index updated the Tencent IoT SDK and autogen_parameter_manager configuration; the Windows Env v2.1.0 Release object landed.
  • 09-09: The main repository merged Renesas GPT PWM register reads (#11753) and removal of the toml dependency from the Rust build script (#11791); four BSPs were merged in a concentrated batch in the GD32 ecosystem repository; the package index added the STM32N6 HAL SDK; elexcon Shenzhen opened.
  • 09-10: The main repository merged the RZ/N2L interrupt dispatch fix (#11765); the Renesas SCI SPI fix PR (#11792) was newly opened and continued to be updated; Copilot’s FinSH console hardening PR (#11455) was closed without being merged.

Mainline Assessment

  • Renesas BSP is the most active vendor line this week: from 09-07 to 09-10 there were actions in this direction for four consecutive days (SDHI card detection, SCI SPI chip select write, GPT PWM register reads, RZ/N2L interrupt dispatch), all of which were correctness fixes at the driver and interrupt level rather than new board introductions, pointing to a maturity-polishing phase for the RZ series on RT-Thread.
  • “New NXP boards in, old tickets cleared” and “GD32 batch migration to the new architecture” form two parallel paths in the vendor ecosystem: the former is the intake rhythm of the main repository, while the latter is self-organized progress in vendor downstream repositories.
  • The pace of clearing the review queue is clearly divergent: small changes (Rust build about 35 minutes, package index about 76 minutes) pass quickly, while kernel- and driver-layer changes (Renesas interrupts 13 days, long-running KLIBC and clock_timer-type PRs spanning months) take significantly longer.

Limitations

  • In this window, Google News queries in both Chinese and English returned no valid hits for “RT-Thread” (the English side continued to hit Rotten Tomatoes film review-type noise), and the Chinese side only fell back to the 08-30 elexcon preview, so this report relies mainly on GitHub and the official API, with limited media-side coverage.
  • Information such as on-site new products and signings during the elexcon exhibition period is usually released in a concentrated manner after the event closes; at the time this report was published (the second day of the exhibition period), no public materials were yet available, so related items are rated as “in progress” rather than “new additions.”

Appendix: Source Verification Table

Source Verification Result
RT-Thread official news API (type=rt_org) The latest entry remains 2026-06-17, with no new additions for the twenty-first consecutive day
RealThread official website news center (rt-thread.com/col19) The list shows 2026-06-17 as the latest, consistent with the official API
GitHub org: RT-Thread repositories sorted by pushed Pushes within the window: rt-thread (09-10 10:09), packages (09-09 15:26); the most recent pushes of all other repositories are earlier than the start of the window
GitHub org: RT-Thread full commit search (committer-date > window start) 3 results: 2 in the main repository + 1 in the package index
GitHub main repository commits / PR / Issue Within the window, 2 merges, 3 new PRs (#11791 merged, #11792/#11793 pending review), 0 new Issues; #11455 closed without being merged
GitHub package index repository PR 1 new PR within the window, which was merged (#2037 STM32N6 HAL SDK index)
GitHub topic:rt-thread ecosystem repositories Four BSP PRs merged in the GD32 downstream repository (included); the awtk push was verified as a general GUI improvement (not included)
Google News aggregation (zh-CN, RT-Thread / 睿擎 / 睿赛德, 1-7 days) No valid hits within the window, only falling back to the 08-30 elexcon preview and a 09-08 open source competition article (already included in the previous day’s report); sports-related items with the same name were excluded
Google News aggregation (en-US, RT-Thread / embedded RTOS, 1-3 days) All were Rotten Tomatoes film review-type noise (“RT” matched as a split term), with no valid hits
HN (Hacker News) 1 hit within the 24-hour window, which was unrelated content (a multiplayer online programming tool) and was excluded
Chinese industry media (EE Times China / Breadboard Community, etc.) The latest public article related to RealThread remains the 08-30 elexcon event preview, with no new additions within the window
elexcon official website and exhibition information The exhibition is held from 09-09 to 09-11 at Shenzhen World Exhibition & Convention Center (Bao’an), RealThread booth in Hall 16, in progress