Karolis Stasaitis

This issue isin't related to the nic template. I believe that since this issue is so old and you already fixed the problem, it should be closed.

I had a similar issue occur recently. It turned out that I was using a different version of deploy-rs on the machine I was deploying from and the version of...

@nox-x ah, thank you so much, I'll take a stab at this in the following days.

Hey, all the mentioned problems are also "fixed" (mitigated) in the main branch now. I experienced the same behavior you saw and it seems to be related to the rate...

@zuozhehao Analyzing and documenting the protocol that the mcu uses to talk to the wireless IC would be tremendously helpful. I haven't found any datasheets or other resources for the...

@namidairo thanks! On a related note, I was just exploring these parts of the stock firmware and found that the SPI comms with the BK3632 are all bit-banged :/

I sniffed the spi lines during the initialization and a couple of keypresses (`0x37`), here's the result: [bk3632-rf-bootup-key-press.csv](https://github.com/user-attachments/files/16199294/bk3632-rf-bootup-key-press.csv). Command `0x1d 0x02` looks like the keyboard report. It seems similar to...

I dug a bit more into `1d 02`, the format seems to be: ``` aa 1d 02 {5} {16} 00{5} ``` The NKRO bits seem to include only keys that...

Oh, and I just figured out that the second byte in these command frames is actually `length_of_the_frame - 3`, example: `32 - 3 = 0x1d`. This applies to all commands....

I'll try to add documentation with more details on how to build the firmware in the future, but for now, it's provided as is. As a starting place, you can...