You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SPI auto-clock feature is potentially dangerous - bricked my 328p pro mini (clone, only HVPP revived the chip). "Detected" SPI speed is very aggressive - on the minimum allowed values that leads to instability during programming, even reading may fail (in my case - 16MHz CH552T, 16MHz 328p as a target - "detected" divider was turned out 3 - about 3 tclcl - minimum allowed, according to the datasheet). Original ArduinoISP cotains more liberal settings. As a workaround I've set SPI0_CK_SE += 3 to the divider at the end of the detection alg.
The text was updated successfully, but these errors were encountered:
dfxhub
changed the title
CH552: SPI auto-speed feature is potentially dangerous
CH552: SPI auto-clock feature is potentially dangerous
Oct 27, 2023
Hi, thank you for the hint and your solution to the problem. The problem doesn't occur to me, but to be on the safe side in the future, I have reduced the maximum speed so that it now complies with the data sheet.
picoISP Programmer - CH552E
SPI auto-clock feature is potentially dangerous - bricked my 328p pro mini (clone, only HVPP revived the chip). "Detected" SPI speed is very aggressive - on the minimum allowed values that leads to instability during programming, even reading may fail (in my case - 16MHz CH552T, 16MHz 328p as a target - "detected" divider was turned out 3 - about 3 tclcl - minimum allowed, according to the datasheet). Original ArduinoISP cotains more liberal settings. As a workaround I've set SPI0_CK_SE += 3 to the divider at the end of the detection alg.
The text was updated successfully, but these errors were encountered: