-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add flash instructions for genuine ST-Link/V2 Flasher #89
Comments
This may or may not be relevant to this issue. I have had several DFM-17 fail to program when powered by used batteries and the same error occurred. Replacing batteries to get better voltage may also fix the error. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran into some issues today trying to flash a RS41 with a genuine ST-Link/V2 programmer instead of the 3rd-party clones I have used before. When trying to flash using openOCD i got the following errors:
I found conflicting information online, about whether or not to connect the voltage supply pin (MCU switch 3.3V/Pin5) to the programmer, so I chose not to connect it. After connecting this pin I had no further issues.
As far as I understand (please correct me if I'm wrong) the corresponding pin on the ST-Links 20-pin header (MCU_VDD/Pin1 and Pin2) does not power the Radiosonde (so batteries or another power supply is still needed for flashing) but is needed to "ensure signal compatibility between the boards" (see User Manual Page 12). I don't know if this was obvious to other people, but it took me some time to figure out.
Maybe consider adding this info to the README (for example like below)?
Also might be a good idea to try to reproduce this issue, as I don't know if my programmer is behaving nominally.
Best regards.
Connect the RS41 radiosonde to the programmer
With 3rd Party ST-LINK Dongle:
remove the batteries from the sonde. Otherwise, leave the batteries in and power on the sonde.
With genuine ST-LINK Dongle:
The text was updated successfully, but these errors were encountered: