Instead of complicating recv() implementation.

Give a clearly dissuading tone on end users trying 512KB version
- it has to many end-usery features lacking.

If run-tests script is run from another dir, we still want to look up
feature checks in run-tests' dir.

As Zephyr currently doesn't handle MTU itself (ZEP-1998), limit amount
of data we send on our side.

Also, if we get unsuccessful result from net_nbuf_append(), calculate
how much data it has added still. This works around ZEP-1984.

A shorter name takes less code size, less room in scripts and is faster to
type at the REPL.

Tests and HW-API examples are updated to reflect the change.

Don't give a guarantee of HW RNG, only a possibility of its usage.

…ation.

If we got a CRASH result, return early, similar to SKIP. This is important
because previous refactor changed branching logic a bit, so CRASH now gets
post-processed into CRASH\n, which broke remote hardware tests.

stmhal doesn't have a machine.UART class so this section is not needed.

This is a user-facing change to the cc3200's API, to make it conform to the
new machine hardware API.  The changes are:

- change I2C constructor to: I2C(id=0, *, freq=100000, scl=None, sda=None)
- change I2C init to: init(*, freq, scl, sda)
- removal of machine.I2C.MASTER constant
- I2C str/repr no longer prints I2C.MASTER

To update existing code it should be enough to just remove the I2C.MASTER
constant from contructor/init for I2C.

The cc3200 port is now similar enough to the standard machine.I2C API so
that all conditionals can be removed.

This aligns the I2C class to match the standard machine.I2C API.

Note that this is a (small) breaking change to the existing cc3200 API.
The original API just returned the size of the input buffer so there's no
information lost by this change.  To update scripts users should just use
the size of the buffer passed to these functions to get the number of bytes
that are read/written.

cc3200 has been updated to conform to the API and now returns None.

It controls the character that's used to (asynchronously) raise a
KeyboardInterrupt exception.  Passing "-1" allows to disable the
interception of the interrupt character (as long as a port allows such a
behaviour).

Sometimes when setting a channel callback the callback fires immediately,
even if the compare register is set to a value far into the future. This
happens when the free running counter has previously been equal to what
happens to be in the compare register.

This patch make sure that there is no pending interrupt when setting a
callback.

…df/html/db/dc1/group__rtc__apis.html#ga826b88529aef76135636c06d408513aa

…utines

Proper deepsleep as proposed upstream

Minor Cleanup

This reverts commit 81b50c5.

Roosted7's update to latest ESP-IDF

… module