arduino / arduino/ArduinoCore-mbed
Please clarify WiFi, BLE and Ethernet capabilities on the PortentaH7 M4 core.
- Dominant language
- C
- Stars
- 411
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
As far as I can tell, WiFi, BLE and Ethernet only work when activated from the M7 core. Can someone clarify if any of these 3 can be run from the PortentaH7 M4 core, (using RPC if Serial print is needed etc) ?
Also if any of the 3 can't run from the M4 core is this a physical hardware issue or is it something that could be fixed using software?
I am also having some issues running (WiFi, BLE, Ethernet and LoRaWan) from within a thread, is that a known issue?
My reasoning for the question is: I do a lot of CPU intensive [EdgeImpulse.com ](https://www.edgeimpulse.com/) machine learning vision coding with the PortentaH7 connected to either the Ethernet or LoRa Vision Shields and the machine learning code must be on the faster M7 core, meaning communication needs to be done from the slower M4 core. The only communication success I have had using the M7 Core is with bare bones LoRa peer-to-peer communication directly using the Murata module (see [MKRWAN issue 107](https://github.com/arduino-libraries/MKRWAN/issues/107)), even Arduino LoRaWan using the [MKRWAN library](https://github.com/arduino-libraries/MKRWAN) seems to have some threading issues.
Sorry to be a pain, but the whole point of the dual core Arduino is to be able to put extra processes on the other core.
Jeremy aka rocksetta on Twitter
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no file, test, or code entry point. Start by tracing PortentaH7 M4/M7 support for WiFi, BLE, Ethernet, and threaded operation, then review the linked MKRWAN issue and library context. Done means documenting which capabilities work from M4, whether limits are hardware or software, and the threading behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100