-
Notifications
You must be signed in to change notification settings - Fork 51
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
Problem with boot mode on T-Deck #5
Comments
I have the same issues. erase_flash works fine on T-HMI and on T-Display-S3 but the T-Desk either times out (non bootloader mode) or stalls (bootloader mode by pressing the trackball-button). I also tried it under Windows 11 and on MacOS. |
Try this method! https://github.com/Xinyuan-LilyGO/T-Deck/tree/master/firmware |
Unfortunately the linked instructions are the ones I've already followed and does not make bootloader mode work on the T-deck. I am still unable to flash when the T-Deck is in bootloader mode on any of my devices. |
Please take a photo of the PCB on ESP32S3 and show it to me. |
Hello, I tried all kinds of setting on the Windows Flasher, but I always see the same behaviour:
if in bootload-mode (COM4 or COM7): it waits some seconds and returns with a message box saying:
KInd regards |
Thanks! Removing D2 worked perfectly fine for me! Uploading new firmware is no longer a problem. Kind regards Bernd |
I just received two T-Decks with the D2 jumper. Should they be removed in all cases? Kindly explain before I have the same problem. |
Can confirm. i was having the same problem and removing D2 fixed it. |
Had the very same problem. |
Wow, talk about fast fix to the production line: I just received two T-Decks ordered 2 weeks ago and notice D2 is not installed on either. I don't see any version info on the PCB though, is there any way to tell the difference? |
Ok So I got a boot load problem and I did figure it out. The ESP32-S3 need to have GPIO0 and GPIO46 to 0 to go into the boot load mode but the ESP32-C3 int is connected to the GPIO46 and disturb the very high resistor pull down value. So shorting the GPIO46 and the same time that I press the GPIO0 button , then press the reset and release both GPIO0 and GPIO46 does the trick. This tooks me 2 evenings to figure out why the T DecK didn |
Name of God thank you for this answer I've been looking for a solution for 3 days |
THANK YOU THANK YOU, fixed my issue uploading code. removing D2. |
This issue is stale because it has been open for 30 days with no activity. |
I have 3 t-decks. Unfortunately one of them corrupted during a download, since then I have been unable to get it to take an new firmware.
I can (sometimes) get it to boot into the rom bootloader mode by holding down the trackball while resetting, however, once I try to use the esptool it finds the com port, but times out in writing.
I have tried this also on other computers with identical results. I've also tried putting my working T-decks into bootloader mode and while I can get them to bootloader mode the results are identical to my failed T-Deck.
The good ones will still take updated firmware while running normally, but the failed T-Deck will not, as it continually resets the USB connection.
With trace enabled in esptool I get the following:
I've tried forcing the chip with --chip esp32s3 (and esp32) as well as various baud rates. Everything I try fails with the write timeout.
Connection is successful and I get data from the chip when I do:
But any attempt to write or to erase the flash fails with a write timeout.
This is reproducable on all 3 of my T-Decks when in bootloader mode (and on multiple computers), but like I said, 2 of them can get flashed normally in the non-bootloader mode.
The text was updated successfully, but these errors were encountered: