Hello,
I have the rebooting esp32 problem. I can't find out the cause but I can avoid it and reproduce it again.
I have these functions to access a device using SPI and everything is well, but when I wrap these functions in
an object class the rebooting problem arises. Any experience or ...
Search found 3 matches
- Thu Dec 26, 2024 1:58 pm
- Forum: Hardware
- Topic: esp32 rebooting due to weird cause
- Replies: 0
- Views: 733
- Mon May 08, 2023 11:06 am
- Forum: ESP32 Arduino
- Topic: PN5180 SPI protocol takes a long time
- Replies: 1
- Views: 2040
Re: PN5180 SPI protocol takes a long time
More details
Esp32 DevKitC
VSPI bus, mosi 23, miso 19, CLK 18, NSS 5, BUSY 21, RST 22.
I coded
1. waitForPinValue(busyPin, LOW, cmdTimeout) //cmdTimeout Is 10ms, checking interval 10us.
2. digitalWrite(nssPin, LOW)
3. delayMicroseconds(1000) // delay(1)
4. spi->transfer
5. waitForPinValue(busyPin ...
Esp32 DevKitC
VSPI bus, mosi 23, miso 19, CLK 18, NSS 5, BUSY 21, RST 22.
I coded
1. waitForPinValue(busyPin, LOW, cmdTimeout) //cmdTimeout Is 10ms, checking interval 10us.
2. digitalWrite(nssPin, LOW)
3. delayMicroseconds(1000) // delay(1)
4. spi->transfer
5. waitForPinValue(busyPin ...
- Mon May 08, 2023 1:34 am
- Forum: ESP32 Arduino
- Topic: PN5180 SPI protocol takes a long time
- Replies: 1
- Views: 2040
PN5180 SPI protocol takes a long time
Hi, I implemented an iso15693 inventory16 command on an esp32 controller using Arduino IDE AND a PN5180 nfc reader.
It works well, although collisions happen. But i had to delay the flow control 1ms after asserting NSS before wait for busy pin high. If i didnt that it doesn't work.
The problem Is ...
It works well, although collisions happen. But i had to delay the flow control 1ms after asserting NSS before wait for busy pin high. If i didnt that it doesn't work.
The problem Is ...