platformio / platformio/platformio-core
Support UDOO boards
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9.5k
- Forks
- 905
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 2
Description
Two board classes:
- Neo (basic/extended/full variants all using Freescale™ i.MX 6SoloX applications processor with an embedded ARM Cortex-A9 core and a Cortex-M4 Core)
- Dual/Quad, using a separate Atmel® SAM3X8E
The manufacturer provides a patched Arduino IDE based on the board support package linked below. There are two firmware upload paths for the Neo:
- Run udooneo-m4uploader tool on the local Linux core
- Run udooclient on developer workstation, which uses a TCP connection to a service that runs m4uploader locally
For the Dual/Quad variants, the bossac tool is used (patched, see repository).
My main interest is in the Neo boards. I'm happy to have a go at writing the support, though I would probably need some help with that.
References
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced UDOO arduino-board-package and the two Neo upload paths, including udooneo-m4uploader and udoofota; compare them with the existing PlatformIO board-support structure. Define whether Neo, Dual/Quad, or both are in scope, then verify that the selected boards can build and upload firmware through their supported paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arduino, linux
- Domain
- build-system, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100