The rtc_set_datetime() from pico-sdk will validate the values in the
datetime_t structure and refuse to set the time if they aren't valid. It
makes sense to raise an exception if this happens instead of failing
silently which might be confusing (as an example, see:
https://github.com/micropython/micropython/pull/6928#issuecomment-860166044
).

Fixes #7346.

Add low power functionality configurable with:

    lan.config(low_power=True/False)

The supplied value for microseconds in datetime() will be treated as a
starting value for the reported microseconds.  Due to internal processing
in setting the time, there is an offset about 1 ms.

This change moves the datetime tuple format back to the one used by all the
other ports:

    (year, month, day, weekday, hour, minute, second, microsecond)

Weekday is a number between 0 and 6, with 0 assigned to Monday.  It has to
be provided when setting the RTC with datetime(), but will be ignored on
entry and calculated when needed.

The weekday() method was removed, since that is now again a part of the
datetime tuple.

The now() method was updated so it continues to return a tuple that matches
CPython's datetime module.

Initial support for machine.RTC on rp2 port. It only supports datetime()
method and nothing else. The method gets/returns a tuple of 8 items, just
like esp32 port, for example, but the usec parameter is ignored as the RP2
RTC only works up to seconds precision.

The Pico RTC isn't very useful as the time is lost during reset and there
seems to be no way to easily power up just the RTC clock with a low current
voltage, but still there seems to be use-cases for that, see issues #6831,
and a Thonny issue #1592. It was also requested for inclusion on v1.15
roadmap on #6832.
Signed-off-by: NKrzysztof Adamski <k@japko.eu>

This is the minimum change to fix the example code so it actually runs on
the majority of ports.

The current MicroPython app size is larger than the size allocated in the
partitions table.

Changes introduced are:
- the application offset is now loaded from the partition table instead of
  being hard-coded to 0x10000
- maximum size of all sections is computed using the partition table
- an error is generated if any section overflows its allocated space
- remaining bytes are printed for each section
Signed-off-by: NDamien George <damien@micropython.org>

Signed-off-by: NDamien George <damien@micropython.org>

Because these boards use the SPI flash cache in their bdev.c configuration.
Signed-off-by: NDamien George <damien@micropython.org>

Usage:

    usb = pyb.USB_VCP()
    usb.irq(lambda u:print(u, u.read()), usb.IRQ_RX)
Signed-off-by: NDamien George <damien@micropython.org>

This commit adds a few math functions to the source list in the Makefile,
and implements the log2f function, so that ulab can be compiled on the nrf
boards.  It also addresses part of #5162.

This fix prevents server.wait_closed() from raising an AttributeError when
trying to access server.task.  This can happen if it is called immediately
after start_server().

This commit fixes the following problems converting to/from Python integers
and ffi types:
- integers of 8 and 16 bits not working on big endian
- integers of 64 bits not working on 32 bits architectures
- unsigned returns were converted to signed Python integers

Fixes issue #7269.

Signed-off-by: NDamien George <damien@micropython.org>

Signed-off-by: NDamien George <damien@micropython.org>

Signed-off-by: NDamien George <damien@micropython.org>

Signed-off-by: NDamien George <damien@micropython.org>

Currently only advertising and scanning are supported, using the ring
buffer for events (ie not synchronous events at this stage).

The ble_gap_advertise.py multi-test passes (tested on a nucleo_wb55rg
board).
Signed-off-by: NDamien George <damien@micropython.org>

Updates the zephyr port build instructions and CI to use the latest
zephyr release tag.
Signed-off-by: NMaureen Helm <maureen.helm@nxp.com>

Zephyr's default value for CONFIG_NET_SOCKETS_POSIX_NAMES was changed
from false to true between Zephyr v2.5.0 and v2.6.0. This caused
conflicts in MicroPython, which uses the zsock_ prefixed functions, so
disable it.
Signed-off-by: NMaureen Helm <maureen.helm@nxp.com>

Zephyr's Kconfig symbols and defaults for SDHC/SDMMC disk drivers and
the disk access subsystem were reworked between Zephyr v2.5.0 and
v2.6.0. Update MicroPython accordingly.
Signed-off-by: NMaureen Helm <maureen.helm@nxp.com>

Following on from ef168348, this adds a
coverage build and running of the test suite on an ARM 32-bit Linux-based
architecture.
Signed-off-by: NDamien George <damien@micropython.org>

Signed-off-by: NDamien George <damien@micropython.org>

Signed-off-by: NDamien George <damien@micropython.org>

Prior to this commit, cache flushing for ARM native code was done only in
the assembler code asm_thumb_end_pass()/asm_arm_end_pass(), at the last
pass of the assembler.  But this misses flushing the cache when loading
native code from an .mpy file, ie in persistentcode.c.

The change here makes sure the cache is always flushed/cleaned/invalidated
when assigning native code on ARM architectures.

This problem was found running tests/micropython/import_mpy_native_gc.py on
the mimxrt port.
Signed-off-by: NDamien George <damien@micropython.org>

   "$(BUILD)/partition_table/partition  -table.bin" is typing mistake.
Signed-off-by: Nleo chung <gewalalb@gmail.com>

These are at the moment more or less identical to the Teensy 4.0 files,
except for the pins.csv file and the flash size.

This adds the machine.ADC class with the read_u16() method.  make-pins.py
and supporting files are updated to generate ADC information.

Besides Python features this includes the extmod modules which make use of
the Pin module, especially machine.softSPI, machine.SoftI2C and onewire.

Since not all boards support double fp, all board specific .mk files are
affected too.

Initial version, using the LP RTC clock.  It provides setting the date and
time with rtc.init() or rtc.datetime(), and reading the date and time with
rtc.datetime() or rtc.now().  The method weekday() reports the weekday of
the current date.  It starts with 0 for Monday.

The tuple order for datetime() and now() matches the CPython sequence:
(year, month, day, hour, minute, second, microsecond, TZ).  TZ is ignored
and reported as None.  Microsecond is provided at a best effort.

If a battery is not supplied, the default boot date/time is 1970/1/1 0:0:0.
With a battery, the clock continues to run even when the board is not
powered.  The clock is quite precise.  If not, using rtc.calibration() may
help.

Setting it to OSC_CLK interferes the utime module's functionality.  This is
still an area demanding an understanding.

So there is a 1-1 mapping of hardware timer to Python object.

The device is unreliable with the WFE included.  This needs further
investigation.

It supports three hardware timer channels based on the PIT timers of the
MIMXRT MCU.  The timer id's are 0, 1 and 2.  On soft reboot all active
timers will be stopped via finalisers.

Signed-off-by: NDamien George <damien@micropython.org>