Closed Tropaion closed 1 year ago
xieqinan
commented
1 year ago @Tropaion， I checked the output log, and it appears that your C6 module sample is at an early stage and has not yet had the eFuse burnt.
A potential workaround for this issue is to switch your ESP-IDF commit to 38b4952 at a later stage. However, please note that this workaround is intended for testing purposes only and is not recommended for use in production environments where eFuse versions are crucial.
Tropaion
commented
1 year ago @xieqinan Thanks for your help, that really sucks. The seller I bought it from didn't say anything about that. I bought 10 pieces of the module for a prototype, is there a way to physically identify if the eFuse is burnt or not? Out of interest, why is the eFuse not burnt? And what does the Fuse indicate? I persume burning it myself is not possible.
And how do I change the commit of the ESP-IDF?
chshu
commented
1 year ago @Tropaion If you bought the modules from official store, the eFuse should be flashed already. Could you run this command and share with us the output:
espefuse.py summaryTo checkout specific IDF commit, you can use this command:
git checkout 38b4952
git submodule update --init --recursive@chshu If bought the module from Adafruit, they were the only ones who had them in stock: https://www.adafruit.com/product/5671
espefuse.py summary
I will send you the result tomorrow, I'm at home office today.
To checkout specific IDF commit, you can use this command:
git checkout 38b4952 git submodule update --init --recursive
I don't know if this is possible, I didn't download it via git. I installed my environment with the VS Code and espressif plugin. And if I use this workaround, is it still possible to use the latest zigbee-sdk?
EDIT: If the reason is the eFuse, why did the chip work when I tried a simple example, driving a blinking led?
Tropaion
commented
1 year ago @chshu I tried running espefuse.py summary but nothing happens.
I guess it has something to do with the boot mode.
In which mode does the module have to be?
My esp is only connected with RX, TX and GND. I set it to download mode manually.
ESP-ROM:esp32c6-20220919
Build:Sep 19 2022
rst:0x1 (POWERON),boot:0x4 (DOWNLOAD(USB/UART0/SDIO_FEI_FEO))
waiting for downloadEDIT: I think I found and interesting bug in the esptool. I have installed the master branch. When I use the esptool, no matter which command, the python script runs infinitely and spawns processes until my RAM is full and my pc crashes. I can't even stop the script with the task manager, since it is conitinously spawning. But I have no idea why.
Tropaion
commented
1 year ago @chshu After dowloading the latest version from https://github.com/espressif/esptool I got it to work, here the result: efuses.txt
EDIT: I tried a second module I got now too, same error: efuses2.txt
xieqinan
commented
1 year ago Hi @Tropaion , Thank you for providing the log. The problem has been resolved and will be published this week.
If you need to stay on a specific commit, please add the patch to your branch. efuse_patch.zip
Tropaion
commented
1 year ago @xieqinan Thanks, what exactly was the problem? Will my modules work again when I update my installation next week? I don't need a specific commit, I normally use the latest version.
xieqinan
commented
1 year ago The reason for the chip may not being burnt with the ADC calibration block. We have already fixed the issue and will sync it within this week. You can use the provided patch to solve your problem temporarily.
xieqinan
commented
1 year ago The issue has been fixed in the latest esp-idf.
Please test whether the fix is helpful to you and close the issue.
Tropaion
commented
1 year ago @xieqinan Sorry, was on holidays. I tested it now with the master branch and it's working, thank you.
Hello, I developed an application on the Dev.-Board, which is working without any problems. Now, I developed a small custom board with the recommended layout for the ESP32-C6-WROOM-1. After flashing the application via UART0 I get following error, which doesn't make any sense to me, because I'm not even using the eFuse.
I tried a simple example on my custom boards, blinking a led and sending logs, which works without problem. Any idea why this happens? Thanks, Tropaion