00:02 <_whitenotifier-5> [glasgow] TomKeddie synchronize pull request #275: cli: add --force-reload option to override bitstream id check in all cases - https://git.io/JtPFA

00:16 <_whitenotifier-5> [glasgow] TomKeddie opened issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtXQK

00:20 <_whitenotifier-5> [glasgow] whitequark commented on issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtXQy

00:20 <_whitenotifier-5> [glasgow] whitequark closed issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtXQK

00:22 <_whitenotifier-5> [glasgow] TomKeddie commented on issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtXQF

00:23 <_whitenotifier-5> [glasgow] whitequark commented on issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtXQA

00:24 <_whitenotifier-5> [glasgow] TomKeddie commented on issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtXQp

00:24 <_whitenotifier-5> [glasgow] whitequark commented on issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtXQh

00:26 <_whitenotifier-5> [glasgow] TomKeddie commented on issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtX7I

00:32 <_whitenotifier-5> [glasgow] TomKeddie commented on issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtX7G

00:55 <d1b2> <Greg> I agree with esden, empowering. I'm often using it as a tool for programming/debugging. So often I want it to be transparent. But it's reassuring to know that it can tackle anything.

00:59 <d1b2> <Greg> The way the entire project, hardware and software integrates is probably my favorite part. It legitimately puts a smile on my face when I think about all the steps that are happening (Some of which I still don't truely understand) when you run glasgow ... from a terminal, and within seconds you've reconfigured hardware and are looking at useful data!

00:59 <whitequark> :D

01:06 <samlittlewood> I keep being startled by how easy it is to connect user facing python to IO and a state machine - err - I’ve written l less than a page of code and it’s kinda starting to work - how did that happen?

01:09 <ebb> My 2c: I intend to write a PIC16 programming applet soon. I've used a lot of Python, only a tiny bit of Verilog, no (n)migen and that's pretty much all that's relevant here -- but I'm not afraid, because Glasgow is safely hackable

01:16 <_whitenotifier-5> [glasgow] rwhitby commented on issue #276: applet: explore ideas for testing usb 2.0 data with Glasgow - https://git.io/JtX5c

01:22 <whitequark> nice!

01:22 <whitequark> there's a branch that has LV PIC programming sketches

01:22 <whitequark> the problem is that PIC programming is kind of a major nightmare

01:22 <whitequark> the way to do it eventually is probably to parse pickit bytecode

01:23 <d1b2> <konsgn[no-Mic]> emulate the pickit pic?

01:23 <hl> pickit uses bytecode?

01:24 <whitequark> cc marcan

01:24 <ebb> Admittedly *my* end goal is to try reading out the firmware of one specific part

01:25 <ebb> But the programming guide for its subfamily did read as if the various commands and their binary encodings differ across parts a lot

01:27 <d1b2> <konsgn[no-Mic]> if it's non-lv then you also need a 12v supply to do erasing i believe, but just readback may not call for that.

01:27 <whitequark> they do differ a whole lot

01:27 <whitequark> and there are hundreds of protocols effectively

01:29 <d1b2> <konsgn[no-Mic]> for a while people were hacking the dat file of the pickit2 to add parts to it. That may be a file of interest. though it is related to communication to pickit2

01:30 <ebb> So it sounds like the pickit to some extent abstracts the part-specific details away?

01:30 <ebb> I'm not sure whether by bytecode you mean firmware or instructions sent from a PC

01:31 <d1b2> <konsgn[no-Mic]> some of, i think. eg: pickit3 can target pic32's but pickit 2 couldn't target them arbitrarily.

01:32 <d1b2> <konsgn[no-Mic]> although the pickit 2 was considered a more robust design.....or maybe thats just personal opinion

01:32 <d1b2> <konsgn[no-Mic]> 2 worked better with linux, i can say thatp

02:04 <d1b2> <DX-MON> my experiences with Glasgow have been a fantastic "plug and go" combined with the freedom to know that it's not Glasgow's fault when it's wrong.. it usually never is and I can trust it to be doing what I asked (case in point, debugging my keyboard's clock rates and UART.. after a rocky time even with BMP.. plugged in Glasgow to the keyboard and set it for autobaud UART.. within moments I had the confirmation I'd spent hours trying to get the other way

02:04 <d1b2> and was able to then confirm I'd correctly fixed the problem via the same autobaud route - something I've never been able to experience the pleasure of before

02:06 <d1b2> <DX-MON> (in the process, I even uncovered some "fun" behaviour in the way single-stepping works on the ATXMega processor on the keyb and observe how it'd fix the problem)

02:19 <whitequark> :)

02:40 <d1b2> <edbordin> So far I have just admired the design from afar, the whole thing looks beautiful to me :) I'd hope that the number of crowdsupply backers helps confirm that many others agree it is a tool they want to use

05:13 <_whitenotifier-5> [glasgow] TomKeddie commented on issue #171: selftest: some tests ignore --port spec - https://git.io/Jt1vm

05:13 <_whitenotifier-5> [glasgow] TomKeddie closed issue #171: selftest: some tests ignore --port spec - https://git.io/Je2JN

05:14 <_whitenotifier-5> [glasgow] TomKeddie commented on issue #151: Selftest is not supported on revC - https://git.io/Jt1vY

05:20 <_whitenotifier-5> [glasgow] rwhitby commented on issue #151: Selftest is not supported on revC - https://git.io/Jt1vB

06:20 <levi> The chat here today has made me excited to get my Glasgow from the crowdsupply run. :)

13:07 <fridtjof[m]> Me too :)

15:45 <d1b2> <theorbtwo> I've been excited to get a glaglow for ages, as someone who really wants to do electronics, but is afraid of breaking things. It seems well designed to let me do programming instead.

16:34 <modwizcode> I'm excited to have a real device to use jtag

16:35 <modwizcode> Especially one I can throw at some test points and have it probe the interfaces

20:33 <_whitenotifier-5> [glasgow] TomKeddie commented on issue #151: Selftest is not supported on revC - https://git.io/Jt1Sg

22:55 <gruetzkopf> mplabx IPE reflashes the pickit all the time when switching families

22:58 <gruetzkopf> (i have the misfortune of working with pic14/16/18 sometimes)