English is currently available.
RISC-V Microcontrollers DISCUSSION
Two MCU boards use RISC-V cores, but the same interrupt-driven UART driver does not work on both. Which platform details must be reviewed beyond the shared instruction-set name?
Reference: Zephyr: board porting guide (https://docs.zephyrproject.org/latest/hardware/porting/board_porting.html).
The instruction set does not make peripheral addresses, interrupt routing or clock trees identical. Read each MCU's interrupt-controller and UART documentation, including vector or dispatch setup, priority handling and the order used to acknowledge a pending condition.
Separate reusable protocol logic from register access and board initialization. Check the startup code and runtime's interrupt entry conventions, especially when mixing vendor libraries and custom assembly. A handler with the correct C name can still be connected through the wrong mechanism.
Bring up polling first, then a single interrupt source with a visible event marker. Test repeated events and simultaneous sources so a missing acknowledgement does not remain hidden. A supported board package can reduce porting effort, but its actual peripheral coverage still needs checking.
Back to RISC-V Microcontrollers community
