ChanServ changed the topic of #glasgow to: glasgow debug tool · code https://github.com/GlasgowEmbedded/Glasgow · forum https://glasgow.whitequark.org · logs https://freenode.irclog.whitequark.org/glasgow
HexGlaze has quit [Ping timeout: 268 seconds]
HexGlaze has joined #glasgow
jacob| has joined #glasgow
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark pushed 3 commits to master [+0/-0/±3] https://git.io/fjxe3
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 1b71f1f - applet: fix outdated check in synthesis_test().
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 29b0b52 - applet: assertBuilds(): improve error on argparse failure.
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 42c038a - cli: every APPLET argument is required.
qazwsxal has quit [Ping timeout: 268 seconds]
qazwsxal has joined #glasgow
thaytan has quit [Ping timeout: 276 seconds]
thaytan has joined #glasgow
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark pushed 3 commits to master [+0/-0/±4] https://git.io/fjxfU
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 673b53e - support.asignal: fix thread unsafety.
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 765b757 - device.hardware: correctly handle asynchronous libusb cancellation.
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark c103a8f - software: fix build_ext not being called for bdist_wheel.
pinoaffe has joined #glasgow
<whitequark> electronic_eel: how's the test rig going? I lost track of this a bit
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark pushed 2 commits to master [+0/-0/±5] https://git.io/fjxUO
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 4de7004 - device.hardware: shut down libusb polling thread.
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 431f985 - device.hardware: GlasgowHardwareDevice.{usb→.usb_handle}
<whitequark> tnt: ok i FINALLY figured out what the hang was caused by
<tnt> \o/
<tnt> 4de7004 I guess ?
<whitequark> tnt: yeah
<whitequark> i didn't realize python will kill daemon threads in the middle of a C function that takes a lock *and* then proceed to call destructors
<whitequark> this seeems ... basically insane
<whitequark> like, i thought it destroys the interpreter *then* quits while killing daemon threads. or something to that extent
<whitequark> which come to think of it is probably just not possible
<whitequark> shared memory multiprocessing was a bad idea tbh
<whitequark> ok
<whitequark> what *was* i doing
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark pushed 3 commits to master [+0/-0/±3] https://git.io/fjxTq
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 1979b66 - device.hardware: short-circuit USB callback during shutdown.
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 76e7e29 - device.hardware: log cancelled USB transfers.
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark c47a734 - cli: await all tasks, not just the ones that are done.
<whitequark> ok i *think* that's all the USB bugs?
<electronic_eel> whitequark: I completed building the test jig pcb and basic checks were successful
<electronic_eel> for more detailed tests was waiting for the Glasgow from Greg to arrive - which - tada- it did today
<electronic_eel> but I didn't have time to look at it yet and won't until maybe very late this evening or even tomorrow
<whitequark> ack
<whitequark> no rush
pie_ has quit [Remote host closed the connection]
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark pushed 2 commits to master [+1/-0/±2] https://git.io/fjxI5
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 39a6c37 - support.data_logger: implement stdout, CSV and InfluxDB data loggers.
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 3d2387e - applet.sensor.scd30: use support.data_logger.
pie_ has joined #glasgow
ali_as has quit [Remote host closed the connection]
ali_as has joined #glasgow
pie_ has quit [Ping timeout: 252 seconds]
pie_ has joined #glasgow
pie_ has quit [Ping timeout: 248 seconds]
ali_as has quit [Read error: Connection reset by peer]
ali-as has joined #glasgow
evck has joined #glasgow
pie_ has joined #glasgow
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/fjxOb
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark ae08add - support.data_logger: fix InfluxDB tag handling.
<_whitenotifier> [Glasgow] Error. The Travis CI build could not complete due to an error - https://travis-ci.org/GlasgowEmbedded/Glasgow/builds/578005041?utm_source=github_status&utm_medium=notification
XgF has quit [Remote host closed the connection]
XgF has joined #glasgow
englishm has quit [Excess Flood]
englishm has joined #glasgow
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/fjxsY
<_whitenotifier> [GlasgowEmbedded/Glasgow] whitequark 81fcd37 - applet.sensor.bmp280: use support.data_logger.
pie_ has quit [Ping timeout: 245 seconds]
pie_ has joined #glasgow
<electronic_eel> whitequark: ok, now I got my glagow running!
<electronic_eel> does "glasgow run selftest pins-ext" work for you? I get an nmigen error when I try that
<electronic_eel> is that something with my setup or a bug in the code? when I check out the omigen tag it works
chris_99 has joined #glasgow
<chris_99> Hey, i'm just wondering roughly how much the assembled version of glasgow might cost? Also i'm just having a little look at https://github.com/GlasgowEmbedded/Glasgow/blob/master/software/glasgow/applet/memory/floppy/__init__.py would i be right in thinking writes are currently not supported (as per the comment)?
<electronic_eel> chris_99: re price - esden is planning to manufacture glasgows, but he didn't do a proper price calculation yet AFAIK
<electronic_eel> but my guess would be around 200$ as there are quite a lot of parts on glasgow
<chris_99> gotcha, thanks!
<electronic_eel> but if you can do bga soldering you can build one yourself
<ZirconiumX> The prototypes come up to about $200, yeah
<electronic_eel> re floppy: the comment in the floppy applet says "read and write disks using IBM/Shugart floppy drives"
<electronic_eel> but I haven't read further in the code or tested this applet myself
<electronic_eel> oh, sorry, I read further and it says "Writes are not currently supported" hmm
<chris_99> yeah, sorry that's the bit i meant. but i haven't looked through the code in detail
<electronic_eel> do you have an application that needs floppy writing?
<esden> electronic_eel: according to the last cost calculation I made they should retail at around ~$170 but it is not fixed in stone and is subject to changes. :)
<chris_99> yeah i wanted to play with a 5.25" floppy, writing to disk
<electronic_eel> esden: thanks, seems I was being conservative in predicting the price
<esden> yeah you are not that far off :D
<esden> who knows, depending on the tariffs and other things it might go up... :/
<electronic_eel> now we have leeway to add some more expensive ti parts in the next rev ;)
<esden> lol :D
<gruetzkopf> soo many small components packed at their min
<electronic_eel> yes, I got my glasgow today and when you see it with your own eyes you really see how densely packed it is
<electronic_eel> chris_99: when whitequark wrote the floppy applet I think she had primarily backup of floppys in mind
<electronic_eel> I don't know how much work it would be to add writing capability. Maybe you should ask her
<chris_99> gotcha that makes sense. backup is definitely more important
<electronic_eel> yeah. I don't know if I still would want to write to floppys today. There are floppy emulators for old computers out there that store image files onto sd card or similar. They connect up like a traditional floppy drive
<electronic_eel> once you have a backup of the floppy you could use one of these
<electronic_eel> with some software work glasgow could of course become such an emulator
pie_ has quit [Ping timeout: 245 seconds]