Skip to content

Instantly share code, notes, and snippets.

@instance-id
Last active November 21, 2023 16:43
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save instance-id/f52b8efbea082f08de06d08cfe7bb504 to your computer and use it in GitHub Desktop.
Save instance-id/f52b8efbea082f08de06d08cfe7bb504 to your computer and use it in GitHub Desktop.
Request for assistance applying new feature branch to Kinesis 360Advantage firmware.

I attempted to implement this myself, but I think I am missing a step somewhere. If anyone is be able to spot something I might have missed, please do let me know, as I am was familiar with ZMK prior to this attempt.

I use a Kinesis 360Advantage Pro, as such I am using firmware from them.

Steps taken:

  1. Forked the Kinesis repo: Original: https://github.com/KinesisCorporation/Adv360-Pro-ZMK My fork: https://github.com/instance-id/Adv360-Pro-ZMK
  2. Checked the west.yml file from the above repo to locate the base firmware and forked it: Original: https://github.com/ReFil/zmk My fork: https://github.com/instance-id/zmk
  3. Made the same modifications from PR: zmkfirmware/zmk#1318 in my forked repo under the appropriate branch: https://github.com/instance-id/zmk/commit/5b1a6afe5d19afa7ee9bc82e12316f8311060e54
  4. Updated the west.yml in my forked firware building repo to point to my forked firmware source repo and branch. https://github.com/instance-id/Adv360-Pro-ZMK/blob/V2.0/config/west.yml
  5. Made updates to my defconfig files to add the new CONFIG_SHELL and other variables to enabled the features: https://github.com/instance-id/Adv360-Pro-ZMK/commit/eb46aa12d86b4de0ebcc4578a6e42f4ed7973f66
  6. Build the firmware and checked the build steps under "Adv360 Left Kconfig file" and "Adv360 Right Kconfig file" to see that variables were set: Ex. https://img.instance.id/3ngKFWgXv0JX/direct
  7. Applied firmware to my keyboard.
  8. Installed the tools and libraries needed for USBIP as per: https://github.com/caksoylar/zmk-posix-testbed#testing-the-keyboard-through-usbip
  9. Ran sudo usbip list -r localhost , received following message:
zsh ✗  usbip list -r localhost
usbip: error: could not connect to localhost:3240: System error

Unfortunately, this is where I am now stuck. These steps I took were assumptions that this was the right way to go about this in the first place, so it is possible that I am off at any point in this process. If someone might be able to point me in the right direction, I would greatly appreciate it.

@petejohanson
Copy link

At least here, before using usbip I need to modprobe a few extra kernel modules:

sudo modprobe usbip-core
sudo modprobe vhci-hcd

Does that help?

@instance-id
Copy link
Author

Hey, sorry, didn't realize there was a reply. It's been some time since I was messing with this, but I was able to get some help from someone in one of the related PR's, and was able to get it working. Naturally, I never used it again after that, lol.

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