-
-
Notifications
You must be signed in to change notification settings - Fork 691
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
STM32 died after flash read. #1882
Comments
@therealuzr If I got you right, you did not backup your bootloader right. |
yeah thx, that could help if i had it before, i believe. but now st link can't connect to the stm chip |
I recently had to deal with st-link and got the advice to bridge VSSA to NRST on the chip at boot in order to connect to it. |
thx, i'll try to figure that out and try tomorrow |
I happens to buy a ts100 with broken firmware, after connecting it to pc it wasn't able to install driver, like the data lines was broken (they're not). So after some research i bought a St-link v2, because i thought that the bootloader was corrupted or something. I read the chip, saved what it showed me. and then i needed to flash the bootloader for ts100, which i not found, instead i flashed a ts80 bootloader and now stm32 from my iron is not responding in software (st-link utility). okay. fast forward to this very moment. I have a new ts100, i opened it, get the stm chip out, connected it to st-link, read the flash, it showed me 00x0 or something like that, then i tried to disable read protection, it read something (not only 00x0) and i unpluged stm to assembly my iron back, and it wont turn on, i disassembled to check the stm with stlink again and it's now not responding just as the previous chip. I do not understand what exactly i did wrong, any advices would be helpful. That was my 1st and 2nd time ever work with stm. So, try to not blame me much. thx
The text was updated successfully, but these errors were encountered: