I have an application where I need to trigger short SPI transfers quite often (at around a rate of 13000 Hz) and on time. But a few times every second I'm unable to meet the deadline because something is blocking hardware interrupts from the peripheral.
Here's an illustration of the problem:
D1 is the SPI clock, D2 is a GPIO that I set high in the post-transaction callback and set low in the pre-transaction callback. The post-transaction call back also kicks off the next SPI transfer. As you can see, there's a more than 500 us gap when no transaction is running because it is not kicked off in time from the pre callback because it's delayed. I also observed some delays of 100-160 us.
Any ideas what's happening here? A higher priority interrupt maybe? How to raise the SPI peripheral's interrupts' priority? Thanks!
Interrupts from SPI master delayed
Jump to
- English Forum
- Explore
- News
- General Discussion
- FAQ
- Documentation
- Documentation
- Sample Code
- Discussion Forum
- Hardware
- ESP-IDF
- ESP-BOX
- ESP-ADF
- ESP-MDF
- ESP-WHO
- ESP-SkaiNet
- ESP32 Arduino
- IDEs for ESP-IDF
- ESP-AT
- ESP IoT Solution
- ESP RainMaker
- Rust
- ESP8266
- Report Bugs
- Showcase
- Chinese Forum 中文社区
- 活动区
- 乐鑫活动专区
- 讨论区
- 全国大学生物联网设计竞赛乐鑫答疑专区
- ESP-IDF 中文讨论版
- 《ESP32-C3 物联网工程开发实战》书籍讨论版
- 中文文档讨论版
- ESP-AT 中文讨论版
- ESP-BOX 中文讨论版
- ESP IoT Solution 中文讨论版
- ESP-ADF 中文讨论版
- ESP Mesh 中文讨论版
- ESP Cloud 中文讨论版
- ESP-WHO 中文讨论版
- ESP-SkaiNet 中文讨论版
- ESP 生产支持讨论版
- 硬件问题讨论
- 项目展示
Who is online
Users browsing this forum: No registered users and 138 guests
- All times are UTC
- Top
- Delete cookies
About Us
Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. ESP8266EX and ESP32 are some of our products.