Age | Commit message (Collapse) | Author |
|
|
|
cc3200 has been updated to conform to the API and now returns None.
|
|
|
|
|
|
The cc3200 port is now similar enough to the standard machine.I2C API so
that all conditionals can be removed.
|
|
|
|
|
|
stmhal doesn't have a machine.UART class so this section is not needed.
|
|
|
|
|
|
|
|
|
|
Don't give a guarantee of HW RNG, only a possibility of its usage.
|
|
|
|
Give a clearly dissuading tone on end users trying 512KB version
- it has to many end-usery features lacking.
|
|
Notes on WiPy incompatibilities with the standard module API are
moved under "Known issues" to its documentation.
|
|
Notes on WiPy incompatibilities with the standard socket module API are
moved under "Known issues" to its documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It's a standard function, and it's already described (in the library
intro) that for any given port, any function may be missing.
|
|
These are basic MicroPython API, and all ports should implement them.
|
|
MONO_xxx is much easier to read if you're not familiar with the code.
MVLSB is deprecated but kept for backwards compatibility, for the time
being.
This patch also updates the associated docs and tests.
|
|
|
|
Since eaef6b5324fa2ff425802d4abeea45aa945bfc14 writes are used instead of
reads.
|
|
* Fix mis-spelling of `ticks_add` in code examples.
* Be consistent about parentheses after function names.
* Be consistent about formatting of function, variable and constant names.
* Be consistent about spaces and punctuation.
* Fix some language errors (missing or wrong words, wrong word order).
* Keep line length under 90 chars.
Signed-off-by: Christopher Arndt <chris@chrisarndt.de>
|
|
|
|
esptool 1.3 now supports both Python 2.7 and 3.4+.
Updated github link to now-official espressif repo.
|
|
|
|
|
|
|
|
Render related constants grouped together, with common description.
|
|
User can override PYTHON executable before running script,
gen-cpydiff.py works only with Python3 and most systems register
its executable as 'python3'.
|
|
TODO: Remove WiPy-specific chunks.
|
|
|
|
This patch introduces the a small framework to track differences between
uPy and CPython. The framework consists of:
- A set of "tests" which test for an individual feature that differs between
uPy and CPy. Each test is like a normal uPy test in the test suite, but
has a special comment at the start with some meta-data: a category (eg
syntax, core language), a human-readable description of the difference, a
cause, and a workaround. Following the meta-data there is a short code
snippet which demonstrates the difference. See tests/cpydiff directory
for the initial set of tests.
- A program (this patch) which runs all the tests (on uPy and CPy) and
generates nicely-formated .rst documenting the differences.
- Integration into the docs build so that everything is automatic, and the
differences appear in a way that is easy for users to read/reference (see
latter commits).
The idea with using this new framework is:
- When a new difference is found it's easy to write a short test for it,
along with a description, and add it to the existing ones. It's also easy
for contributors to submit tests for differences they find.
- When something is no longer different the tool will give an error and
difference can be removed (or promoted to a proper feature test).
|
|
|
|
MicroPython guarantees '/' to be a path separator, so extra constant taking
precious ROM space are not needed. MicroPython never had such constant, only
one vendor port had it (now unmaintained).
|
|
WiPy is the only port with ADC and SD, so they shouldn't be included in
other ports' documentation.
|
|
On the PYBv1.0, X1 maps to A0, not B6.
|
|
|
|
|
|
|
|
This new function controls what happens on a hard-fault:
- debugging disabled: board will do a reset
- debugging enabled: board will print registers and stack and flash LEDs
The default is disabled, ie to do a reset. This is different to previous
behaviour which flashed the LEDs and waited indefinitely.
|
|
machine.time_pulse_us() is intended to provide very fine timing, including
while working with signal bursts, where each transition is tracked in row.
Throwing and handling an exception may take too much time and "signal loss".
So instead, in case of a timeout, just return negative value. Cases of
timeout while waiting for initial signal stabilization, and during actual
timing, are recognized.
The documentation is updated accordingly, and rewritten somewhat to clarify
the function behavior.
|