Failed to find USB device with matching vendor & product ID

[pr2zi]

Hi,
I was trying to connect Bloom to my AVR128DB48. I initialised the yaml file and configured it properly as adviced. The command lsusb leaves me with this entry: Bus 001 Device 008: ID 03eb:2175 Atmel Corp. nEDBG CMSIS-DAP

2023-01-09 12:53:14 CET [MT] [1]: [INFO] Selected environment: "default"
2023-01-09 12:53:14 CET [TC] [2]: [INFO] Starting TargetController
2023-01-09 12:53:14 CET [TC] [3]: [INFO] Connecting to debug tool
2023-01-09 12:53:14 CET [TC] [4]: [ERROR] The TargetController encountered a fatal error. See below for errors:
2023-01-09 12:53:14 CET [TC] [5]: [ERROR] Failed to find USB device with matching vendor & product ID.
2023-01-09 12:53:14 CET [TC] [6]: [INFO] Shutting down TargetController
2023-01-09 12:53:14 CET [MT] [7]: [ERROR] TargetController failed to start up
2023-01-09 12:53:14 CET [MT] [8]: [INFO] Shutting down Bloom
2023-01-09 12:53:14 CET [SH] [9]: [INFO] Shutting down SignalHandler

Did I miss something to make it run?

[navnavnav]

Hi @pr2zi,

That vendor and product ID belongs to the Curiosity Nano evaluation board. Have you selected the curiosity-nano debug tool in your bloom.yaml?

Can you please post the contents of your bloom.yaml here? It should look something like this:

environments:
  default:
    debugTool:
      name: "curiosity-nano"

    target:
      name: "avr128db48"
      physicalInterface: "updi"

    debugServer:
      name: "avr-gdb-rsp"
      ipAddress: "127.0.0.1"
      port: 1442

insight:
  enabled: true

If you're confident that your bloom.yaml is correct, then please enable debug logging and post the full debug log. To enable debug logging, set debugLoggingEnabled to true in bloom.yaml:

debugLoggingEnabled: true

environments:
  ...

Thanks!

[pr2zi]

Hi @navnavnav,
Thank you for your quick response. I missed name: "curiosity-nano" and added this which lead to this new error:

2023-01-09 14:42:02 CET [MT] [1]: [DEBUG] Debug log printing has been enabled
2023-01-09 14:42:02 CET [MT] [2]: [DEBUG] Bloom version: 0.11.1
2023-01-09 14:42:02 CET [MT] [3]: [INFO] Selected environment: "default"
2023-01-09 14:42:02 CET [MT] [4]: [DEBUG] Number of environments extracted from config: 1
2023-01-09 14:42:02 CET [SH] [5]: [DEBUG] Starting SignalHandler
2023-01-09 14:42:02 CET [SH] [6]: [DEBUG] SignalHandler ready
2023-01-09 14:42:02 CET [TC] [7]: [INFO] Starting TargetController
2023-01-09 14:42:02 CET [TC] [8]: [INFO] Connecting to debug tool
2023-01-09 14:42:02 CET [TC] [9]: [ERROR] The TargetController encountered a fatal error. See below for errors:
2023-01-09 14:42:02 CET [TC] [10]: [ERROR] Failed to open USB device - error code -3 returned.
2023-01-09 14:42:02 CET [TC] [11]: [INFO] Shutting down TargetController
2023-01-09 14:42:02 CET [TC] [12]: [DEBUG] Event "TargetControllerThreadStateChanged" (1) registered for listener ApplicationEventListener
2023-01-09 14:42:02 CET [MT] [13]: [ERROR] TargetController failed to start up
2023-01-09 14:42:02 CET [MT] [14]: [INFO] Shutting down Bloom
2023-01-09 14:42:02 CET [MT] [15]: [DEBUG] Joining TargetController thread
2023-01-09 14:42:02 CET [MT] [16]: [DEBUG] TargetController thread joined
2023-01-09 14:42:02 CET [MT] [17]: [DEBUG] Joining SignalHandler thread
2023-01-09 14:42:02 CET [SH] [18]: [DEBUG] SIGNAL 10 received
2023-01-09 14:42:02 CET [SH] [19]: [INFO] Shutting down SignalHandler
2023-01-09 14:42:02 CET [MT] [20]: [DEBUG] SignalHandler thread joined
2023-01-09 14:42:02 CET [MT] [21]: [DEBUG] Saving project settings to /mnt/c/GIT/avr128_curiosity_nano_board/.bloom/settings.json

[navnavnav]

Hmm, that looks like a permissions issue.

How did you install Bloom? Did you use one of the binary packages hosted on https://bloom.oscillate.io/download? Or did you build from source? If you built from source, did you manually copy over the Udev rules to /etc/udev/rules.d/? Have you disconnected and reconnected the Curiosity Nano board since you installed Bloom? Udev rules are applied on device connection, so if the device was already connected when you updated the rules, those changes will only apply once you disconnect and reconnect.

Could you try running Bloom as root? If that works, then it's likely an issue with udev rules. Let me know and we'll take it from there.

[pr2zi]

I installed bloom with the deb from your download page. Could me using WSL Ubuntu cause the problem?
I ran bloom as root and got a bit further this time:

2023-01-10 09:03:22 CET [MT] [1]: [DEBUG] Debug log printing has been enabled
2023-01-10 09:03:22 CET [MT] [2]: [DEBUG] Bloom version: 0.11.1
2023-01-10 09:03:22 CET [MT] [3]: [INFO] Selected environment: "default"
2023-01-10 09:03:22 CET [MT] [4]: [DEBUG] Number of environments extracted from config: 1
2023-01-10 09:03:22 CET [SH] [5]: [DEBUG] Starting SignalHandler
2023-01-10 09:03:22 CET [TC] [6]: [INFO] Starting TargetController
2023-01-10 09:03:22 CET [SH] [7]: [DEBUG] SignalHandler ready
2023-01-10 09:03:22 CET [TC] [8]: [INFO] Connecting to debug tool
2023-01-10 09:03:22 CET [TC] [9]: [DEBUG] HID device path: 0001:0002:00
2023-01-10 09:03:22 CET [TC] [10]: [INFO] Debug tool connected
2023-01-10 09:03:22 CET [TC] [11]: [INFO] Debug tool name: Curiosity Nano
2023-01-10 09:03:23 CET [TC] [12]: [INFO] Debug tool serial: MCHP3372031800001314
2023-01-10 09:03:23 CET [TC] [13]: [DEBUG] Loading AVR8 target description file: /opt/bloom/bin/../resources/TargetDescriptionFiles/AVR/AVR8/DB/AVR128DB48.xml
2023-01-10 09:03:23 CET [TC] [14]: [DEBUG] Failed to extract memory segment from target description element - Unknown type: "other"
2023-01-10 09:03:23 CET [TC] [15]: [DEBUG] Failed to extract memory segment from target description element - Unknown type: "user_signatures"
2023-01-10 09:03:23 CET [TC] [16]: [DEBUG] Failed to extract bit field from register target description element - Failed to convert bit field mask to integer (from hex string)
2023-01-10 09:03:23 CET [TC] [17]: [INFO] Activating target
2023-01-10 09:03:23 CET [TC] [18]: [DEBUG] Setting DEVICE_UPDI_PROGMEM_BASE_ADDR AVR8 parameter
2023-01-10 09:03:23 CET [TC] [19]: [DEBUG] Setting DEVICE_UPDI_PROGMEM_BASE_ADDR_MSB AVR8 parameter
2023-01-10 09:03:23 CET [TC] [20]: [DEBUG] Setting DEVICE_UPDI_FLASH_PAGE_SIZE AVR8 parameter
2023-01-10 09:03:23 CET [TC] [21]: [DEBUG] Setting DEVICE_UPDI_FLASH_PAGE_SIZE_MSB AVR8 parameter
2023-01-10 09:03:23 CET [TC] [22]: [DEBUG] Setting DEVICE_UPDI_EEPROM_PAGE_SIZE AVR8 parameter
2023-01-10 09:03:23 CET [TC] [23]: [DEBUG] Setting DEVICE_UPDI_NVMCTRL_ADDR AVR8 parameter
2023-01-10 09:03:23 CET [TC] [24]: [DEBUG] Setting DEVICE_UPDI_OCD_ADDR AVR8 parameter
2023-01-10 09:03:23 CET [TC] [25]: [DEBUG] Setting DEVICE_UPDI_FLASH_SIZE AVR8 parameter
2023-01-10 09:03:23 CET [TC] [26]: [DEBUG] Setting DEVICE_UPDI_EEPROM_SIZE AVR8 parameter
2023-01-10 09:03:23 CET [TC] [27]: [DEBUG] Setting DEVICE_UPDI_EEPROM_BASE_ADDR AVR8 parameter
2023-01-10 09:03:23 CET [TC] [28]: [DEBUG] Setting DEVICE_UPDI_SIG_BASE_ADDR AVR8 parameter
2023-01-10 09:03:23 CET [TC] [29]: [DEBUG] Setting DEVICE_UPDI_FUSE_BASE_ADDR AVR8 parameter
2023-01-10 09:03:23 CET [TC] [30]: [DEBUG] Setting DEVICE_UPDI_FUSE_SIZE AVR8 parameter
2023-01-10 09:03:23 CET [TC] [31]: [DEBUG] Setting DEVICE_UPDI_LOCK_BASE_ADDR AVR8 parameter
2023-01-10 09:03:24 CET [TC] [32]: [DEBUG] Failed to activate physical interface on AVR8 target - retrying with external reset applied.
2023-01-10 09:03:24 CET [TC] [33]: [ERROR] The TargetController encountered a fatal error. See below for errors:
2023-01-10 09:03:24 CET [TC] [34]: [ERROR] AVR8 Activate physical interface command failed - Failure reason: Illegal value given
2023-01-10 09:03:24 CET [TC] [35]: [INFO] Shutting down TargetController
2023-01-10 09:03:24 CET [TC] [36]: [INFO] Deactivating target
2023-01-10 09:03:24 CET [TC] [37]: [INFO] Closing debug tool
2023-01-10 09:03:24 CET [TC] [38]: [DEBUG] Event "TargetControllerThreadStateChanged" (1) registered for listener ApplicationEventListener
2023-01-10 09:03:24 CET [MT] [39]: [ERROR] TargetController failed to start up
2023-01-10 09:03:24 CET [MT] [40]: [INFO] Shutting down Bloom
2023-01-10 09:03:24 CET [MT] [41]: [DEBUG] Joining TargetController thread
2023-01-10 09:03:24 CET [MT] [42]: [DEBUG] TargetController thread joined
2023-01-10 09:03:24 CET [MT] [43]: [DEBUG] Joining SignalHandler thread
2023-01-10 09:03:24 CET [SH] [44]: [DEBUG] SIGNAL 10 received
2023-01-10 09:03:24 CET [SH] [45]: [INFO] Shutting down SignalHandler
2023-01-10 09:03:24 CET [MT] [46]: [DEBUG] SignalHandler thread joined
2023-01-10 09:03:24 CET [MT] [47]: [DEBUG] Saving project settings to /mnt/c/GIT/avr128_curiosity_nano_board/.bloom/settings.json

[navnavnav]

Hi @pr2zi,

I've just tested Bloom with the same Curiosity Nano evaluation board (EV35L43A), and it works fine. I've not been able to reproduce the error you're seeing there. I've also tried it on a number of Linux VMs, again without issue.

I suspect the issue lies with USB device I/O, from within WSL. But given that I know very little about WSL and Windows, I'm afraid I cannot be of much help.

If you don't mind me asking, why are you trying to run Bloom on Windows? Doesn't Microchip Studio provide a GDB server of its own (atbackend.exe)? I can't find much info on this, but I'm sure I've seen others reference it on AVRFREAKS.

If you insist on using Bloom on Windows, I recommend using a VirtualBox VM. I use this for testing Bloom on a number of Linux distros. If you do go down this path, be sure to install the VB Guest Additions for the VM, and select the USB 3.0 xHCI controller.

[pr2zi]

Hi @navnavnav ,

I wanted to debug my AVR128 in Clion. Using windows there is as far as i know only one way to debug AVR (with Microchip Studio). Since im mainly working with Clion constandly importing and exporting projects from Clion to Microchip and vice versa is quite annoying and consumes too much time.
Thats why I wanted to try Bloom although im on Windows. I installed VirtualBox today and hope to get it running.

[navnavnav]

Hey @pr2zi,

Ok, you should be able to use Bloom in a Virtual Box VM, on Windows. You could also setup port forwarding, so that you can run the GDB client (CLion) on the host machine (as opposed to in the VM).

The Insight GUI might be a little slow in the VM, but you can disable it if you wish (see https://bloom.oscillate.io/docs/configuration#insight-config).

Let me know how it goes and if you have any issues.

[pr2zi]

Hi @navnavnav,
I was able to get bloom running on the VirtualBox. But I would still prefer a Solution using WSL. Is there any chance that this is realisable or you could have a look into this?

[navnavnav]

I'm glad you got it working in a VirtualBox VM.

There are no plans to look at Windows or WSL support in the near future.