-
-
Notifications
You must be signed in to change notification settings - Fork 792
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support UDOO boards #439
Comments
I can see this issue is just hanging there untouched for a long time, so as I'm also very much interested, maybe somebody can give any tips how to do this? If someone can give me some tips, where to start, I'd be glad to pick up this issue. Thanks in advance |
@onliner10 here is docs http://docs.platformio.org/en/latest/platforms/custom_platform_and_board.html I see that these boards are based on Atmel SAM. In this case, just need to add new board to https://github.com/platformio/platform-atmelsam and integrate uploading. |
I tried to just add new JSON manifest, but I think it's not as simple since it's not really Atmel SAM board but Freescale i.MX 6SoloX with integrated both M9 and M4 chips. I've went through their documentation on http://www.udoo.org/docs-neo/Advanced_Topics/Recompile_MQX_Libraries.html and it seems like we need some MQX libraries (whatever they are..). When I last tried uploading sketch compiled for due in Platformio, i was unable to upload it (whereas the ones compiled with their patched Arduino IDE uploaded without any issues). So, i tried to just copy all their board files from AppData and create new framework out of it, but I don't really think this is the good way |
Two board classes:
The manufacturer provides a patched Arduino IDE based on the board support package linked below. There are two firmware upload paths for the Neo:
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
The text was updated successfully, but these errors were encountered: