Wednesday, 2018-02-07

*** tpb has joined #timvideos00:00
*** ducky[m] has quit IRC00:15
*** micolous[m] has quit IRC00:16
*** jea[m] has quit IRC00:16
*** nbags[m] has quit IRC00:16
*** CarlFK[m] has quit IRC00:17
*** hozer has quit IRC00:20
futarisIRCcloudNB, we have a Digilent Analog Discovery 2 here, so I could probably use that to check the HSYNC and VSYNC for VGA...00:25
*** nbags[m] has joined #timvideos00:50
*** ducky[m] has joined #timvideos01:15
*** micolous[m] has joined #timvideos01:15
*** jea[m] has joined #timvideos01:15
*** CarlFK[m] has joined #timvideos01:15
*** nbags[m] has quit IRC02:57
*** micolous[m] has quit IRC02:57
*** jea[m] has quit IRC02:57
*** CarlFK[m] has quit IRC02:57
*** ducky[m] has quit IRC02:58
*** rohitksingh_work has joined #timvideos03:55
tpbTitle: GitHub - dirjud/Nitro-Parts-lib-Xilinx: This is mainly a simulation library of xilinx primitives that are verilator compatible. (at
tpbTitle: conda fails to install python=36 (verification error) · Issue #22 · timvideos/litex-buildenv · GitHub (at
ewenmithro: It appears by far the fastest solution to "conda can't upgrade from python=3.5 to python=3.6" is just to move build/conda aside, and run `scripts/` to install a brand new conda environment.  (That issue has a bunch of other things I tried unsuccessfully to hopefully avoid others having to repeat the same problems...)04:18
ewenmithro: I've just added a comment to the litex-buildenv commit changing to python-3.6 pointing at that issue, to help someone else find the quicker solution...04:21
futarisIRCcloudewen: I found that too. I was doing a clean build for other reasons, so just ended up removing build completely.04:38
ewenfutarisIRCcloud: Thanks for the confirmation.  Removing build/conda seems sufficient, and faster than having to, eg, download Linux git again too.04:43
ewenBut it's probably going to be a trap a bunch of the fpga-miniconf users fall into...04:44
ewenmithro: Maybe post something to fpga-miniconf list pointing out issue, and quickest work around?04:44
*** micolous[m] has joined #timvideos05:42
*** ducky[m] has joined #timvideos05:59
*** jea[m] has joined #timvideos06:04
*** swalladge has quit IRC06:10
*** nbags[m] has joined #timvideos06:16
*** CarlFK[m] has joined #timvideos06:23
*** swalladge has joined #timvideos06:26
*** futaris[m] has joined #timvideos06:32
*** ewen has quit IRC07:00
*** thaytan has quit IRC07:54
*** thaytan has joined #timvideos07:55
*** ChanServ sets mode: +v thaytan07:55
cr1901_modern_florent_: So in litesdcard, it's not possible to read SCR register if you attach SDCore to the BIST Module, correct?08:16
cr1901_modernerr let me rephrase that08:17
cr1901_modern_florent_: So in litesdcard, it's not possible to read the data returned from the SD card* if you attach SDCore to the BIST Module, correct?08:18
cr1901_modernThis complicates supporting old cards that don't support CMD23 (SET_BLOCK_LENGTH)... b/c reading the SCR register (ACMD55) is how you figure out which commands are supported.08:19
cr1901_modernAnd SCR register is a command that has a data payload.08:19
cr1901_modern_florent_: Current status is that I'm writing a Wishbone bridge module for litesdcard, but there's gonna be some conflicts w/ the existing BIST that I need help with once I submit a pull. I'll let you know.08:20
*** sb0 has quit IRC08:26
*** xobs has quit IRC09:39
*** xobs has joined #timvideos09:44
*** futarisIRCcloud has quit IRC11:05
*** sb0 has joined #timvideos11:22
*** cr1901_modern has quit IRC12:33
*** cr1901_modern has joined #timvideos12:34
*** rohitksingh_work has quit IRC12:36
*** sb0 has quit IRC12:54
*** cr1901_modern1 has joined #timvideos13:04
*** cr1901_modern has quit IRC13:06
*** cr1901_modern1 has quit IRC13:19
*** cr1901_modern has joined #timvideos13:20
*** sb0 has joined #timvideos13:30
*** cr1901_modern1 has joined #timvideos13:46
*** cr1901_modern has quit IRC13:48
*** cr1901_modern has joined #timvideos14:39
*** cr1901_modern1 has quit IRC14:40
_florent_cr1901_modern: litesdcard only has 1 sink/1 source. For now the user should provide the mux before that so that you can have BIST + another sink/source.14:43
cr1901_modern_florent_: Is there a way to access the memory port of a sink?18:09
cr1901_modern_florent_: Ignore last q18:09
mithroCarlFK: look at the comments in the github UI -- my comments would make more sense then18:20
CarlFK[m]mithro: um.. I just looked.  still not sure what you mean18:22
CarlFKmithro: still lost18:24
mithroCarlFK: That comment refers to the new lines inside the def find_last_rev function18:25
CarlFKoh.  so you are top posting ;)18:25
CarlFKmithro: um.. my UI is a little different ... sec...18:26
mithroCarlFK: click the "Files changed" tab18:29
CarlFKmithro: still not sure which lines you are talking about18:31
tpbTitle: finds last rev that built, and caches github by CarlFK · Pull Request #97 · timvideos/HDMI2USB-mode-switch · GitHub (at
CarlFKmithro: umm... what comment and what lines are you talking about ?18:32
mithroCarlFK: That is the UI I'm looking at18:33
mithroCarlFK: Do my comments make more sense when looking at that UI?18:34
mithroCarlFK: Okay, I'll try again18:37
CarlFKmithro: lets go though each one.18:37
CarlFK           FIXME: Move cache to a class18:37
CarlFKdo you want that to be added as a #comment or actually re coded now?18:37
mithroCarlFK: There - I removed my old comments and added more explicit requests18:40
mithroCarlFK: do they make more sense?18:41
CarlFKmithro: yes.18:45
CarlFKmithro: the UI doesn' t make it obvious if you are commenting on code above or below18:45
mithroCarlFK: Okay - the general idea is that you put the comment at the start of the scope the comment relates to (IE for functions that would be after the function definitions, for files that would be at the top/first line of the file, etc)18:47
CarlFKmithro: that seems odd.  is it somehow dictated by something, or some convention ?18:50
mithroCarlFK: Common convention18:53
mithroCarlFK: IE -- It's were you would put a docstring for the object18:53
CarlFKmithro: huh.  seems more like top posting to me.18:54
mithroCarlFK: Generally after fixing each comment you would reply with "Done" or "Fixed" on each one separately btw19:08
CarlFKmithro: ah - sure.  next time19:11
mithroCarlFK: Better code review tools let you basically "mark comment as fixed"19:11
*** springermac has quit IRC19:17
CarlFKmithro: I'm not sure this is important, but if you have a sec..       hdmi2usb-mode-switch -v --by-type atlys --flash-image ...   Numato Opsis in 'operational' mode ...
tpbTitle: Ubuntu Pastebin (at
CarlFKshould it be telling me about  Opsis when I say --by-type atlys ?19:39
mithroCarlFK: because you have -v19:50
CarlFK[m]k - just making sure.19:51
CarlFKmithro: another if you have time.  current udev rule package (no idea if it was ever tested for Atlys)  $ hdmi2usb-mode-switch -v --by-type atlys --load-fx2-firmware hdmi2usb.hex  (no sudo)20:31
CarlFKFound exart-uarts at [LsusbDevice(04e2:1410:0001 /dev/bus/usb/002/012)] associating with Atlys at []20:31
tpbTitle: Ubuntu Pastebin (at
*** cr1901_modern has quit IRC20:32
CarlFKvizzini-dkms Installed: 1.0.0-5~ppa3~ubuntu14.0420:33
CarlFKI forget if that kicks in before --load-fx2-firmware hdmi2usb.hex20:34
CarlFKdmesg shows [4885339.175478] usbcore: registered new interface driver vizzini20:35
*** cr1901_modern has joined #timvideos20:35
mithroCarlFK: You don't have both Atlys USB plugged in?21:18
mithroCarlFK:  Found exart-uarts at [LsusbDevice(04e2:1410:0001 /dev/bus/usb/002/012)] associating with Atlys at []21:19
mithroCarlFK: That means there is something wrong with the FX2 on the Atlys21:19
CarlFK[m]mithro (IRC): huh.  "yes".    fixed by unplugging everything plugging it back in.. etc.  odd that this is an atlys mouted in a case with usb cables attached to the side of the case, and they looked well seated.21:27
CarlFK[m] Found exart-uarts at [LsusbDevice(04e2:1410:0001 /dev/bus/usb/002/064)] associating with Atlys at [Board(dev=LsusbDevice(1443:0007:0000 /dev/bus/usb/002/065), type='atlys', state='unconfigured')]21:28
mithroThere could multiple things going wrong21:28
mithroCarlFK[m]: mode-switch is not well tested with an Atlys and the exart serial interface makes things even more complicated21:28
CarlFK[m]mithro (IRC): this line line wasn't showing up in lsusb Bus 002 Device 068: ID 1443:0007 Digilent Development board JTAG21:34
CarlFK[m]and I am sure it was before.  and didn't touch cables.21:35
*** springermac has joined #timvideos22:13
*** FelixVi has joined #timvideos22:50
*** samsagaz has quit IRC23:47
*** futarisIRCcloud has joined #timvideos23:49

Generated by 2.13.1 by Marius Gedminas - find it at!