PJRC only describes the integration into the classic DE 1.8.x.
August 11, 2021, 2:58pm
It is not possible at this time, but everyone is working to make it possible in the future.
Information about it in this feature request and the ones linked from it:
04:40PM - 15 Sep 20 UTC
08:05AM - 10 Jun 22 UTC
When will there be support for the Teensy boards?
The classic Arduino IDE never provided the support for what Paul requires, which resulted in the Teensyduino approach where the official Arduino IDE is significantly modified. This time around, we have the opportunity to provide those capabilities out of the box, both for Teensy and for any other boards that might have a use for them. This very complex infrastructure must be designed and implemented properly and that has taken a lot of work. But it is coming along very well.
If you're curious, you can see the RFCs here:
and the work in progress here:
03:37PM - 23 Jun 21 UTC
**Please check if the PR fulfills these requirements**
- [x] The PR has no du
… plicates (please search among the [Pull Requests](https://github.com/arduino/arduino-cli/pulls)
before creating one)
- [x] The PR follows
[our contributing guidelines](https://arduino.github.io/arduino-cli/latest/CONTRIBUTING/#pull-requests)
- [x] Tests for the changes have been added (for bug fixes / features)
- [x] Docs have been added / updated (for bug fixes / features)
- [x] `UPGRADING.md` has been updated with a migration guide (for breaking changes)
* **What kind of change does this PR introduce?**
This PR introduces quite a bit of changes to add support for Pluggable Discoveries as specified by the related [RFC](https://github.com/arduino/tooling-rfcs/blob/main/RFCs/0002-pluggable-discovery.md).
- **What is the current behavior?**
Currently the Arduino CLI uses a bundled `serial-discovery` tool to search for supported boards connected to serial ports, there is no support for boards connected to the network or 3rd party boards that require specific tools to be discovered.
There is currently no way for 3rd party platforms to specify a custom tool to run to discover boards.
* **What is the new behavior?**
After this PR is merged any platform will be able to specify custom tools to run at discovery time to find supported boards, for example when calling `arduino-cli board list`.
This change is fully retro compatible with platform that don't specify a discovery tool, the bundled `serial-discovery` tool will be used as a fallback.
Discovery tools will be internally loaded automatically when the Arduino CLI is initialized and run when necessary.
- **Does this PR introduce a breaking change, and is
Yes, they are documented in the `docs/UPGRADING.md` file.
* **Other information**:
See [how to contribute](https://arduino.github.io/arduino-cli/latest/CONTRIBUTING/)
(Arduino CLI handles all the non-GUI operations for all the Arduino development software, so anything like this must first be implemented in Arduino CLI, after which it propagates to the IDE)
December 9, 2021, 2:58pm
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.