Yes, I am opening this forum very special because all my cards are destroyed by a monster every few months, my 8 different cards are broken in total and I can't upload code to any of them anymore because the serial port does not open, I have no idea how such a thing happened.
Is the problem in voltage? No because it's not on voltage because I'm using a usb hub as a precaution when uploading code
Is the problem in the card?
The problem isn't with the card, because on the new cards I bought, it breaks the same day as the old card.
Is the problem on the computer I am using?
No, because when it starts to fail on the same day, it gives the same result even if I try the non-perishable card on another computer.
Is the problem in the cable?
No it's not because I have different cables for each card
Is the problem in the aging of the card?
No, because the 2 new cards I bought broke in one use.
What's the last thing that happens before it breaks down?
esp32 loads code just before it crashes, and then the serial port is closed, never to be opened again
Are there any exceptions to corruption?
Yes, I have a card, it was an esp model (esp32-wrover-e) that worked better and stronger than other cards, only it was not damaged, only its camera and wi-fi system were damaged.
sometimes they don't damage directly, they just damage some things. However, as I mentioned, all of my cards, some of which were damaged in the first step, were completely corrupted afterward, but most of the corrupted ones damage down without even undergoing a mild deterioration phase. I only have 1 card left in the mild degradation phase but most systems are not working.
10) How did the problem start?
The problem suddenly damage the wi-fi system and usb systems of the cards that were inserted in the first session, only on my own computer, but this problem did not exist on other computers and I thought it was voltage source and bought a usb hub, yes, no more cards were damagen until today. but today my card is damagen even though usb hub is plugged in. (my card damageright after I installed the code) and now I realized that the problem that I had solved temporarily after 3 months started again and I thought that I should switch to another computer and I inserted my new card into the computer that had never had a bad history before and another card damage. so the problem is not in the computer, I don't know what to do.
I used to do it that way before, when my cards started to fail 3 months ago, I started using a usb hub and connected the second computer I tried without using a usb hub.
I moved your topic to an appropriate forum category @abcda .
In the future, please take some time to pick the forum category that best suits the subject of your topic. There is an "About the _____ category" topic at the top of each category that explains its purpose.
I think the problem with 2 sessions may be from lidar, because in my 2nd session, the lidar was inserted while the cards were broken, and sometimes the code disconnects when there is an electronic circuit, but it is very likely that this is not the problem because there was no electronic circuit in the first session, I don't have a lot of cards to try, what I don't understand is why. they all break down on the same day at the same time.
I have more than one model in my hand, I will try on this model, my main affected model is esp32-s2, I thought the problem was the voltage at first because my computer was corrupting some external usbs that day and not only did it break it in the normal way, it also led to the error "usb device did not recognize" as a solution to this problem. I used an external usb hub and uploaded my codes beautifully for the next 3 months without any card breakdown, but YESTERDAY (the day before the cards broke down) I was curious about the usb hub and connected the usb hub to the computer without voltage, instead of giving it external voltage (the day before it broke down), maybe the usb hub broke down first and Since I used the cards in the usb hub that day, the cards there were already broken because when I tried the next day, none of the cards were working, but I never touched a card that day, the room was broken on another computer. The problem may not be external, because I tried it on 2 different computers, 2 different cards and 2 different cables. I don't have a lot of right to try too much, I only have 1 right to break a profit. (2 different laptop)
I understand that sometimes it can be difficult to choose, but please just use your best judgement.
This is a very active forum so we need the help of the users to keep it well organized. This will also be in your best interest because it will make it more likely that the helpers most knowledgeable on the subject matter will see your posts.
what is the probability of the usb hub damage really first? will connecting the usb hub directly to the computer without voltage to the usb hub damage the usb hub?
(not normal laptop, for laptop that damaged usbs)
1. At the back of my Board, the mark is: ESP32S. It is marked as ESP-WROOM-32 on the top of the RF Shield.
2. There are ESP32S2, ESP32S3, ESP32C3, and ESP32 Dev Module in the IDE. 3. Where is the ESP32S1 or ESP32S or ESP32 in the IDE? 4. Which one is the ESP32 -- is it the 30-pin version, the Standard one? I have not seen one marked as ESP32!
It is possible that the code that you are loading has a bug in it that is randomly triggered in some way. When it is triggered, it maybe possible that the side affect is to screw up the bootloader.
What is a bootloader? It is a small program on the ESP32 (and Arduino and so on) that can receive a new program from the USB and install it into the memory of the ESP32 (or Arduino etc).
If you do screw up the bootloader, then it won't work properly anymore and thus you might not be able to upload new code to your board.
Have a look at this article about ESP32 bootloaders.
What you have connected to the device is important and whether or not it needs some protection from interference .
Other problems such as there being a voltage on an input when the power supply is off or too heavy a load on an output pin can cause an issue .
If you post up a circuit diagram we can have a look .
