* making pio_calculate_clkdiv8_from_float round to the neareset 1/256 (not lower 1/256)
* chage rounding of all float clkdivs to round to neareset; default to nearest (which is a backwards incompatible change, but I think OK), and add ability to turn it off
* fix copy/paste errors in PICO_CONFIG
* Calculate size of FRAC field using its own MSB and LSB, rather than hoping that INT_LSB is in the right place
* Add a new REG_FIELD_WIDTH macro, and make the calculation of the clock-dividers more consistent
---------
Co-authored-by: Andrew Scheller <andrew.scheller@raspberrypi.com>
In some cases, the flash lockout task can start on the wrong core and
not have time to move to the correct core before exit is called. This
causes a timeout as the exit function is looking at the wrong core when
checking for the lockout task.
* Thow FATAL_ERROR when using post-processing functions after pico_add_extra_outputs
* Remove property definition, and rename to `PICOTOOL_PROCESSING_CONFIGURED` and `picotool_check_configurable`
* done -> configured
* Slight tweak to the config-extraction scripts.
A small logic bug meant they were reporting more false-positive warnings than they should have been.
* Small code tidy-up
- Re-synchronise the PICO_CMAKE_CONFIG: entries with the corresponding PICO_CONFIG: entries
- Fix a silly typo I made in #2002
- Enhance config-extraction scripts to catch similar typos in future
Tweaks compare_build_systems.py slightly so that it does not assume the
root directory of submodules, which arguably made the implementation a
little less intuitive.
* Remove btstack Segger RTT from pico-btstack
We now have this in the SDK so adding it again in pico-btstack leads to
link errors.
But it's possible to use the btstack RTT functionality by defining
ENABLE_SEGGER_RTT=1, and if we're not using pico_stio_rtt we still need
to add the btstack RTT source.
* Fix build issues when RTT is enabled
Fixes https://github.com/raspberrypi/pico-examples/issues/565
* Fixes to picolibc_interface
- Don't include bindings for tinystdio if picolibc was compiled with POSIX_IO.
- Add times() function, which seems to be missed, in the same pattern as settimeofday/gettimeofday.
* Adds check that ensures the Bazel and CMake Pico SDK version strings
stay in sync.
* Adds check that ensures the Bazel pins for external dependencies stays
in sync with the git submodule pins.
* Updates cyw43-driver pin in Bazel.
* Makes the checks for some build configurability options non-blocking.
* Add XIP cache maintenance API (fixes#2005)
Also add a cache clean to hardware_flash implementations, to avoid
losing pending writes on the subsequent invalidate.
* Fix comment typos, add to docs index, remove unnecessary defaulting of XIP_CACHE assertions on FLASH
* Fix sense of unsigned wrapping test
* update bazel build
---------
Co-authored-by: graham sanderson <graham.sanderson@raspberrypi.com>
* add support for machdyne werkzeug rp2040 board
* boards/machdyne_werkzeug: set default flash size for cmake
---------
Co-authored-by: inc <87362+inc@users.noreply.github.com>
It seems to be possible to get stuck in the loop which is checking for
abort. It can take 100s of iterations before an abort happens and on
each iteration we're clearing the abort interrupt even when it's not
required. If we only clear the abort when needed the lockup doesn't seem
to be reproducible.
Fixes#2025
* Add `pico_btstack_mesh` CMake library to link BlueTooth Mesh capabilities hidden in BTstack
* Add pico_btstack_mesh to docs
---------
Co-authored-by: theshteves <stevenkneiser@gmail.com>
The function is setting the callback after enabing the interrupt which
can cause a hang if a receive character is already pending.
Similarly we also have to clear the callback pointer only after the
interrupt is disabled.
Fixes#2009
Add the key files and partition table JSON to the link dependencies, to ensure the postprocessing is run when any of them are updated. Link dependencies seem to be the simplest way, as the elf file needs re-linking anyway given it has been post-processed, so this doesn't add any unecessary extra processing.
Without this fix, if you modify a pt.json file or a private key, the ouptut binary will not have the correct pt/key.
