Skip to content
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 parsing Arduino additional board json files? #969

Open
fake-name opened this issue May 28, 2017 · 2 comments
Open

Support parsing Arduino additional board json files? #969

fake-name opened this issue May 28, 2017 · 2 comments
Labels

Comments

@fake-name
Copy link

I recently purchased a Arducam ESP8266 module, and it only has support for the Arduino Text-editor+macro button build system "IDE". It also appears to not exist in the platformio framework (not surprising, it's new and kind of esoteric.

Anyways, I was wondering if it would be possible for platformio to parse either the arduino compatible "index.json", or the various metadata files in the underlying github repository. It seems like it should be possible to infer the required configuration from these files to build a binary for the board, but that could be me being naive.

@Belisarith
Copy link

Belisarith commented Jun 23, 2017

I'll second that request.
The arduino ide json file is located here:
http://www.arducam.com/downloads/ESP8266_UNO/package_ArduCAM_index.json

You can get working a nodemcu or the arducam uno board if you select the nodemcu in platform.io and put the arducam library into your lib folder. However, if you do it this way, there is data loss when taking pictures.
The problem somehow has to do with the standard libraries for the esp8266, see this github link.
https://github.com/ArduCAM/Arduino/issues/101

If you follow the way described by arducam using the arduino ide the pictures are fine.
So I suppose the makers of arducam somehow modified the esp8266 libraries. But I don't see a possibility to include these modified files when working with platform.io, because always the standard libraries of the framework are compiled. This is way over my level of expertise. Therefore, it would be nice if arducam would be included as one board into platform.io or someone could explain how to force platform.io to take the libraries of the lib folder instead of the framework libraries.

Furthermore, I think it would be huge benefit if there would be some kind of tool to migrate boards by using the json file of the arduino ide and make the necessary migrations to include these boards thereby into platformio. Again way over my level of expertise.

@ivankravets ivankravets changed the title [Feature Request] - Support parsing Arduino additional board json files? Support parsing Arduino additional board json files? Jul 4, 2017
@ivanscorral
Copy link

As the use of generic boards with rare chips and community-made boards becomes more prevalent, it is important to have support for them in the PlatformIO ecosystem. I propose that a "Community Custom Boards and Platforms" repository be created within PlatformIO. This repository would allow users to share information and configurations for custom boards and platforms, making it easier for others to use them in their projects.

I'll explain two features that I would consider very useful, and should be prioritized as such.

Arduino to Platformio conversion

I also propose the development of an automated tool for converting existing Platforms/Boards/Frameworks to PlatformIO. This tool would analyze the existing platform, generate necessary files and configurations, and test for compatibility to ease migration to PlatformIO. This feature would simplify migration and make it more accessible to a wider range of users, as well as reducing the effort of maintaining and updating for multiple platforms
For example, if a user wanted to use a generic board with a rare chip in their project, they could search the repository for that board and find information about its specifications, compatibility with different software and libraries, and any known issues or workarounds. They could also download configuration files and examples directly from the repository, making it easy to get started with the board.

Community made packages/boards/platforms

Additionally, by sharing information about custom components in a central location, it would encourage collaboration and knowledge-sharing within the community. This would benefit everyone by making it easier to use custom components and encouraging innovation in the field.

This feature would be beneficial for the community of PlatformIO users, making it easier to use custom components and encouraging innovation in the field. It would also help for those that are new to the field to quickly understand the differences between different boards and make a decision on which one to use for their projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants