13:56 <emptty> Hello there, is there a way to retrieve the list of all currently connected boards?

13:56 <PaulFertser> emptty: connected where?

13:57 <emptty> I'm wondering whether it's possible to improve this code: https://github.com/tock/tockloader/blob/master/tockloader/openocd.py#L213 which issues some random commands to discover which board is actually connected to the computer on which the python script is running

13:57 <emptty> (I'm not a tock contributor, merely a [future] user)

14:02 <karlp> wow, that's never going to work well like that anyway :)

14:03 <karlp> a whole lot of parts will get detected as microbit_v2

14:03 <emptty> PaulFertser: my dream would be that openocd would somehow scan the USB to recognize the boards and targets that are available, idling

14:04 <karlp> that someone thought that code was useful does not inspire me with confidence in tock :|

14:05 <PaulFertser> lol, no way that's serious

14:05 <PaulFertser> emptty: sorry, that really doesn't make much sense

14:06 <emptty> that's also my feeling, and that's why I'm wondering whether you can do better

14:07 <karlp> openocd, for better or worse, doesn't do any sort of autodetection at all, across target types.

14:07 <karlp> it doesn't even support it within many families that _are_ detectable, so trying to script around it is going ot be a trainwreck.

14:08 <emptty> note that this code in tock is fully optionnal. Merely a fallback for the case where the user didn't provide the board name

14:09 <PaulFertser> It's not possible to auto-detect board because there are many different boards all looking exactly the same from debugger point of view.

14:11 <karlp> what led you to look at tock?

14:12 <karlp> it looks like a relatively stagnant academic project

14:20 <emptty> curiosity, mostly. I like the idea of how they protect memory and their notion of capsule. But I'm only lurking around