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
During the FF OSD porting to MSX the Blinker test (blinky-test-f1-1.2.hex) had no output from Blue pill via serial interface. Then @keirf informed me that:
No blinking led is bad. No serial is weird. I may have broken the build slightly and it's not currently at 115200 baud. Actually I think that's likely. Try 3000000 baud (three million).
Would it be possible to release the fixed Blinky test with proper baud rating please? Thanks. This test is essential to identify the Blue Pill boards that could work with Goteks.
The text was updated successfully, but these errors were encountered:
Wierzbowsky
changed the title
Blinker test with proper baud rating needed (currently 3000000)
Blinky test with proper baud rating needed (currently 3000000)
Oct 14, 2022
A correct blinky will be included in older greaseweazle releases. Try downloading, say, v0.20 of greaseweazle host tools (firmware and host tools used to be in the same download file). If that works you could link to that older release in the docs you are writing.
I will update blinky in latest greaseweazle firmware when I next make a release. But that's not happening immediately for firmware.
I could update the wiki to point at v0.20 release temporarily for blinky serial though?
During the FF OSD porting to MSX the Blinker test (blinky-test-f1-1.2.hex) had no output from Blue pill via serial interface. Then @keirf informed me that:
No blinking led is bad. No serial is weird. I may have broken the build slightly and it's not currently at 115200 baud. Actually I think that's likely. Try 3000000 baud (three million).
Would it be possible to release the fixed Blinky test with proper baud rating please? Thanks. This test is essential to identify the Blue Pill boards that could work with Goteks.
Originally posted by @keirf in #48 (comment)
The text was updated successfully, but these errors were encountered: