Closed vardan closed 1 month ago
It worked for me in https://github.com/espressif/esp-hosted/commit/61c9415c1eb619787cc151dadc708780a172a413
Just to re-clarify, if you use NG with https://github.com/espressif/esp-hosted/commit/61c9415c1eb619787cc151dadc708780a172a413 at both sides, ESP and host, it works, but when you use latest master, it doesn't work. Is this correct?
have you integrated resetpin and it is resetting the esp every time the kernel module is reloaded (on every insmod after rmmod)?
Can you please click a photo of setup for connections?
Yes, it is correct. Everything works on 61c9415c1eb619787cc151dadc708780a172a413
Yes, I am sure resetpin is toggled every time. Here's modprobe.conf file
root@stm32mp1-pixie:~# cat /etc/modprobe.d/esp32_spi.conf
options esp32_spi resetpin=95
I can also see esp32c6 module reloading every time kernel module is reloaded
It is a PCB, so no wires here
I strongly suspect some mismatch on my side, because I keep getting this behaviour not only on latest master but any commit later than the version I am currently on.
@kapilkedawat ++
Sorry, I found what the problem was - we use different CS than IO10 configured by default. I completely forgot to change that before building the firmware for ESP32C6. It works now.
Checklist
How often does this bug occurs?
always
Expected behavior
[ 17.082465] esp32_spi: process_esp_bootup_event: Received ESP bootup event [ 17.082502] esp32_spi: process_event_esp_bootup: Bootup Event tag: 3 [ 17.082517] esp32_spi: esp_validate_chipset: Chipset=ESP32-C6 ID=0d detected over SPI [ 17.082527] esp32_spi: process_event_esp_bootup: Bootup Event tag: 2 [ 17.082539] esp32_spi: adjust_spi_clock: ESP Reconfigure SPI CLK to 16 MHz [ 17.082548] esp32_spi: process_event_esp_bootup: Bootup Event tag: 0 [ 17.082558] esp32_spi: process_event_esp_bootup: Bootup Event tag: 1 [ 17.082567] esp32_spi: process_fw_data: ESP chipset's last reset cause: [ 17.082575] esp32_spi: print_reset_reason: POWERON_RESET [ 17.082587] esp32_spi: check_esp_version: ESP Firmware version: 1.0.3 [ 17.090100] esp32_spi: esp_reg_notifier: Driver init is ongoing [ 17.241949] esp32_spi: esp_cfg80211_get_tx_power: [ 17.452792] esp32_spi: init_bt: ESP Bluetooth init [ 17.453332] esp32_spi: print_capabilities: Capabilities: 0xe8. Features supported are: [ 17.453347] esp32_spi: print_capabilities: WLAN on SPI [ 17.453357] esp32_spi: print_capabilities: BT/BLE [ 17.453366] esp32_spi: print_capabilities: - HCI over SPI [ 17.453375] esp32_spi: print_capabilities: - BLE only
Actual behavior (suspected bug)
[ 1517.062899] esp32_spi: spi_dev_init: ESP32 peripheral is registered to SPI bus [5],chip select [0], SPI Clock [10] [ 1518.596709] esp32_spi: process_rx_buf: offset_rcv[0] != exp[12], drop
Error logs or terminal output
Steps to reproduce the behavior
Project release version
a4a5f00923b45f11d833a3631768f8f7ad1df868
System architecture
other (details in Additional context)
Operating system
Linux
Operating system version
OpenEmbedded Linux, kernel 5.10.116
Shell
Bash
Additional context
I am trying to bump both host and network-adapter to the latest version (a4a5f00923b45f11d833a3631768f8f7ad1df868) and there's clearly a mismatch of versions as I keep getting printouts of dropped packets. Can you guide me hot to interpret srcrevision in the kernel module description? It is clearly not a commit id it has been built on. Same for the network-adapter. Where can I see srcrevision there? It worked for me in 61c9415c1eb619787cc151dadc708780a172a413
I am using ST stm32mp151 MPU and ESP32C6-mini chip