Build fail for C6 (TZ-619) #56
Comments
|
The basic_thread_border_router example in esp-thread-br repo works as is on ESP Thread BR Board, which is ESP32-S3 + ESP32+H2. Please use ot_br example in esp-idf on ESP32-C6, but the single SoC solution is not recommended for production. In order to setup the Thread BR with C6 + H2, here are the steps for your reference:
Then there should be some output as below: |
|
Thanks, I was actually trying to setup it as C6+H2, so I will follow the ot_br example. Maybe the README.md for this project should be updated since it might be a bit confusion since it state that the project support any ESP32-S & ESP32-C systems: "Hardware Platforms
|
|
ot_br example is much easier to get start with on standalone modules. While it's still doable to run the basic_thread_border_router example on C6+H2, just need to connect more GPIO pins as described here: https://github.com/espressif/esp-thread-br?tab=readme-ov-file#standalone-modules. Your previous compile issue could be resolved by enabling |
|
Thanks you. However, once I connect the H2 to the C6 using all the 9 pins and start idf.py monitor, I get the following endless loop of messages: SPIWP:0xee |
|
@orenc75 Hi, could you please show us how did you connect the C6 with H2? You said you connect 9 pins, which pins did you use? |
|
Hi, I set the following pins: C6 side -> H2 Side I also set in menuconfig the following pins: |
|
@orenc75 Hi I tried to use the uart 0 for C6 to communicate with H2, and also used the GPIO19 and GPIO18 on c6, all things work fine. And what is the GPIO 10~13 used for in your apps? Did you enable RCP SPI in your project? If you use uart, please check both BR and RCP side, you should enable If you want to use SPI for communication between BR and RCP. You should enable BTY, did you try this example?
|
|
@zwx1995esp Regarding the setup using ot_br as @chshu wrote. It is not working for me either. I connect the three pins and followed the steps and this is the error I got: Leaving... abort() was called at PC 0x42006b1b on core 0 Stack dump detected TP : 0x407ea590 T0 : 0x37363534 T1 : 0x7271706f T2 : 0x33323130 MHARTID : 0x00000000 None Stack memory: ELF file SHA256: c76836d87 Rebooting... |
|
I see, so could you please try these steps again on the 0.let's checkout the ESP-IDF to this commit (Notice, please use 1.compile the RCP after removing all previous build files.
Only enable this config, please do not modify any others:
4.Open the C6 monitor |
|
If all things go as expected, you will see |
|
@zwx1995esp abort() was called at PC 0x42006b1b on core 0 Stack dump detected TP : 0x407ea714 T0 : 0x37363534 T1 : 0x7271706f T2 : 0x33323130 MHARTID : 0x00000000 Thinking that my C6 is defective, I flashed the "blink" example to both C6 and H2, and both worked flawlessly. |
So, could you please take a photo showing that how do you connect the C6 with H2? |
|
Thank you
|
|
could you please try to add this code after this line? (before calling the function |
|
I added the lines (Your marked line is at line #65 in my active code), and flashed both sides. abort() was called at PC 0x42006b1b on core 0 Stack dump detected TP : 0x407ea6e4 T0 : 0x37363534 T1 : 0x7271706f T2 : 0x33323130 Do you want me to find a shorter jump lines? |
Oh, too bad, it does not make sense... You can have a try with a shorter jump line. I compile the .bin file to you, and could you please try with this bin file building from my side? Let's try if the file built from my side can work or not. If it also did not work, it might be some HW issue related to your board.
|
|
Tips: if you see an error "no module named esptool", You can install it via command |
|
ok, now it is working! The message seems different from what you posted here: Is it ok? So I got a problem with my build process? |
Yes, could you please double check with these steps again? |
|
@zwx1995esp , I started a fresh installation on a different computer. I documented the steps I did so maybe you can find what am I doing wrong. I am using windows environment.
git status results:
Result: Success
Result: Failed I did not touch the HW in between the tests. |
|
I have an update. I installed a fresh Linux installation and repeated the steps in #56 (comment) . I compared the bin files I got from @zwx1995esp and the file sizes are different: For ot_rcp: For ot_br: So I definitely missing something in the complication since it happen in both Windows and Linux and on fresh installations of es-idf for both. |
|
An update: So now it is working. Thank you all. |
|
It is working now |
Building on ESP32-C6 fails for both esp-idf-v5.1.2 and esp-idf-v5.2-beta2.
For example, on esp-idf-v5.2-beta2, using ESP32-C6, I get the following error:
In file included from C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_br.c:17:
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_br.c: In function 'app_main':
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_config.h:54:36: error: 'CONFIG_PIN_TO_RCP_MOSI' undeclared (first use in this function); did you mean 'CONFIG_PIN_TO_RCP_BOOT'?
54 | .mosi_io_num = CONFIG_PIN_TO_RCP_MOSI,
| ^~~~~~~~~~~~~~~~~~~~~~
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_br.c:77:25: note: in expansion of macro 'ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG'
77 | .radio_config = ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG(),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_config.h:54:36: note: each undeclared identifier is reported only once for each function it appears in
54 | .mosi_io_num = CONFIG_PIN_TO_RCP_MOSI,
| ^~~~~~~~~~~~~~~~~~~~~~
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_br.c:77:25: note: in expansion of macro 'ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG'
77 | .radio_config = ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG(),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_config.h:55:36: error: 'CONFIG_PIN_TO_RCP_MISO' undeclared (first use in this function); did you mean 'CONFIG_PIN_TO_RCP_RX'?
55 | .miso_io_num = CONFIG_PIN_TO_RCP_MISO,
| ^~~~~~~~~~~~~~~~~~~~~~
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_br.c:77:25: note: in expansion of macro 'ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG'
77 | .radio_config = ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG(),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_config.h:56:36: error: 'CONFIG_PIN_TO_RCP_SCLK' undeclared (first use in this function); did you mean 'CONFIG_PIN_TO_RCP_RX'?
56 | .sclk_io_num = CONFIG_PIN_TO_RCP_SCLK,
| ^~~~~~~~~~~~~~~~~~~~~~
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_br.c:77:25: note: in expansion of macro 'ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG'
77 | .radio_config = ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG(),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_config.h:66:37: error: 'CONFIG_PIN_TO_RCP_CS' undeclared (first use in this function); did you mean 'CONFIG_PIN_TO_RCP_RX'?
66 | .spics_io_num = CONFIG_PIN_TO_RCP_CS,
| ^~~~~~~~~~~~~~~~~~~~
C:/Users/ORENC/Private/Thread/esp-thread-br/examples/basic_thread_border_router/main/esp_ot_br.c:77:25: note: in expansion of macro 'ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG'
77 | .radio_config = ESP_OPENTHREAD_DEFAULT_RADIO_CONFIG(),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the C:\Users\ORENC\Private\Thread\esp-thread-br\examples\basic_thread_border_router\build\log\idf_py_stderr_output_48496 and C:\Users\ORENC\Private\Thread\esp-thread-br\examples\basic_thread_border_router\build\log\idf_py_stdout_output_48496
The text was updated successfully, but these errors were encountered: