8000 Esp32-s3 busio SPI watchdog reset · Issue #8000 · adafruit/circuitpython · GitHub
[go: up one dir, main page]
Skip to content

Esp32-s3 busio SPI watchdog reset #8000

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
HemQL opened this issue May 19, 2023 · 1 comment
Closed

Esp32-s3 busio SPI watchdog reset #8000

HemQL opened this issue May 19, 2023 · 1 comment
Labels
bug

Comments

@HemQL
Copy link
HemQL commented May 19, 2023

CircuitPython version

Adafruit CircuitPython 8.0.5 on 2023-03-31; ESP32-S3-DevKitC-1-N8R8 with ESP32S3
Board ID:espressif_esp323_devkitc_1_n8r8
UID:C7FD1A3EA8C9

Code/REPL

import board
import busio
spi = busio.SPI(board.IO36, board.IO35, board.IO37)
cs = board.IO40
print(“SPI initialized.”)

Behavior

Board resets to safe mode for reason: “Internal watchdog timer expired.”

Description

Also tested in 8.1.0-RC.0. I suspect that busio.SPI() is taking SPI0 used by the ESP32S3 to talk to its internal flash, rather than the SPI2 or SPI3 buses that are safe for the MCU to assign.

Additional information

Defining the SPI() object in the REPL does not immediately result in an error, and commands like print(some local variable) seem to still work, but most other commands result in a watchdog reset.
@HemQL HemQL added the bug label May 19, 2023
@anecdata
Copy link
Member

SPI0/1: GPIO26-32 are usually used for SPI flash and PSRAM and not recommended for other uses. When using Octal Flash or Octal PSRAM or both, GPIO3337 are connected to SPIIO4 ~ SPIIO7 and SPIDQS. Therefore, on boards embedded with ESP32-S3R8 / ESP32-S3R8V chip, GPIO3337 are also not recommended for other uses.

https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-reference/peripherals/gpio.html

@HemQL HemQL closed this as completed May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@anecdata @HemQL
0