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
I recently purchased the Solo Hacker (USB C) and am facing issues while following the getting-started docs. I've tried looking into older issues with similar problems here in the repo, but none of the suggested solutions have helped me completely solve this.
So my question is which (additional) steps are necessary to recognize the device with the solo cli using wsl? (Or is there a way to make the firmware on ubuntu, copying over the binaries to windows and then deploying the code to the device from there as I'm able to run commands to the device there?)
I am working on a Windows machine, so I have WSL (version 2) installed with Ubuntu 22.04.2 LTS, where I am trying to generate and deploy new code to the device. I attach the usb device with usbipd wsl attach --busid <busid> and make sure with lsusb on ubuntu that it is recognized:
Bus 001 Device 004: ID 0483:a2ca STMicroelectronics Solo 4.1.5
However now, running the command solo1 key version or solo1 key update on ubuntu I get the message:
No Solo found.
If you are on Linux, are your udev rules up to date?
Running solo1 ls on ubuntu gives me the following:
:: Solos
Running the same command on Windows powershell with admin rights when the device is not attached to ubuntu:
:: Solos
204C3790324B: Solo 4.1.5
(I have updated the key's firmware on Windows in powershell with admin rights, so at least that step has worked, but now I'd like to successfully deploy the firmware from the docs to change the LED colors).
plugging the solo key in and attaching it to ubuntu, and then
running ls -1 /dev > ~/after.txt again and comparing the difference with diff ~/before.txt ~/after.txt but no diff is returned.
Edit:
Here's the output of dmesg (omitting the serial) so I feel like it's properly attached (?):
[ 5874.500496] usb 1-1: SetAddress Request (5) to port 0
[ 5874.544750] usb 1-1: New USB device found, idVendor=0483, idProduct=a2ca, bcdDevice= 1.00
[ 5874.548549] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5874.549357] usb 1-1: Product: Solo 4.1.5
[ 5874.549710] usb 1-1: Manufacturer: SoloKeys
The text was updated successfully, but these errors were encountered:
I recently purchased the Solo Hacker (USB C) and am facing issues while following the getting-started docs. I've tried looking into older issues with similar problems here in the repo, but none of the suggested solutions have helped me completely solve this.
So my question is which (additional) steps are necessary to recognize the device with the solo cli using wsl? (Or is there a way to make the firmware on ubuntu, copying over the binaries to windows and then deploying the code to the device from there as I'm able to run commands to the device there?)
I am working on a Windows machine, so I have WSL (version 2) installed with Ubuntu 22.04.2 LTS, where I am trying to generate and deploy new code to the device. I attach the usb device with
usbipd wsl attach --busid <busid>
and make sure withlsusb
on ubuntu that it is recognized:However now, running the command
solo1 key version
orsolo1 key update
on ubuntu I get the message:Running
solo1 ls
on ubuntu gives me the following:Running the same command on Windows powershell with admin rights when the device is not attached to ubuntu:
(I have updated the key's firmware on Windows in powershell with admin rights, so at least that step has worked, but now I'd like to successfully deploy the firmware from the docs to change the LED colors).
I set up the udev rules according to solokeys/solo1-cli#92 (comment) and tried finding the USB device's name by
ls -1 /dev > ~/before.txt
,ls -1 /dev > ~/after.txt
again and comparing the difference withdiff ~/before.txt ~/after.txt
but no diff is returned.Edit:
Here's the output of
dmesg
(omitting the serial) so I feel like it's properly attached (?):The text was updated successfully, but these errors were encountered: