Skip to content
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

[Bug] Compiled firmware for yandrstudio/yr6095 do not work #20982

Open
2 tasks
daviddgm opened this issue May 18, 2023 · 6 comments
Open
2 tasks

[Bug] Compiled firmware for yandrstudio/yr6095 do not work #20982

daviddgm opened this issue May 18, 2023 · 6 comments

Comments

@daviddgm
Copy link

Describe the Bug

I tried to compile and update firmware for yandrstudio/yr6095 with bootloader stm32duino, uf2boot and tinyuf2, but none of them work in this board.

Keyboard Used

yandrstudio/yr6095

Link to product page (if applicable)

https://www.aliexpress.com/item/1005004689966255.html

Operating System

Linux

qmk doctor Output

No response

Is AutoHotKey / Karabiner installed

  • AutoHotKey (Windows)
  • Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

For every firmware that do not work need to program bootloader again.

@sigprof
Copy link
Contributor

sigprof commented May 18, 2023

The fact that the bootloader declared for yandrstudio/yr6095 does not match what is installed on real PCBs is known for some time: #18278 (comment). Some other Y&R boards using STM32F103 MCUs (or clones) are probably also affected with the same problem.

Unfortunately, it seems that the maintainer of those boards is not really interested in getting them properly supported in upstream QMK (they apparently have their own fork with some core modifications related to their customized bootloader), and I don't actually have that PCB, so I'm not 100% sure what should be the proper bootloader setup for that hardware.

@daviddgm
Copy link
Author

Hi. Please one basic question, I need to use .hex or .uf2 file to update the board?

@sigprof
Copy link
Contributor

sigprof commented May 18, 2023

That depends on which bootloader you actually have on your PCB:

  • If you have some version of the uf2boot bootloader (that appears as an USB drive to the computer), you need the .uf2 file.
  • If you have the stm32duino bootloader, you need flash a .bin file using dfu-util (QMK Toolbox may be able to do that, because it has support for that bootloader).
  • A .hex file is not used by any common bootloaders for F103.

Note that you can't simply convert a .bin file which was compiled for the stm32duino bootloader to the .uf2 format, because the firmware intended for use with the uf2boot bootloader needs to be compiled for a different base address.

@bartman
Copy link

bartman commented Jun 30, 2024

I need to reflash the bootloader onto my yr6095. I have found the Flashing STM32Duino Bootloader. Unfortunately the pads on the board are not labeled.

Anyone figure out which pin is which?

Also there are no jumpers on the yr6095, is that going to be a problem?

@fauxpark
Copy link
Member

fauxpark commented Jun 30, 2024

Per the datasheet the third pin from the left appears to be connected to PA13 (SWDIO). From this we can reasonably infer the second pin is PA14 (SWCLK). Then the first pin with the thicker traces is probably VCC, and the remaining pin GND. Double check this with a multimeter first though.

@bartman
Copy link

bartman commented Jun 30, 2024

Thanks. Found the data sheet here: STM32F103

with multimeter I see, from left to right:

  • ~0V -- guessing GND
  • ~0V -- guessing SWCLK
  • ~3.3V -- guessing SWDIO
  • ~3.3V -- guessing VCC

Here is my current guess https://imgur.com/BESNPOm

ST-Link ordered... will update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants