[Question] RCP firmware was updated every time when board was powered on (TZ-931)

[briansuyu]

hi, i am debugging a strange behavior on my customized esp32 + esp32H2 board, the RCP firmware was updated every time when board was powered on. Here is the log:
idf version 5.2.2
esp thread br version: master

1. when board was powered on 1st time, the internel RCP firmware was not found and then reboot
   

2. after reboot, internal RCP firmare was found and running RCP firmware was not found and update process was perfomed
   

3. after 2nd reboot, then everything seems working
   

and every time when board was powered off ->on , it go through 1->3 again.

board connection:

I build several small example tests and test the 2 chips individually. Both chips seems working for those individual module tests.
Could i ask where might the problem be?

[gytxxsy]

hi, i am debugging a strange behavior on my customized esp32 + esp32H2 board, the RCP firmware was updated every time when board was powered on. Here is the log: idf version 5.2.2 esp thread br version: master

1. when board was powered on 1st time, the internel RCP firmware was not found and then reboot
   
2. after reboot, internal RCP firmare was found and running RCP firmware was not found and update process was perfomed
   

3. after 2nd reboot, then everything seems working
   

and every time when board was powered off ->on , it go through 1->3 again.

board connection:

I build several small example tests and test the 2 chips individually. Both chips seems working for those individual module tests. Could i ask where might the problem be?

The esp-thread-br example uses ESP32S3 + ESP32H2 by default (refer hardware platforms ). Are you sure you are using ESP32 + ESP32H2? If so, I would like to know if this is an issue that occurs every time. Could you provide more detailed steps to reproduce the problem?
In fact, I modified the project configuration to use ESP32 + ESP32H2, and the other configurations are basically consistent with those in the screenshot you provided (except that Wi-Fi is used instead of Ethernet), but I did not reproduce this issue.