arduino / arduino/ArduinoCore-mbed

Complication error/potential bad configuration?

Open
#687 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
411
Forks
225
PR merge metrics
No merged PRs in 30d

Description

Context:

- OS: Windows 11
- Using Arduino IDE
- Board being used: RP Pico (RP2040)
- Library required to complete project: _[SX126x-Arduino](https://github.com/beegee-tokyo/SX126x-Arduino)_
- Cloned arduinocore-mbed repo to "C:/users/xxxxxx/Arduino/hardware"
- Cloned arduinocore-api repo to "C:/RP240/"
- Created a symlink from /arduino-git/mbed/core/adruino to c:/rp240/arduinocore-api/api using Link Shell Extension (_mklink_ was causing me all types of challenges) (Link shell extension "Link Source" was api dir, dropped symbolic link in mbed/core/arduino dir)
- Installed the Arduino Mbed OS Nano Boards board manager for Arduino IDE (does this install all required ARM compiler toolchain elements?)

When compiling the LoRaWAN example from the _[SX126x-Arduino](https://github.com/beegee-tokyo/SX126x-Arduino)_ library , compilation failed with the error _#include no such file exists_ etc, within one of the source files for the SX126X library. Started doing some manual absolute file path changes to the library, but that lead me down a rabbit hole of absolute paths on absolute paths etc etc. Which leads me to think I have made some errors elsewhere?

Anyone else has similar issues/any suggestions?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Arduino Mbed OS Nano Boards installation and the LoRaWAN example from the SX126x-Arduino library, then trace why the source files cannot find mbed.h with the cloned arduinocore-mbed and arduinocore-api directories. Done means the example compiles on Windows 11 without absolute-path edits or missing-header errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
arduino, c
Domain
build-system, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.