-
Notifications
You must be signed in to change notification settings - Fork 37
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
[ISSUE] ST-link claims Read Out Protection is enabled #1
Comments
@shuffleznl Are you using the ORIGINAL or OFFICAL ST-LINK-V2 device or a clone device? Which BIGTREETECH board are you trying to talk to? |
@shuffleznl Try to recover the chip by using the system bootloader: Force boot0 pin to be 1 and force boot1 pin to be 0 at power up, start bootloader then connect USB and program the chip with DFU programmer. You can download the DFU programmer https://www.st.com/en/development-tools/stsw-stm32080.html# Another link to help with this issue: https://community.st.com/s/question/0D50X00009XkZDo/how-disable-read-out-protection- |
i'm in same situation with my GTR bigtreetech 1.0 :-( |
on linux i had this error : st-info --probe st-flash --version st-flash --reset --format=ihex write GTR-V1.0-bootloader-only.hex st-flash --reset write GTR-V1.0-bootloader-only.bin 0x08000000 can you help me please ? i used a stlink V2 clone |
Instead of loading only the bootloader file, try flashing the "Bootloader+firmware" file. This file contains the Micro-SD card bootloader and the original firmware that was delivered when you got the GTR board fresh from the factory. Also check to see if the micro-SD card reader is even working. I have seen other users say that the micro-SD card reader has bent pins. Use a flashlight and check to see what the micro-SD card reader's input slot looks like. Are all the pins flat in the slot? On Linux, you could use the STM32programming Utility. They make a version that will run under Mint Linux. I use that one when I am on my Linux laptop. The last time I used st-link from GitHub (if I am remembering correctly) I had trouble with flashing the MCU boards. If you must use st-link from GitHub then check out their current issue and closed issues (https://github.com/stlink-org/stlink/issues). Someone else might have experienced this issue and might have solved it. You might have to rollback to a different version of st-link (https://github.com/stlink-org/stlink/releases) I know you are using a V2-clone on Linux but I highly recommend you buy and official ST-LINK-V2. STMelectronics has some proprietary stuff in that device that the clones do not have. If you own BTT boards, it is worth the investment to buy a genuine ST-LINK-V2. They are around $55 (https://www.amazon.com/Microcontrollers-circuit-debugger-programmer-emulator/dp/B00C7WDTLG). You have to think of buying an ST-LINK-V2 original as if you need a specialized set of Wera Allen keys. For example Wera TORX Allen Keys cost around $55 on amazon (https://www.amazon.com/Wera-05024480001-Multicolor-L-Key-TORX/dp/B07B7XWJZ6). |
Apologies for abandoning the thread, I moved to SKR board (until it fried), on different (non-BTT) HW now. Can confirm; Wera and original ST-Link are both worth it. |
Bug Description
First of all thanks for your great work, doing what Biqu/BTT failed to!
Makes me very humbled to see the work individuals put in to support others.
I'm not sure if to post here, as it's not a bug with any of your doing at all :)
Issue appeared after restarting the board (it was printing before, so FW/SW was running well).
Rebooting the board didn't start nor did it read from SD (tried several FW's).
Upon connection of ST-link (swapped SWCLK & SWDIO to be sure) it reads Device, DeviceID, RevisionID, but Flash Size is reported 'Unknown'. Also a warning is thrown; 'Can not read memory! Disable Read Out Protection and retry.'
Cannot reset Option Bytes Read Out Protection from 1 to 0.
Full Chip Erase is also 'protected' because of 'Read Out protection is activated' warning.
Additional Information
EDIT: Updated the ST-link FW and checked latest version of ST-Link.
The text was updated successfully, but these errors were encountered: