Search found 3667 matches
- Sat Oct 16, 2021 12:50 pm
- Forum: ESP32 boards
- Topic: ESP32 hardware counter support status
- Replies: 2
- Views: 1255
Re: ESP32 hardware counter support status
There is work in progress: https://github.com/micropython/micropython/pull/6639
- Sat Oct 16, 2021 12:48 pm
- Forum: ESP32 boards
- Topic: ESP32: get which EXT1 pin caused wake
- Replies: 25
- Views: 70780
Re: ESP32: get which EXT1 pin caused wake
AFAIK, you are asking for information that does not exist. EXT0 and EXT1 cause a wakeup from deep sleep, which behaves like a reset. Any previous information of the code that was kept in RAM does not exist any more. So the only information available is about the hardware - the port bitmap.
- Sat Oct 16, 2021 8:35 am
- Forum: ESP32 boards
- Topic: ESP32: get which EXT1 pin caused wake
- Replies: 25
- Views: 70780
Re: ESP32: get which EXT1 pin caused wake
I did not look into the return code in detail, but my first impression was that of a bit map of GPIO pins. That would have the information about which pin fired.
- Fri Oct 15, 2021 8:12 pm
- Forum: ESP32 boards
- Topic: ESP32: get which EXT1 pin caused wake
- Replies: 25
- Views: 70780
Re: ESP32: get which EXT1 pin caused wake
@karfas: you are right, in that creating a method like machine.wake_ext1_status() similar to machine.wake_reason() in modmachine.c is pretty simple. Something like the code below. Doing that is not a problem, getting a PR merged may take some time. STATIC mp_obj_t machine_wake_ext1_status(void) { re...
- Fri Oct 15, 2021 8:57 am
- Forum: ESP32 boards
- Topic: ESP32: get which EXT1 pin caused wake
- Replies: 25
- Views: 70780
Re: ESP32: get which EXT1 pin caused wake
You could use a digital schmitt-trigger like 74hc14 + R-C-Diode instead of an op-amp, with a typical supply current of 2µA, or an Attinyx5 with a sleep current of <1µA, which would be woken up by the ext1 signal and creates the intended response. No external parts required.
- Thu Oct 14, 2021 3:08 pm
- Forum: Other Boards
- Topic: Teensy 4.0 & 4.1
- Replies: 290
- Views: 466342
- Wed Oct 13, 2021 11:42 am
- Forum: Other Boards
- Topic: Teensy 4.0 & 4.1
- Replies: 290
- Views: 466342
Re: Teensy 4.0 & 4.1
@loboris I made a PHY driver for the LAN8720 chip and tested it with a WaveShare LAN8720 board. It worked instantly (which means according to Murphy, it has nasty well hidden bugs). The connection is straightforward, with two aspects to take care of when using the Waveshare board: - the RXER pin of ...
- Mon Oct 11, 2021 11:49 am
- Forum: Other Boards
- Topic: Teensy 4.0 & 4.1
- Replies: 290
- Views: 466342
- Mon Oct 11, 2021 10:30 am
- Forum: Other Boards
- Topic: Teensy 4.0 & 4.1
- Replies: 290
- Views: 466342
- Mon Oct 11, 2021 8:31 am
- Forum: Other Boards
- Topic: Teensy 4.0 & 4.1
- Replies: 290
- Views: 466342
Re: Teensy 4.0 & 4.1
@loboris I made the board files for the SOM Vision carrier board. Maybe you could try the, It contains the Pin definitions for the Arduino and RPi header. Unfortunately, no hardware SPI pins are routed to these headers. So there is not hardware SPI then. It may be better to define the SODIMM pins in...