Skip to content

Release v1.1.1 (hotfix)#12

Merged
w1ne merged 1 commit into
mainfrom
release/1.1.1
Jun 15, 2026
Merged

Release v1.1.1 (hotfix)#12
w1ne merged 1 commit into
mainfrom
release/1.1.1

Conversation

@w1ne

@w1ne w1ne commented Jun 15, 2026

Copy link
Copy Markdown
Owner

iolinki v1.1.1 — hotfix

Real-hardware validation on a Nucleo-F103RB (STM32F103RB, Cortex-M3) surfaced a build defect in the Zephyr UART PHY that shipped in v1.1.0.

Fixed

  • UART PHY did not compile on real hardware. uart_irq_update() returns void in current Zephyr, but the ISR used it in a boolean (if (!uart_irq_update(dev))). native_sim builds use the virtual PHY, so CI never compiled this path. Now called as a statement per the API.

Added

  • nucleo_f103rb board overlay (IO-Link UART on USART1).

Validated on silicon

  • Cross-builds for nucleo_f103rb: FLASH 25% (33 KB/128 KB), RAM 54% (11 KB/20 KB) — confirms the resource-constrained claim.
  • Flashed via openocd; boots and runs in thread mode (no fault) on the real MCU.
  • Note: full IO-Link master-over-UART exchange not run (the board's ST-Link VCP delivered no data in this environment — solder-bridge routing / USB-CDC limitation, not a code issue).

Patch release; no API changes.

uart_irq_update() returns void in current Zephyr; the PHY ISR used it in a
boolean (if (!uart_irq_update(dev))), so the UART PHY did not compile when
targeting a real board. native_sim builds use the virtual PHY, so CI never
exercised this path. Call uart_irq_update() as a statement per the API.

Validated on a Nucleo-F103RB (Cortex-M3): builds (FLASH 25% / RAM 54% of 20KB),
flashes via openocd, boots, and runs on silicon. Adds a nucleo_f103rb board
overlay (IO-Link UART on USART1). Bumps version to 1.1.1.
@w1ne w1ne merged commit ea6d991 into main Jun 15, 2026
6 checks passed
@w1ne w1ne deleted the release/1.1.1 branch June 15, 2026 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant