Serial connection issue with DIY

[andrea-dandrea]

Good afternoon,

so I tried the DIY Jade wallet on a M5StickC Plus.
I built version 1.0.23 on esp-idf version 5.1.1 and flashed the stick.
It apparently connects and works via bluetooth, but has issues via usb and doesn't even connect.
The Jade wallet reacts when I plug it on the PC (both usb logo and battery power up), but the PC doesn't recognize it any more as a serial device, the phone also not.
I built version 1.0.24 but I cannot flash if because the serial port doesn't connect/work.
I checked the logs of when I flashed the stick first and it looks that right after starting up the pc loses the serial port.
At the moment I am not able to bring the stick back to factory status and start all over again, even the M5Burner app cannot connect or erase the device.
I guess the factory reset in Jade menu just resets the wallet and not the stick itself.
Any suggestion will be appreciated.

Andrea

EDIT: after some forum reading, it seems that the serial port of M5StickC Plus can have issues, and others reported them; after some testing I discovered that the PC doesn't connect when I use a usb3 port, but does connect on a usb2, even if unreliabily; with that I have been able to wipe the device and flash the newer bin file.
With the new version 1.0.24 I've been able to connect and activate the wallet by usb on Sparrow, but not on Green, neither on PC nor on Android. I'm not sure if this difficulty in connecting my stick to Green is due to my less than ideal usb connection or not.

[nate922]

Hi Andrea.

I believe this issue is due to the USB device ID of the M5StickC.

M5StickC uses VendorID:0403 ProductID:6001 which is different to retail jade.
Sparrow uses HWI which recently has this device ID added.

You can recompile green with this device ID and it should work.

[robertclarkson]

Firmware verion 1.0.27-11-gca6ea18
I'm having a similar issue with the device not being found in Green wallet using USB with the Wrover Cam ESP32. The device shows up as

Bus 001 Device 009: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

[JamieDriver]

When connecting via USB the app has to scan looking for a (potential) Jade device.
It is possible that the app in question does not have the vid/pid of your device.
The list we have (in our internal ci tests) is:

    # Used when searching for devices that might be a Jade/compatible hw
    JADE_DEVICE_IDS = [(0x10c4, 0xea60), (0x1a86, 0x55d4), (0x0403, 0x6001), (0x1a86, 0x7523)]

[mauriciorlima]

Ao conectar via USB, o aplicativo tem que escanear procurando por um dispositivo Jade (potencial). É possível que o aplicativo em questão não tenha o vid/pid do seu dispositivo. A lista que temos (em nossos testes internos de ci) é:

    # Used when searching for devices that might be a Jade/compatible hw
    JADE_DEVICE_IDS = [(0x10c4, 0xea60), (0x1a86, 0x55d4), (0x0403, 0x6001), (0x1a86, 0x7523)]

Has this error been corrected yet?

[JamieDriver]

Jade's own list of devices to scan for is:

    JADE_DEVICE_IDS = [
            (0x10c4, 0xea60), (0x1a86, 0x55d4), (0x0403, 0x6001),
            (0x1a86, 0x7523), (0x303a, 0x4001), (0x303a, 0x1001)]

I believe these are (were) updated to include diy devices when support for that device is added.

If some other wallet software, eg Sparrow, is not using that full list, it indeed won't see some devices - but there is nothing we can directly do from here. If anything, you'd need to raise an issue with the wallet in question.

After the upcoming 1.0.31 release, when further devices should be supported (eg. M5StickCPlus2 🤞 ) I will raise issues against these other projects to update their lists to the master list as in our repo.

[JamieDriver]

I have recently made a PR to HWI which should address this issue - ofc we have to wait for HWI to take them, release, and then Sparrow to upgrade HWI ...
See bitcoin-core/HWI#753