While flashing and testing the batch of boards I've just run, I also noticed that the Glasgow's serial isn't reported correctly until the glasgow utility has interacted with it for the first time (since power up).

This seems to be because the firmware needs to be loaded (software/glasgow/device/hardware.py:88), which is fair enough / makes sense.

While digging, I also noticed that a list of connected serials is in fact listed if A) no serial number is given, and B) there are more than 1x Glasgows attached to the system. See software/glasgow/device/hardware.py:120, for example:

venv:$ glasgow run selftest loopback
E: g.cli: found 2 devices (serial numbers C1-20200923T174926Z, C1-20200923T190627Z), but a serial number is not specified

I appreciate that this is only presented when required... but it isn't presented when an invalid serial is given (e.g: "oops - pick from this list"), and it feels like a bit of an unexpected route (i.e: "just try running something" vs "show me a list").

Yeah, reasonable request.

This seems to be because the firmware needs to be loaded (software/glasgow/device/hardware.py:88), which is fair enough / makes sense.

You can also run glasgow flash, which will cause the firmware to be loaded on power-up. Glasgow boards that are distributed to general public actually have to be shipped in that state because otherwise you have to do an annoying little registry dance to have them recognized via WinUSB.

You can also run glasgow flash, which will cause the firmware to be loaded on power-up.

Oh, oops... I didn't run this step for the batch I've just done - I just ran glasgow factory, and then the various self test steps. Everything seems to work okay - I'll have a play and then send an email to the group so that they're aware that this might be something worth doing(!)

Glasgow boards that are distributed to general public actually have to be shipped in that state because otherwise you have to do an annoying little registry dance to have them recognized via WinUSB

Huh, interesting... For clarity, do boards need to be shipped with firmware flashed? (i.e: which state are you referring to by "in that state")

For clarity, do boards need to be shipped with firmware flashed (i.e: which state are you referring to by "in that state")?

Boards need to be shipped with firmware flashed so that they present the WinUSB descriptor on first plug-in. Otherwise Windows remembers the lack of the descriptor and you'll get an access violation even if you plug a flashed board in.

You can fix that by deleting a single registry key (which I think it's possible to write a .reg file for, and it's definitely possible with a short PowerShell snippet), or by using a driverless INF file (which someone will have to write, but it's straightforward).

But it's easiest to ship flashed boards, in which case no interaction is necessary. Install the Python package and off you go.

Understood - thanks for the clarification! I had expected it to be that way round, but wanted to be sure.