00:00 <josHua[m]> Is there some specific information that you find that manual lacking? For instance, what would you like to see in a tutorial? I took a pass on the getting started guide a few months ago and feel at least some sense of responsibility for it, and I'm interested in how people would like to use Glasgow to make the getting started guide more useful.

00:43 <_whitenotifier-1> [glasgow] whitequark created branch update-lockfile - https://github.com/GlasgowEmbedded/glasgow

00:43 <_whitenotifier-1> [glasgow] whitequark opened pull request #685: Update `pdm.min.lock` - https://github.com/GlasgowEmbedded/glasgow/pull/685

00:50 <_whitenotifier-1> [glasgow] github-merge-queue[bot] created branch gh-readonly-queue/main/pr-685-e2597fd67d7e046043e88c8ebb2b4e720d091b08 - https://github.com/GlasgowEmbedded/glasgow

00:58 <_whitenotifier-1> [GlasgowEmbedded/glasgow] github-merge-queue[bot] pushed 1 commit to main [+0/-0/±1] https://github.com/GlasgowEmbedded/glasgow/compare/e2597fd67d7e...b0fd3eb1e65d

00:58 <_whitenotifier-1> [glasgow] github-merge-queue[bot] deleted branch gh-readonly-queue/main/pr-685-e2597fd67d7e046043e88c8ebb2b4e720d091b08 - https://github.com/GlasgowEmbedded/glasgow

00:58 <_whitenotifier-1> [glasgow] whitequark deleted branch update-lockfile - https://github.com/GlasgowEmbedded/glasgow

00:58 <_whitenotifier-1> [glasgow] whitequark closed pull request #685: Update `pdm.min.lock` - https://github.com/GlasgowEmbedded/glasgow/pull/685

05:30 <l0rds474n[m]> It's pretty good but some more hands on examples would be nice. As an example, how do I use it to find correct pinout etc.

05:30 <l0rds474n[m]> So you out there who use it, show us how you use it.

05:36 <josHua[m]> Got it. In my mind, that question is maybe more for a general description of hardware reverse engineering (the https://securinghardware.com/ curriculum, perhaps?). What kind of device, and what kind of interface are you looking to find pinouts of? What would you like to use a Glasgow for that it would be useful to have tutorials of?

05:36 <josHua[m]> I think it makes a lot of sense to have more "suggestions" for using Glasgow to stimulate the imagination of what's possible. I particularly like using it for I2C things, since it speaks I2C just a lot better than the 'original Glaswegian device' (i.e., FTDI MPSSE) and so that's what I usually break mine out for, though I think that i2c eeproms are one of the listed examples!

05:41 <l0rds474n[m]> That's a good question, I get a lot of unknown boards that I have to investigate 😁

05:41 <l0rds474n[m]> But I also do a lot of SPI and I2C.

05:43 <josHua[m]> there is the jtag-pinout applet to automatically probe JTAG pinouts

05:46 <l0rds474n[m]> Looked at that but not sure what I get out of it. Haven't been able to test my unit in my lab yet, only checked that it's working with the software etc.

05:47 <josHua[m]> there is also the `i2c-initiator` applet, but obviously the tricky thing about I2C and SPI is that there is not really a one way to talk to any given peripheral! to get a sense of the users that I'd be writing for, if I said "to work with an arbitrary peripheral that you have a datasheet for, here is the outline of some Python code that you would write", would that be exciting or scary?

08:00 <l0rds474n[m]> Python is a normal language I use so no problem to get an example from that. Just looked at how to script things with this device.

08:02 <l0rds474n[m]> * this device. But true that SPI and I2C is device specific but to get started it could be nice how to think etc.

08:04 <josHua[m]> cool, that's useful information. I think one question I've been trying to answer is to what degree the median Glasgow user is or is not comfortable with writing and interacting with Python, and/or with doing some toolsmithing as part of their day-to-day work. but it sounds like a tutorial of the form "I am going to go grab a random I2C device off my desk, and get it working by hand, then write a script to drive it to do some task that I

08:04 <josHua[m]> care about in an idiomatic form" would be useful

08:10 <l0rds474n[m]> Sounds good, basically I will use this device for everything I can when I'm warmed up 😉

08:10 <l0rds474n[m]> One device to rule them all is something my wife likes, she doesn't have a ton of hardware laying around 😉

10:14 <Attie[m]> there is a (very basic) i2c script example!

10:14 <Attie[m]> https://github.com/GlasgowEmbedded/glasgow/blob/main/examples/i2c-pcf8574.py