Can't connect second Bela Mini to Windows

PaulELong

This used to work but it's been a while since I had both connected. I can connect to each one separately, and they each have a different IP address.

One issue I've noticed is the iSerialNumber on the second device I plug in shows an error in USB Device Viewer from the windows SDK:

"iSerialNumber: 0x03
!ERROR: No String Descriptor for index 3!".

The first one shows "bela". From what I understand the value should be unique or it can cause issues. Can I change what the bela/pocketbeagle returns when USB is enumerated?

giuliomoro

When it worked previously was it on Windows? You may have updated windows in the meantime and that may have changed some things related to the drivers?

If the devices have different usb descriptors, it must be because they are running different versions of the Bela image. Are these the same boards that used to work together in the past? See if you can flash them both with the latest image and start from there.

PaulELong

It's possible it was working on a previous machine with win10, and now I reinstalled Win11 fresh, so that could be
a difference. Also, it detects both devices as separate drives. But it doesn't detect both network interfaces. I can try to reflash them, but that is a bit of work.

What I'm wondering is that since they both show the same iSerialName as "__bela__", do you know of a way I can change one of them to something else? Is there a config file somewhere that defines this value?

giuliomoro

PaulELong What I'm wondering is that since they both show the same iSerialName as "bela", do you know of a way I can change one of them to something else? Is there a config file somewhere that defines this value?

Sure, change __bela__ to something else in /opt/Bela/bela_gadget.sh and reboot.

PaulELong d now I reinstalled Win11 fresh, so that could be a difference.

I think Windows 11 may show two different network interfaces for each Bela, each interface served by a different driver. Do you see 2 from one and 0 from the other?

PaulELong

Yes, I was only seeing two network interfaces. I made the change to __bela2__ and now it's working. Another issue I saw before the change is that I tried to rename the adapter so I could tell them apart. But when I renamed the adapter to bela1, and then removed the first bela and attached the second, it would also be called bela1. That's another reason I thought they were getting identified as the same thing. Also, maybe this step is required to run into the issue I was seeing. Perhaps there was some new requirement, or naming them caused the problem, but at this point it seems to be working. Thanks for the help!

giuliomoro

Ok thanks for the detailed debrief report