Saturday, 2018-04-07

*** tpb has joined #timvideos00:00
*** nancy has joined #timvideos00:12
*** nancy has quit IRC00:21
*** Ali-Saurus has quit IRC01:11
*** theshaun111 has joined #timvideos02:33
*** theshaun has quit IRC02:34
*** theshaun111 is now known as theshaun02:34
*** CarlFK has quit IRC03:14
*** nancy has joined #timvideos03:38
*** nancy has quit IRC03:38
*** CarlFK has joined #timvideos03:48
*** ChanServ sets mode: +v CarlFK03:48
*** sb0 has quit IRC04:12
*** rohitksingh has joined #timvideos04:50
*** rohitksingh has quit IRC04:55
*** rohitksingh has joined #timvideos05:03
*** rohitksingh has quit IRC05:05
*** rohitksingh has joined #timvideos05:08
*** rohitksingh has quit IRC05:12
*** rohitksingh has joined #timvideos05:13
*** rohitksingh has quit IRC05:15
*** rohitksingh has joined #timvideos05:16
*** nancy_ has joined #timvideos06:41
*** nancy_ has quit IRC07:02
*** nancy_ has joined #timvideos07:53
*** nancy_ has quit IRC07:56
*** CarlFK has quit IRC08:49
*** nancy_ has joined #timvideos09:39
*** nancy_ has quit IRC09:52
*** i___ has joined #timvideos10:19
*** i___ has quit IRC10:35
*** nancy has joined #timvideos13:29
*** nancy has quit IRC14:09
*** sb0 has joined #timvideos14:33
*** CarlFK has joined #timvideos15:12
*** ChanServ sets mode: +v CarlFK15:12
*** sb0 has quit IRC15:57
*** nancy has joined #timvideos16:47
nancyHelp !16:47
*** nancy has quit IRC16:49
*** nancy has joined #timvideos16:50
CarlFKnancy: please post your question too.17:02
CarlFKer... please just post a question instead of "help"17:03
nancysorry sir17:04
nancynet not so good , had  a doubt regarding last year's work , The run length encoding adopted17:05
nancysir was looking at the scripts and didnt understand , what we wanted , we have to code it upto 3 level deep!17:06
nancyAnd sir for the image size conversion-padding/cropping : python script which imports PIL library and than we integrate it with the existing HDMI Litex firmware17:12
*** nancy_ has joined #timvideos17:14
*** nancy_ has joined #timvideos17:15
nancy_Sir for Image size conversion , a script importing PIL library and than , integrating with existing Litex Firmware ( In case the message has been missed)17:16
*** nancy has quit IRC17:18
nancy_is it in right direction . correct me sir17:25
CarlFKnancy_: I don't think you can import PIL in the micro python environment17:31
CarlFKalso, that isn't what I was thinking.17:31
CarlFKnancy_: I recommend staring with the most simple case: same input resolution as output, what we have now,  but instead of transferring the whole frame, loop over it and transfer one row at a time17:33
nancy_ok sir , we cant either do it with ffmpeg ?17:38
CarlFKnancy_: what cpu would run ffmpeg?17:42
nancy_sir as far as i know the CPU will affect the speed of the process.17:45
CarlFKwhat CPU?17:45
nancy_sir that i didnt check17:49
nancy_I found it : hardware requirements are basically any cpu17:54
nancy_only speed will vary according to hardware17:55
CarlFKnancy_: did you think the fpga would run ffmpeg?17:55
paddatrappernancy_: there is no traditional cpu to work with here...17:56
paddatrapperYou do have the softcpu though17:58
nancy_ok sir17:59
CarlFKnancy_: can you find me the code that copies the input frame?18:13
*** nancy has joined #timvideos18:17
*** nancy_ has quit IRC18:18
paddatrapper<+CarlFK> nancy_: can you find me the code that copies the input frame?18:19
paddatrappernancy: ^18:19
nancysir , looking18:22
*** nancy has quit IRC18:36
*** nancy has joined #timvideos18:37
CarlFKhey look, I made a test.  :)
tpbTitle: HDMI2USB-litex-firmware/ at master · CarlFK/HDMI2USB-litex-firmware · GitHub (at
CarlFK  "expected version test passed."18:40
tpbTitle: Ubuntu Pastebin (at
CarlFKnow to figure out how to do that with jenkins18:41
CarlFKbut after I go to the store to get milk for breakfast18:41
CarlFKnancy: where did you see last years work?  "looking at last year's work , the pixels are copied using the existing DMA engine in the gateware"19:26
nancysir , yes was looking at code
tpbTitle: HDMI2USB-litex-firmware/firmware at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
nancysorry for late reply , was in other tab ..19:37
nancywas trying to understand the firmware code19:38
paddatrappernancy: so you're looking at the current code? Just checking that you're not working off an old version lying around somewhere20:05
nancy  checking this20:08
tpbTitle: HDMI2USB-litex-firmware/gateware at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
paddatrappernancy: yup, that's the one20:09
tpbTitle: HDMI2USB-litex-firmware/pattern.c at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
tpbTitle: HDMI2USB-litex-firmware/hdmi_in0.c at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
nancylast 2 , possible inputs20:10
paddatrappernancy: hdmi_in1.{h,c} is another input (the second HDMI input)20:22
nancy is it related to this issue sir20:26
tpbTitle: Replace hdmi_in0.c with template thing · Issue #383 · timvideos/HDMI2USB-litex-firmware · GitHub (at
paddatrappernancy: yeah, it is a horrible hack20:27
nancyyes sir20:29
paddatrapperGrr... Let's try that again21:05
paddatrapperG'night all21:05
felix[m]1Hi everybody! I'm trying to flash the HDMI2USB firmware onto a nexys video. Flashing the gateware (via python --mode=gateware) works fine, but the firmware throws an "AssertionError: File is too big! -32768 file does not fit in 67992 space".21:23
felix[m]1I'm assuming that there is a missing value in the calculation at
tpbTitle: HDMI2USB-litex-firmware/ at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
felix[m]1Here's where the error comes from:
tpbTitle: HDMI2USB-litex-firmware/ at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
felix[m]1Hmm, if `address_start = platform.gateware_size + make.BIOS_SIZE` and `address_end = platform.gateware_size` and finally `file_end = address_start+file_size`, the assertion `file_end < address_end` can't possibly hold, can it?21:30
CarlFKfelix[m]1: stand by....21:35
felix[m]1Sure! Please let me know if there's anything I can try. I'd have thought that the additions for address_start and address_end were swapped, but that's where the bios is supposed to go, right?21:37
CarlFKfelix[m]1: -32768 is ... I think 111 111 111 111  signed 2 byte int ?21:38
felix[m]1Hmm, that seems a bit too high a value?21:40
CarlFKnot so much high, just unlikely that it is a meaningful number21:40
CarlFKit is the result of address_end - address_start - right?21:41
tpbTitle: Wolfram|Alpha: Computational Intelligence (at
* felix[m]1 sent a long message: felix[m]1_2018-04-07_21:40:42.txt <>21:44
tpbTitle: Wolfram|Alpha: Computational Intelligence (at
CarlFKthats a little more telling..21:45
felix[m]1Yes, that was a much better idea :-)21:45
CarlFKaddress_start = 16809984  address_end = 1677721621:45
CarlFKthe end is before the start, right ?21:45
CarlFK16 809 984   16 777 21621:46
felix[m]1Could it have something to do with the `gateware_size = 0x1000000` at
CarlFKI suspect our 111... thing is the result of "overflow error"21:46
tpbTitle: HDMI2USB-litex-firmware/ at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
felix[m]1But that goes into both values? I'm confused (and utterly incapable of doing arithmetic :-) )21:47
CarlFKforget the math, the start/end descriptions don't make sense to me21:48
CarlFKim assuming start should be less than end21:48
felix[m]1Yes, I think you're right. FWIW, the `bios_size` is 32768, which would explain the difference, because it's added only to `address_start`?21:49
CarlFKnancy: I have another task for you to help get you started understanding the code: add a 3rd test pattern to
tpbTitle: HDMI2USB-litex-firmware/pattern.c at master · timvideos/HDMI2USB-litex-firmware · GitHub (at
CarlFKfelix[m]1: um.. im not going to pretend to understand your question ...21:51
felix[m]1address_start = platform.gateware_size + make.BIOS_SIZE # -> 0x1000000 + 3276821:51
felix[m]1address_end = platform.gateware_size # -> 0x100000021:51
felix[m]1so address_end - address_start -> -3276821:51
CarlFKaddress_end = platform.gateware_size21:51
CarlFKaddress_start = ... that looks odd to me21:52
felix[m]1Yes, that's what I was thinking (sorry for causing confusion)21:53
felix[m]1But adding the value of make.BIOS_SIZE to address_end instead of address_start would overwrite the bios, right?21:54
felix[m]1So BIOS_SIZE should be added to both, plus an additional offset for the size of the firmware?21:55
CarlFKum.. something like that21:55
felix[m]1(which is only added to address_end)21:55
felix[m]1Or, more generally, since this route (via can't possibly work, how do you flash your board? There must be another way, right?21:56
CarlFKmy guess (never even considered this before) is the bios goes from 0 to bios_size, and then the gateware? from bios_size+1 to.. how ever much it needs21:56
CarlFKI use mode-switch to flash Atlys and Opsis21:57
CarlFKthose are the only 2 boars I have21:57
felix[m]1Ok, I'll open an issue for this, and try mode-switch. Thanks a lot!21:59
felix[m]1And sorry for being obtuse -- I should be heading to bed. I'm super-thankful for your helping me confirming this, I was starting to question my sanity, not to mention my basic math capabilities :-)22:01
CarlFKfelix[m]1: no problem - happy to help, even if I am not sure whats going on either22:08
CarlFKfelix[m]1: this is how I flash:
tpbTitle: Flashing Firmware · timvideos/HDMI2USB Wiki · GitHub (at
felix[m]1Ah, awesome, thanks! I was trying to reverse-engineer the `make flash` command. I've been digging through the mode-switch code, looks like it only supports the opsys and altys, though22:11
felix[m]1I'll search the wiki more thoroughly, chances are I've missed something.22:12
CarlFKchances are what you are looking for hasn't been written or documented22:19
CarlFKtumbleweed: ^^^ "trying to flash the HDMI2USB firmware onto a nexys video. "22:20
felix[m]1Ok, opened an issue at
tpbTitle: Support flashing to board on nexys_video platform / check flash addresses · Issue #425 · timvideos/HDMI2USB-litex-firmware · GitHub (at
felix[m]1No problem, though I'm thinking about just submitting a pull request instead.23:37
felix[m]1But even with all the changes in place, flashing fails consistently -- the image on the board doesn't seem to get overwritten at all.23:38
felix[m]1I must be missing something; what could that be?23:38
felix[m]1The jumper is set to JTAG programming23:38
felix[m]1Here's the output of make image-flash-py:
tpbTitle: Ubuntu Pastebin (at
felix[m]1Ok, `make gateware-flash-py` works, and contents match.23:47
felix[m]1... and so does `make firmware-flash-py`.23:49
felix[m]1How can I find out whether the nexys video needs a bios?23:49
felix[m]1(`make bios-flash` says 'unsupported')23:49
felix[m]1So after flashing gateware and firmware individually, `flterm --port=/dev/ttyUSB0 --speed=115200` doesn't work (though the TX led shows that characters are reaching the board).23:52
felix[m]1Same result for `flterm --port=/dev/ttyUSB0 --kernel=build/nexys_video_video_lm32/software/firmware/firmware.bin --speed=115200`23:54
felix[m]1Temporary loading via `openocd` also continues to work.23:56

Generated by 2.13.1 by Marius Gedminas - find it at!