| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Damien George <damien@micropython.org>
|
|
Signed-off-by: IhorNehrutsa <Ihor.Nehrutsa@gmail.com>
|
|
Signed-off-by: Damien George <damien@micropython.org>
|
|
Synchronous access to pins directly via registers.
Signed-off-by: Ihor Nehrutsa <Ihor.Nehrutsa@gmail.com>
|
|
This board requires slightly different configuration to work. It is
important to hard reset (cycle power) if you try to initialize LAN and it
fails, before trying again with new parameters.
Discussion: https://github.com/orgs/micropython/discussions/11446
AliExpress purchase link: https://pt.aliexpress.com/item/1005002023196214.html
Signed-off-by: Elvis Pfutzenreuter <epxx@epxx.co>
|
|
Signed-off-by: Damien George <damien@micropython.org>
|
|
- Update guide for extending built-in modules.
- Remove any last trace of umodule in other docs.
This work was funded through GitHub Sponsors.
Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
|
|
This adds the freq and duty_u16 keyword settings to the constructor, and
sometimes other details in the PWM section.
For mimxrt a clarification regarding the PWM invert argument was added, and
for rp2 a few words were spent on PWM output pairs of a channel/slice.
|
|
Signed-off-by: Damien George <damien@micropython.org>
|
|
Incorporating PR #7356.
|
|
Signed-off-by: Tomasz 'CeDeROM' CEDRO <tomek@cedro.info>
|
|
It appears that strings in the documentation are typically single quoted.
|
|
Addresses issue #8083.
|
|
Add a new function to control whether held pins will retain their function
through deep-sleep.
Also document this function and explain how to use this in quickref to
retain pin configuration during deep-sleep.
|
|
The current pull=Pin.PULL_HOLD argument doesn't make a lot of sense in the
context of what it actually does vs what the ESP32 quickref document says
it does.
This commit removes PULL_HOLD and adds a new hold=True|False keyword
argument to Pin()/Pin.init(). Setting this to True will cause the ESP32 to
lock the configuration of the pin – including direction, output value,
drive strength, pull-up/-down – such that it can't be accidentally changed
and will be retained through a watchdog or internal reset.
Fixes issue #8283, and see also #8284.
|
|
This attempts to better explain how pull-ups and pull-downs operate in
deep-sleep mode.
|
|
Add brief documentation of the new `drive` keyword argument.
|
|
Update ADC documentation now that the new API is described in the main
docs.
|
|
It has been replaced by machine.bitstream.
Signed-off-by: Damien George <damien@micropython.org>
|
|
Document read_u16(), read_uv() and ADCBlock(). Mark old read(), atten()
and width() methods as legacy.
|
|
The bit-bang implementation was replaced with the RMT implementation in
599b61c08687ca077e3b0e115d5b76affcc673ca. This commit brings back that
bit-bang code, and allows it to be selected via the new static method:
esp32.RMT.bitstream_channel(None)
The bit-bang implementation may be useful if the RMT needs to be used for
something else, or if bit-banging is more stable in certain applications.
Signed-off-by: Damien George <damien@micropython.org>
|
|
The start keyword was removed in 18e48a71ee69557a5340c8652f2e73e586063be3
Signed-off-by: Damien George <damien@micropython.org>
|
|
Save and restore the same duty cycle when the frequency (or frequency
resolution) is changed. This allows a smooth frequency change.
Also update the esp32 PWM quickref to be clearer.
|
|
Signed-off-by: Damien George <damien@micropython.org>
|
|
The methods duty_u16() and duty_ns() are implemented to match the existing
docs. The duty will remain the same when the frequency is changed.
Standard ESP32 as well as S2, S3 and C3 are supported.
Thanks to @kdschlosser for the fix for rounding in resolution calculation.
Documentation is updated and examples expanded for esp32, including the
quickref and tutorial. Additional notes are added to the machine.PWM docs
regarding limitations of hardware PWM.
|
|
|
|
|
|
Anywhere a module is mentioned, use its "non-u" name for consistency.
The "import module" vs "import umodule" is something of a FAQ, and this
commit intends to help clear that up. As a first approximation MicroPython
is Python, and so imports should work the same as Python and use the same
name, to a first approximation. The u-version of a module is a detail that
can be learned later on, when the user wants to understand more and have
finer control over importing.
Existing Python code should just work, as much as it is possible to do that
within the constraints of embedded systems, and the MicroPython
documentation should match the idiomatic way to write Python code.
With universal weak links for modules (via MICROPY_MODULE_WEAK_LINKS) users
can consistently use "import foo" across all ports (with the exception of
the minimal ports). And the ability to override/extend via "foo.py"
continues to work well.
Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
|
|
See https://www.oshwa.org/a-resolution-to-redefine-spi-signal-names
|
|
This commit adds I2S protocol support for the esp32 and stm32 ports, via
a new machine.I2S class. It builds on the stm32 work of blmorris, #1361.
Features include:
- a consistent I2S API across the esp32 and stm32 ports
- I2S configurations supported:
- master transmit and master receive
- 16-bit and 32-bit sample sizes
- mono and stereo formats
- sampling frequency
- 3 modes of operation:
- blocking
- non-blocking with callback
- uasyncio
- internal ring buffer size can be tuned
- documentation for Pyboards and esp32-based boards
- tested on the following development boards:
- Pyboard D SF2W
- Pyboard V1.1
- ESP32 with SPIRAM
- ESP32
Signed-off-by: Mike Teachman <mike.teachman@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The default pins can be optionally configured by a board.
Fixes issue #6974.
Signed-off-by: Damien George <damien@micropython.org>
|
|
Signed-off-by: Damien George <damien@micropython.org>
|
|
Also remove trailing spaces on other lines.
|
|
See related #4581.
|
|
This allows the user to configure the maximum number of clients that are
connected to the access point. Resolves #5125.
|
|
See issue #3188.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
