Post B19bohCRLXOWTg654a by kline@mastodon.sdf.org
 (DIR) More posts by kline@mastodon.sdf.org
 (DIR) Post #B19R4e1znNH1mwc96u by lynn@raru.re
       2025-12-11T18:19:23Z
       
       0 likes, 2 repeats
       
       I bought this keyboard (XVX Jadestone M67) and the vendor published a binary file for use with QMK but they have been reluctant to send me any information about how it was compiled. I feel kinda ripped off but I should be able to figure out how to write firmware for it anyway.The best I could do was assume the DFU was wb32-based from qmk flash output, and also analyzing the binary shows the controller probably is ARMhf. That checks out so it could be any number of Westberry microcontrollers (I could find like 6 out of 7 listed online?). I did flash that binary file and the keyboard operation is apparently the same (any updates were for the wireless version and I have the wired one)Anyway, I'm wondering if anyone has general advice for RE-ing firmware, finding details on microcontrollers, or shooting in the dark trying to do QMK stuff. Thanks!
       
 (DIR) Post #B19bofsuEgAuOnwxzE by kline@mastodon.sdf.org
       2025-12-11T23:10:09Z
       
       0 likes, 0 repeats
       
       @lynn you might have already gone down this path, but if it's built on QMK, then it's built on GPL. As a user, they should be obligated to provide you the source code and also any build scripts required to compile it.Do you believe the firmware is based on QMK? If so, you should email their legal department to get a source code archive that corresponds to your product and version.
       
 (DIR) Post #B19bogZnfCUCXq1DqS by lynn@raru.re
       2025-12-11T23:14:13Z
       
       0 likes, 0 repeats
       
       @kline I think what happened is that they did comply when it was just the wired version, but then they "bundled" future binary releases to support the wireless version. now QMK's position is that it's reasonable to reject the PR without wireless sources
       
 (DIR) Post #B19bohCRLXOWTg654a by kline@mastodon.sdf.org
       2025-12-11T23:17:34Z
       
       0 likes, 0 repeats
       
       @lynn Maybe I misunderstand - I don't think the PR matters.If the hardware vendor sold you a product that uses QMK as a baseline, they are obligated to include the complete source code to users (ie, you).There is no obligation for them to upstream it to QMK-the-project, and it not being in upstream doesn't mean they do not need to provide it.If they have a firmware based on QMK and they have added specific features like wireless stuff, you're still covered, including the new feature code.
       
 (DIR) Post #B19bohxEXYpConzS0e by Nimbius666@comp.lain.la
       2025-12-11T23:21:01.143484Z
       
       0 likes, 0 repeats
       
       @kline @lynn reason I switched to banana pi.  RPI too proprietary