Arduino Q platform: supporting Ventuno Q variant and seeking feedback

Hi everyone,
I’m maintaining a dev-platform for Arduino Q family (Registry link).

Following up on my former post, I added Ventuno Q support. The latest v1.0.0-rc.5 of the platform is now available on both GitHub repository and PlatformIO Registry.

It covers the workflow from building&uploading to unit testing and debugging. The release also updates the framework and toolchain packages to the latest stable version, and it requires PlatformIO Core 6.2.0 or later.

After the implementation, I’ve put together a small set of local tests and run them on the board. These cover RPC communication including Serial monitor, runtime and memory behavior, floating-point operations and PWM timing, and GPIO and its interrupt handling. Although it strongly insists that the Q-oriented platform design works well, validations were still limited to the setups I have available.

Since the platform became publicly available, I’ve been surprised to see it appear high in the Registry. Yet I haven’t received any external issue reports, so I’m still unsure how much it’s being used or how useful it is in other people’s workflows.

If you’ve tried it, I’d love to hear how it went, even if everything worked well. Which board you’re using, whether you work directly on the board or through pio remote, and anything that was confusing or didn’t work would all be helpful.

I expect this to be the final candidate before the major release, and plan to leave some time for feedback and further testing. While keeping an eye on intermittent issues such as a timeout in unit testing, I’ll also add examples and improve the repository’s organization before publishing the stable version.

Thanks all,
Shin

Love it! The platform repo is missing an examples folder and (Github Actions) CI though. You should add that to have clear firmware starting points for a firmware and examples for each supported framework, see e.g. https://github.com/platformio/platform-ststm32/, which are then test-compiled by the CI to verify compilability.

What’s also missing is an SVD file (misc/svd/STM32U585.svd) sourced from https://www.keil.arm.com/packs/stm32u5xx_dfp-keil/overview/ (extract .pack as .zip). If already have debug capabilities with GDB then it should naturally be able to reference the SVD and see the “Registers” view in the debug sidebar in VSCode. Maybe it will need a set mem inaccessible-by-default off in the GDB init commands to convince it it’s fine to read peripheral memory.

I’d also make it clear in the name of the board(s) (https://github.com/lee-lab-skku/platform-arduinoq/blob/main/boards/uno_q.json#L38) that this is building a firmware for only the MCU (STM32) part of the Arduino Uno Q, and not a program for the MPU part (the Qualcomm QRB2210 processor that runs Linux).

I’d also link the platform in https://github.com/platformio/platform-ststm32/issues/869.

Thanks for the kind suggestions!
They are exactly what I’ve been looking for.

To answer:

  • Yes, examples and CI are planned for the major version.
    • Blink and Serial may be starting points, but given this platform’s
      unusual workflow, I’m still figuring out how far the examples should go.
    • Ideally, I’d have self-hosted runners on the boards to exercise and validate the full workflow, though that comes with maintenance costs.
  • SVD support is something I need to learn more about. I’m cautious about adding something unfamiliar at this RC stage.
    • But I’ll look into it and see whether I can safely include it in the release.
  • Updated board names in this commit.
  • Replied with the repo link on the issue.