With PPP support added to MicroPython this would be better
handled by creating a PPP-compatible firmware for Pico Wireless
and using the PPP module instead... I think.
The astatus value was being interpreted as FZ, F2 and F1 causing bizarre
readings and all other channels to be shifted one place.
Additionally the datasheet has been updated to re-order F5, F7 and F8 to
F7, F8, F5, so these channels have been re-ordered accordingly.
Note: This will turn sensor output from confusing abject nonsense into
what looks like pretty reasonable colour data and fixes#989.
The preferred method for installing the ARM toolchain has changed. The method currently shown results in a compilation failure:
```
arm-none-eabi-gcc: fatal error: cannot read spec file 'nosys.specs': No such file or directory
```
Refer to [pico-sdk issue 1529](https://github.com/raspberrypi/pico-sdk/issues/1529)
Fixes#978.
Includes the following changes:
Adjust log.exc to log.exception
7669f03cdc
Logging module dropped support for exc. These adjustments use the exception method instead.
force lowercase headers and force uppercase method
b4393ac65a
add compatibility for micropython above 1.19.0
d067b98dfd
* uasyncio is renamed to asyncio
* directly use core from asyncio
Co-authored-by: Stephen Jefferson <stephen@sjefferson.co.uk>
Co-authored-by: eyJhb <eyjhb@eyjhb.dk>
Co-authored-by: Fabian Clemenz <fclemenz@outlook.com>
while building all demos I found that several colors are uninitialized,
and where throwing an error when building.
I could have added the flag for dismissing that warning, but I felt
more explicit is better.
We've been maintaining a downstream patch to disable C++ exception
handling, which gives us some headroom before our builds get too big and
overwrite themselves at runtime.
Forgetting to apply this patch is a constant source of debugging
frustration. It turns out it can just be added to our USER_C_MODULES cmake
files instead, where it will implicitly be included when building against
our modules.