Post B9OiVzr4ULc2mIDBho by mntmn@mastodon.social
(DIR) More posts by mntmn@mastodon.social
(DIR) Post #B9Mp8GDIKMMRvSJcJ6 by mntmn@mastodon.social
0 likes, 0 repeats
> glasgow flash
(DIR) Post #B9MqCo9kAf7MJGO2bY by mhoye@cosocial.ca
0 likes, 0 repeats
@mntmn is this some horrifying variation of “glasgow kiss”
(DIR) Post #B9MqtaXAh3d6VtkCJM by mntmn@mastodon.social
0 likes, 0 repeats
finally trying out my glasgow (C3), connected it to the I2C port on a pocket mainboard and put the system controller (rp2040) in programming mode so it doesn't do anything. glasgow can then scan and find all the chips on the I2C bus on the board. not sure if it can peek/poke the registers also. would be cool to auto identify the chips.
(DIR) Post #B9Mr6Ee1OCwqOAyjpo by mntmn@mastodon.social
0 likes, 0 repeats
ah nice, there's a REPL https://glasgow-embedded.org/en/use/repl-script.html
(DIR) Post #B9Mur0p0toyyzX7IdE by grimmware@chaos.social
0 likes, 0 repeats
@mntmn I’d love to know how you get on with it, I’ve been eyeing one for a while
(DIR) Post #B9MvU4ulcGh8ykR5rE by mntmn@mastodon.social
0 likes, 0 repeats
@grimmware it seems to be a very solid base, could use some higher level tooling to auto identify i2c chips and talk to them (although there are like a dozen applets for various sensors), GUI would be cool too.
(DIR) Post #B9OiR8oVkjiR7BhOQS by mntmn@mastodon.social
0 likes, 0 repeats
@whitequark @grimmware I see, thanks for the extra info! What would be useful for MNT stuff (goal: diagnose board health with one or two i2c connections) is probably if I made a custom script based on the i2c-controller applet that knows about all possible chips that can be there, and has some register maps for them. But idk how to write the python code in a way that would benefit other people from reusing those "chip definitions" like a library. Maybe I'm overthinking it though.
(DIR) Post #B9OiVzr4ULc2mIDBho by mntmn@mastodon.social
0 likes, 0 repeats
@whitequark @ftg @ignaloidas @grimmware ah yes, totally. i could add detection data for the chips that we use.
(DIR) Post #B9Oj2CiGDc9BvGRqj2 by mntmn@mastodon.social
0 likes, 0 repeats
@whitequark @ftg @ignaloidas @grimmware yes, that sounds good and useful. and the next step would be a table of useful readable registers and their encodings. this will be even more busywork of writing the tables, but also something that i'll happily contribute to, for example for a bunch of BMS chips.
(DIR) Post #B9OjmtG0N8hhByUf6u by mntmn@mastodon.social
0 likes, 0 repeats
@whitequark @ftg @ignaloidas @grimmware all of them, but as a later step. i'm really thinking about leaning as hard as possible into the "explorer" part of the "interface explorer" :D so the endgame, for me, would be to be able to inspect all useful registers of the chips available on i2c, in python objects. then it would be quite satisfying to build quick GUIs for instrumentation also
(DIR) Post #B9Oknd0wLg1V3jMYhE by mntmn@mastodon.social
0 likes, 0 repeats
@whitequark @ftg @ignaloidas @grimmware oh yes, that looks totally usable
(DIR) Post #B9OkvQdGGgfOyS0Tz6 by mntmn@mastodon.social
0 likes, 0 repeats
@whitequark @ftg @ignaloidas @grimmware exciting! and good bug hunting!