-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
host couldn't pass build (EHM-5) #5
Comments
I've found out that if I set ESP32 to be a host target, error will occur like pic upside, but when I choose ESP32-C3 as a host target, the processing will be a suc, but actually I'm using ESP32 as host and ESP32-C3 as slave now accoding to what I've been told bofore (#8) better using two defferent ESP chipsets each as a host and a slave, but I've found the the tutorial document have been changed much, is it still neccesary, what should I do with my two chipest? |
Hello @Speakpig, We are checking still why should it treat as sdmmc as 'cmake' interface. @SohKamYung-Espressif PTAL.. |
Assuming this build issue is only happening at host. As I understand, if you use classic ESP32, you experience build issue at the if(CONFIG_ESP_SDIO_HOST_INTERFACE) This issue not present for ESP32-C6. Can you please help me in providing:
|
1.SPI |
I just found that the error happened while I'm setting the target device, not in the building process, so I just can't get to the step to do some menucofig to choose SDIO or SPI. |
I didn't manually modify the file, I just added dependencies |
@Speakpig Have you disabled Native Wi-Fi on the ESP32 as documented in the troubleshooting page https://github.com/espressif/esp-hosted/blob/feature/esp_as_mcu_host/docs/troubleshooting.md#1-esp-host-to-evaluate-already-has-native-wi-fi :
|
@SohKamYung-Espressif Yeah, I' sure I missed that, the doc structure has been changed a lot since last time I read it, actually, I have been being concerned about this above, however, it's indeed my missing of guidance reading, I'm sry and I will try it out later, thx!
|
@Speakpig yes, the documentation is indeed changed. We tried to simplify and detail enough. Your feedback on this is valuable and welcome. |
If I understand correctly, the SPI FD test is best to start from 5MHz and gradually increase to the actual upper limit, so I need to change this parameter in pic from 30 to 5, right?
And I can't menuconfig the SPI clock in slave side, so it's no need 'cause it dependes on the host setting, right? |
check the 'IDF_PERFORMANCE_MAX_SPI_CLK_FREQ' mentioned in ESP-IDF SPI slave benchmark. For C3 as slave, max it can go upto 40MHz. Clock is released from host, but it cannot go more than 40. But if you use jumper cables as connection (and several other dependencies), it would saturate somewhere by ~30MHz. Manual KConfig change is discouraged. Finally, it would end here (to avoid again again again idf.py menuconfig) Once you sure what is max, you remove manual change and use
and set the freq under 'SPI Clock Freq' option. |
OK, when I'm building the host after my menuconfig done, it ouccur sth like this, why? Before I'm using the default setting which is |
Have you changed the sdkconfig or sdkconfig.h manually? Can you remove
and
and set values through the config GUI? |
Not related to build error, just as information, if you wish to change to spi, exact similar transport need to be setup at slave as well. |
This comment was marked as resolved.
This comment was marked as resolved.
iperf2 is only supported by default. |
OK,I will try iperf2, thx! |
Sorry I missed to understand, can you please assist in letting me know the host and slave ESP used? |
ESP32 as host, and ESP32-C3 as slave
|
I' using iperf3 on WINDOWS, shall I use iperf2? |
The IDF example integrates iperf2 minimal code. So, it needs other end running iperf2 only. Iperf3 may not work, irrespective of operating system used. |
If you test over he air, a lot of factors come in picture. Test first the pure transport speed. If you use PCB, C3 would cope up till 40MHz. Test raw transport throughput, before making wifi conclusions. |
How shall I set the data transfer direction, if I'will be using spi FD? |
Explained in link, Component config ---> ESP-Hosted config ---> Debug Settings ---> RawTP. Set the data transfer direction: Host to Slave, Slave to Host or Bidirectional You can test bidirectional |
The throughput could be achieved little high. But overall both sides are symmetrical, and the transport throughput is great. Can you please try to configure the AP to use 'auto' channel and try to reduce the interference? Alternatively, you can configure native (non hosted) wifi and compare the results. But from hosted perspective, I see this through. |
Sry, I don't quite get it, can u be more specific? |
1 & 2.
|
Yes, wifi throughput should really about match the transport. It would be 1-2mbps less than peak transport throughput in good wifi conditions. The transport test is packet transfer from one place to other. Also you have tested bi-directional transport test. Which would be little bit lower than single direction. So transport I expect to bump little more say about 19-20m in single direction. Nevertheless, try to test with another AP, different environment. In general, the test case (3) would give good amount of transparency for your test. |
Thanks a lot, that's very clear, I'm using the company's wifi mesh network, which is used by many employees, and the test results may be affected by the network environment. |
Any updates ahead @Speakpig ? |
Checklist
Issue or Suggestion Description
I'm using \esp-idf-v5.3\examples\wifi\iperf as a host example, it can pass build process untill I use cmds below
info as follows, much thx:
The text was updated successfully, but these errors were encountered: