-
Notifications
You must be signed in to change notification settings - Fork 117
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
Creating a standalone Zephyr example (ESF-193) #127
Comments
Hello @beriberikix , it does indeed seem that we are not handling Additionally, you can try debugging the host in order to find the point where the timeout happens and report that as well. |
Hi @beriberikix, thanks for using this library and sorry it takes so long to fix the debug tracing. I already tested the fix and it works, but I need to fix some non-related issues first. Please can you add the following lines into
|
No worries, thank you! In addition to the CMake edit, I also need to add I now see more output from the host (nRF52) from the terminal but it doesn't seem to be all that helpful.
|
Can you please review that the pinout is correct? I just noticed that RX and TX pins are swapped in the README for Zephyr example which might have confused you. The example works for me after that. Also beware that the target (ESP32) should not be connected to a PC through USB during flashing as USB-UART converter might interrupt the transfer, just power the target through pins. I see you tried to read the log from the target as you attached it (the flashing should not work like this, as I said). From the |
I tried powering the ESP32C6 direct while programming and got the same result.
I also confirmed the hookup diagrams are as a described above and defined in my overlay. |
I tried your code from the standalone application with esp32 as a host and esp32 (and esp32c6) as a target and it works for me, so it seems like some issue with the nRF chip, overlay or a hardware issue. Also please be aware that GPIO0 is not the boot pin on esp32c6, it is GPIO9. Just making sure once again, USB connector of the target should be disconnected. |
Appreciate the testing! I've confirmed that hardware isn't likely issue on both sides, so it's possible it's the overlay. Can you share the overlay you used for the host ESP32? |
It can be found here. |
One thing I noticed, the pins you selected for UART are marked as low frequency I/O only which should be used below 10 KHz as stated here, you can try to change the pins. |
Port
Zephyr
Target chip
ESP32
Hardware Configuration
Currently testing with the host as a nRF52840 DK and an ESP32.
I've tested with a ESP32-DevKitC but also tested with a ESP32-C6-DevKitC to see if my results are different (they're not.)
Log output
I don't think SERIAL_FLASHER_DEBUG_TRACE is working on the Zephyr port or I'm doing something wrong. I enabled it with
menuconfig
and didn't see a change in output.After
west flash
on the nRF DK, I see:On the ESP32 or ESPC6:
More Information
I created a standalone application that's essentially the example, with a
west.yml
and modified CMake paths. It's likely I made errors when copy files around but couldn't find anything obvious. As you can see from the output, the device does go into programming mode. I tried increasing timeouts but it didn't have any effect.The text was updated successfully, but these errors were encountered: