GitLab

New post_install.sh script that works for Nano Every

correct spelling of UNO

Fix legacy `upload.network_pattern` rule

Fix bug in analogWrite when accessing 16 bit register

Add support for pluggable discovery

Patch to allow use of precompiled libraries

ldflags added to allow precompilation.

Remove unnecessary HID library

The library was inherited from the "Arduino AVR Boards" platform that was the model for this project. It is used by the ATmega32U4-based boards of Arduino AVR Boards, however this platform's boards do not have a native HID capability and so the library serves no purpose, and in fact will not even compile for this platform's boards. So it will be best to remove it.

Disable verbose output in sketch compilation CI logs

Add "smoke test" sketch compilation CI workflow for MuxTO firmware

On every push and pull request that affects relevant files, and periodically, compile the Nano Every's MuxTO firmware sketch.

The binary is saved as a workflow artifact to make it available for beta testers who might prefer flashing it directly
over setting up the toolchain needed to compile it locally.

Due to the standard output from Arduino CLI not providing the correct size data, a bespoke check is done for whether the
compiled binary will fit in the available 12 kB of memory. If not, the workflow run fails.

On creation or commit to a pull request, a report of the resulting change in memory usage of the sketch will be
commented to the PR thread.

The `arduino/compile-sketches` action was previously configured for verbose output.. This option is primarily intended to be used for troubleshooting and doesn't contain any information of value for general usage.

Due to the extensive coverage of this CI workflow, the logs are massive, which makes it inconvenient for anyone to read them to identify the cause of a failure. Removing the verbose output will improve that situation

Use established KEYWORD_TOKENTYPE for Wire keyword

Update GitHub Actions actions used in sketch compilation CI workflows

The reliance on the `actions/upload-artifacts` action as the transfer mechanism between workflow runs means that these
values will always be hardcoded into the workflow. The result is that if the default values of the inputs are changed, it
breaks the workflow, even if the changes are synchronized. So it's more robust to avoid dependening on the default
values.

The "smoke test" sketch compilation and reporting actions have been moved to dedicated repositories. The actions hosted
at the old `arduino/actions/libraries/*` location will no longer be maintained.

Since the time the actions were migrated to the dedicated repositories, a breaking change was made to the default value
of the `sketches-report-path` input, which required a change to the values of the `name` and `path` inputs of the
`actions/upload-artifact` action.

All the other platform bundled libraries use `KEYWORD1` for the library's global instance so this provides consistency.

Use authenticated API requests in "Compile Examples" CI workflow

The arduino/compile-sketches GitHub Actions action used in the "Compile Examples" workflow queries the GitHub API for the base ref of the pull request, which is used for the memory deltas determination.

There were a couple workflow runs recently (1, 2) that failed due to rate limiting. Authenticated API requests are given a more generous API request allowance, so providing the action with the automatically generated GitHub access token should prevent this from happening again.

Instruct the compiler to generate a map file during the compilation

Instruct the compiler to generate a map file during the compilation process which is sometimes useful for debugging.

Changing return type of 'requestFrom' from uint8_t to size_t allows the function to return the correct amount of bytes read (since internally it's already a size_t which is downcast to a uint8_t upon returning it. (#92)

Bugfix: wrong default I2C baud rate was set for Arduino Nano Every

This reverts commit d316aa62 to allow running CI tests on a known baseline

Update platform specification URLs in configuration files

The Google Code URL in boards.txt is very outdated. The URL in platform.txt is to a more recent home of the content,
which has been replaced with a link to the new location, but while I'm updating boards.txt, I might as well point both
URLs to the real page.

Show correct compiler error message in UART0.cpp