NG: Unable to communicate over SPI

[sergey-suloev]

Checklist

• [X] Checked the issue tracker for similar issues to ensure this is not a duplicate
• [X] Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• [X] Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

I expected to have SPI communication work as before.

Actual behavior (suspected bug)

I started experiencing SPI communication issues since I have updated my codebase from the current master branch. The problem is that the NG host driver can't get bootup event anymore. I investigated the issue with logic analyzer and what seems strange to me is that ESP does not rise DATA-READY event before sending bootup packet. This is most likely the reason why IRS isn't called and the packet doesn't arrive. I verified all physical connections again and they all look fine. Could you get an advice what I should try further, please.

Error logs or terminal output

root@nanopi-a64-bookworm:~# dmesg | grep esp
[    6.655317] esp32_spi: esp_spi_probe: Probing ESP32 SPI-driver...
[    6.669734] esp32_spi: esp_spi_probe: raw-tp-mode was not specified
[    6.683096] esp32_spi: esp_spi_probe: ESP32 peripheral is registered to SPI bus [0], chip select [0], SPI Clock [1], SPI mode [0x02]

Steps to reproduce the behavior

NG host driver with ESP32

Project release version

latest

System architecture

other (details in Additional context)

Operating system

Linux

Operating system version

Debian Bookworm

Shell

Bash

Additional context

Allwinner A64 (sun50i) / NanoPi A64

Session1.sal.zip