Problem with "wrong chip" when building and flashing ESP-AT

[uTasker]

Hi All

I am using ESP-IDF 5 to build ESP-AT. All looks to be fine until I try to flash my ESP32-S2-WROOM.

I run python build.py install
where there are choices [1..3]
Platform name:
1. PLATFORM_ESP32
2. PLATFORM_ESP32C3
3. PLATFORM_ESP32C2

so I choose 1.

Module name:
1. WROOM-32
...

so I choose 1.

The build is fine

But when flashing it errors with
"A fatal error occurred: This chip is ESP32-S2 not ESP32. Wrong --chip argument?"

So it seems that the platform name may be wrong, but there is no possibility to enter ESP32-S2 anywhere.

What coudl be going wrong?

Thanks in advance.

Regards

Mark

[uTasker]

UPDATE:

I may have understood the problem being that the ESP32-S2 is not supported in the latest branch so I switched to the branch "release/v2.1.0.0_esp32s2" and tried to follow the document
https://docs.espressif.com/projects/esp ... 0_esp32s2/

but now there are new issues.

I am supposed to do

export ESP_AT_PROJECT_PLATFORM=PLATFORM_ESP32S2
export ESP_AT_MODULE_NAME=WROOM
export ESP_AT_PROJECT_PATH=$(pwd)

to set the module information (I believe I need to do "idf.py export ESP_AT_PROJECT_PLATFORM=PLATFORM_ESP32S2" since just export doesn't work) but these all error with "string sub-command REPLACE requires at least four arguments"

Does this maybe mean that I can't use IESP-IDF 5.0 ??? Do I maybe need to downgrade?

Furthermore the reason why I want to build is because I need to use SPI mode - this release includes SDIO_AT mode but not SPI mode. Will this be a further issue?
I have 1000 ESP32-S2-MINI-I modules that I purchased before knowing that support was going to be dropped and want to some how be able to use them.

Thanks

Regards

Mark

[ESP_Sun]

UPDATE:

I may have understood the problem being that the ESP32-S2 is not supported in the latest branch so I switched to the branch "release/v2.1.0.0_esp32s2" and tried to follow the document
https://docs.espressif.com/projects/esp ... 0_esp32s2/

but now there are new issues.

I am supposed to do

export ESP_AT_PROJECT_PLATFORM=PLATFORM_ESP32S2
export ESP_AT_MODULE_NAME=WROOM
export ESP_AT_PROJECT_PATH=$(pwd)

to set the module information (I believe I need to do "idf.py export ESP_AT_PROJECT_PLATFORM=PLATFORM_ESP32S2" since just export doesn't work) but these all error with "string sub-command REPLACE requires at least four arguments"

Does this maybe mean that I can't use IESP-IDF 5.0 ??? Do I maybe need to downgrade?

Furthermore the reason why I want to build is because I need to use SPI mode - this release includes SDIO_AT mode but not SPI mode. Will this be a further issue?
I have 1000 ESP32-S2-MINI-I modules that I purchased before knowing that support was going to be dropped and want to some how be able to use them.

Thanks

Regards

Mark

Hi,

AT does not support SPI communication on S2 modules, but it supports SPI communication on C3 and C2 modules, so it is recommended that you switch to C3 or C2 modules.
C3 SPI AT Guide: https://docs.espressif.com/projects/esp ... PI_AT.html
C3 DOCS: https://docs.espressif.com/projects/esp ... index.html
C2 SPI AT Guide: https://docs.espressif.com/projects/esp ... PI_AT.html
C2 DOCS: https://docs.espressif.com/projects/esp ... index.html

[uTasker]

Hi

Thanks for the answer.

At the moment I can't switch chips as I have 1000 x ESP32-S2-MINI-I to use up and others won't fit in the product.

Can you answer the question about why it doesn't build? Do I need a different IDF or are there other issues?

Assuming I can manage to build the source I may look into trying to port some of the newer code to send just data over SPI. The AT commands over UART are fine but the traffic data rate is the issue.

Regards

Mark

[ESP_Sun]

Hi

Thanks for the answer.

At the moment I can't switch chips as I have 1000 x ESP32-S2-MINI-I to use up and others won't fit in the product.

Can you answer the question about why it doesn't build? Do I need a different IDF or are there other issues?

Assuming I can manage to build the source I may look into trying to port some of the newer code to send just data over SPI. The AT commands over UART are fine but the traffic data rate is the issue.

Regards

Mark

I don't think you can synchronize esp-idf externally, because the esp-at internal core no longer supports esp32-s2. Maybe you can replace the module with the merchant?

If you must use esp32-s2, another way is to completely rewrite the application layer based on the latest esp-idf.

I am very sorry for not proposing a better solution to this problem.