Saturday, 2017-09-02

*** tpb has joined #timvideos00:00
*** rohitksingh has joined #timvideos04:04
*** paradisaeidae_ has joined #timvideos04:43
*** sb0 has quit IRC05:00
*** nueces has quit IRC05:04
*** paradisaeidae_ has quit IRC05:05
*** sb0 has joined #timvideos05:56
mithropaddatrapper: Ping? I only just got started on stuff now...07:44
paddatrappermithro: pong07:44
mithropaddatrapper: How are things going?07:44
paddatrappermithro: snowed under with work, but I want to spend some time today on the loopback07:45
mithrorohitksingh: Ping? I found this today -> -- it seems to be a "softusb" core for the lattice ice40 boards  -- I'm assuming it is probably USB1.1 however....07:46
tpbTitle: TinyFPGA-B-Series/bootloader/verilog at master · tinyfpga/TinyFPGA-B-Series · GitHub (at
mithrorohitksingh: It is verilog however (compared to that one which is VHDL ->
tpbTitle: USB data transfer in VHDL (at
rohitksinghmithro: Thanks! looks interesting...I can definitely learn something some that code07:49
rohitksinghlooks very recent code07:50
rohitksinghmithro: fantastic idea it is! :) Thanks for sharing it!
tpbTitle: TinyFPGA (at
mithrorohitksingh: Have you seen too?07:55
tpbTitle: usb11_sim_model/USB FS TestBench.pdf at master · freecores/usb11_sim_model · GitHub (at
mithrorohitksingh: It's a USB1.1 host testbench07:55
mithrorohitksingh: I'm also just about to start working on getting sigrok to talk to litescope again...07:56
rohitksinghmithro: Nope, hadn't seen that freecores document before. Its new to me. It is very resourceful though. Saving that it in my PC for future reference!07:58
rohitksinghmithro: You said litescope already has support for sigrok?07:58
rohitksinghor just waveform export?07:59
mithrorohitksingh: Just writing dumping to sigrok compatible files07:59
rohitksinghmithro: oh okay08:00
mithrorohitksingh: But I want to be able to do capture/config/etc via sigrok08:01
rohitksinghmithro: you mean virtual device emulation via litescope right?08:01
rohitksinghsigrok would see litescope as a device, and can trigger, capture etc from it?08:02
mithropaddatrapper: Okay - when do you think you'll want to do that? I'm trying to make it so that it is easy to look at the FX2 signals by making some FPGA firmware which attaches litescope to the FX2 pins on the Opsis -- you can then capture the signals via ethernet08:04
mithrorohitksingh: Yes08:04
rohitksinghmithro: nice! :)08:05
mithrorohitksingh: Will hopefully be :-)08:08
paddatrappermithro: in about 2 hours08:29
paddatrappermithro: that sounds very useful!08:29
*** twoolie has joined #timvideos09:19
Ishan_Bansalmithro : ping09:26
mithroIshan_Bansal: pong09:26
Ishan_Bansalmithro : Will you be able to review the pull request by today, as I am getting my exams started from the day after tomorrow so I want to merge this pull request by tomorrow.09:29
*** twoolie has quit IRC09:29
mithroIshan_Bansal: I'm just trying to get some stuff ready for paddatrapper at the moment -- I'll try and look at it ASAP09:29
Ishan_Bansalmithro : Np.09:30
mithroIshan_Bansal: I would like to get it merged ASAP09:30
mithroIshan_Bansal: we should complain to shenki, he's off camping while we are hear actually doing something useful :-P09:32
Ishan_Bansalmithro : Also I add the documentation in the Adding_documentation branch in the litejpeg repository on my github, still require some changes.09:33
Ishan_Bansalmithro : He must have to give us some special treat for this one :P09:33
mithroIshan_Bansal: one thing which will make it faster to review is to make sure that none of my comments from previous pull requests also apply to this CL09:33
mithrobe back in ~10-1509:34
Ishan_Bansalmithro : Although I make sure that thing, but still may be I can see once again.09:35
*** twoolie has joined #timvideos09:49
paddatrappermithro: going to start working on it now10:03
mithroIshan_Bansal: What I mean is that check things like documentation & indentation and stuff10:03
mithropaddatrapper: So, I think the first thing is to figure out how you want the pins on the FX2 to toggle10:04
paddatrappermithro: they're LOW active mostly10:04
mithropaddatrapper: I mean, write out "X toggles low, then data appears on pins on port A, then X toggles high, then...."10:06
tpbTitle: FX2 FIFO Interface - Google Docs (at
paddatrapperAt the bottom10:10
mithropaddatrapper: added some comments10:13
paddatrappermithro: The table above explains the registers10:14
mithropaddatrapper: Okay - so where is the fx2 code for this?10:16
tpbTitle: WIP: Loopback Device by paddatrapper · Pull Request #43 · timvideos/HDMI2USB-fx2-firmware · GitHub (at
paddatrapperbusy fixing it at the moment to be more like the doc and your comment10:17
mithroping me when you have done that10:17
paddatrappermithro: done10:34
mithropaddatrapper: You don't seem to be sending the SKIP signal?10:43
paddatrappermithro: I am:
tpbTitle: WIP: Loopback Device by paddatrapper · Pull Request #43 · timvideos/HDMI2USB-fx2-firmware · GitHub (at
mithropaddatrapper: Can you create some defines for that?10:51
paddatrappermithro: sure10:51
mithroShould be something like10:52
mithroEP8BCL = SKIP_FIFO10:52
mithroWhere "#define SKIP_FIFO bmBIT710:52
mithro(bm == bitmask)10:52
*** twoolie has quit IRC10:54
paddatrappermithro: I did it as SKIP(8), but can change to bit definition if you want10:56
mithropaddatrapper: Yeah "SKIP(8)" would mean "skip 8 buffers" to me10:56
tpbTitle: fx2lib/eputils.h at master · mithro/fx2lib · GitHub (at
paddatrappermithro: fixed10:58
mithropaddatrapper: The interrupts are enabled/disabled like so ->
tpbTitle: fx2lib/autovector.h at master · mithro/fx2lib · GitHub (at
paddatrappermithro: but we aren't using the interrupts?11:01
mithropaddatrapper: I wondered if there should be something like "COMMIT_ARM_EP8()" and "SKIP_ARM_EP8()"11:01
paddatrappermithro: ah I see11:01
paddatrappermithro: I've got to head out now. I'll be back in about 4 hours11:03
mithropaddatrapper: I guess usart_send_byte_hex is enough of a "sleep"11:03
paddatrappermithro: can through more in, but I think so11:03
mithropaddatrapper: I may be in bed at that time11:03
mithropaddatrapper: Next step is to capture a trace of that output...11:03
mithropaddatrapper: Actually, you should just be able to look at the uart data...11:03
paddatrappermithro: yeah. I'm using sigrock to track the control signals (address, clock, etc) and uart for the actual data11:05
*** ChanServ sets mode: +v thaytan_13:43
*** thaytan_ is now known as thaytan13:43
*** thaytan has quit IRC14:12
*** twoolie has joined #timvideos15:01
*** twoolie has quit IRC16:37
*** nueces has joined #timvideos16:44
*** thaytan has joined #timvideos17:05
*** ChanServ sets mode: +v thaytan17:05
*** rohitksingh has quit IRC20:05

Generated by 2.13.1 by Marius Gedminas - find it at!