*** tpb has joined #timvideos | 00:00 | |
mithro | bblr | 00:00 |
---|---|---|
futarisIRCcloud | _florent_: Thanks for the input. I tried synthesising a gateware for mimasv2, but it fell over. "AttributeError: 'Record' object has no attribute 'clk_p'" | 00:00 |
futarisIRCcloud | _florent_: https://github.com/futaris/litex-buildenv/commit/0d970ca06f3ecb53a6a1402eda2f308ac15c0c4c | 00:05 |
tpb | Title: add mimasv2 video · futaris/litex-buildenv@0d970ca · GitHub (at github.com) | 00:05 |
futarisIRCcloud | mimasv2 seems broken in latest git | 00:31 |
*** ewen has joined #timvideos | 02:53 | |
futarisIRCcloud | Hi Ewen. I rolled back the submodules too. Just doing a rebuild again now, with the rev you said worked... | 03:22 |
ewen | futarisIRCcloud: I'm trying doing a rebuild with 7e8f01bcfce7821940911e094b1528c73f292212 | 03:27 |
ewen | futarisIRCcloud: Which is about the latest date (2018-01-22) that I think I might have retested Mimas v2 | 03:27 |
ewen | futarisIRCcloud: (There's also a challenge that there's a Python 3.5 -> Python 3.6 transition in that time.) | 03:27 |
futarisIRCcloud | Yeah, I just get "LiteX SoC BIOS (" on that build too. I think it's related to the Python 3.6 change too. | 03:28 |
ewen | futarisIRCcloud: 7e8f01bcfce7821940911e094b1528c73f292212 didn't revive my non-working board either :-( | 03:29 |
cr1901_modern | lemme guess, mimas goes into the weeds after sending a few chars? | 03:29 |
futarisIRCcloud | weeds? | 03:29 |
cr1901_modern | crashes* | 03:29 |
ewen | cr1901_modern: In my case I get no obvious output at all :-( | 03:29 |
mithro | ewen: which PIC firmware are you running? | 03:30 |
ewen | cr1901_modern: But yes, crashes seems plausible. Any ideas? | 03:30 |
futarisIRCcloud | With the older build, yes. With newer builds, nothing. | 03:30 |
ewen | mithro: How can I check that? | 03:30 |
mithro | Not sure - jimmo knows | 03:30 |
ewen | mithro: Ah, you mean serial loader firmware. Just the default that shipped with it. | 03:30 |
cr1901_modern | ewen: Make sure the integrated_ram_size has the first 12 bits cleared | 03:30 |
ewen | cr1901_modern: Where do I check that? | 03:31 |
cr1901_modern | we dealt with this issue last year and I couldn't figure out why it crashed | 03:31 |
cr1901_modern | https://github.com/timvideos/litex-buildenv/blob/master/targets/mimasv2/base.py#L199 | 03:31 |
mithro | bblr - dinner | 03:31 |
tpb | Title: litex-buildenv/base.py at master · timvideos/litex-buildenv · GitHub (at github.com) | 03:31 |
cr1901_modern | Aaand it already is | 03:31 |
cr1901_modern | Wonder if something else regressed... mimasv2 worked fine last I tried. | 03:32 |
mithro | The following line is what is needed if you have different pic firmware running -> https://github.com/timvideos/litex-buildenv/blob/master/targets/mimasv2/base.py#L200 | 03:32 |
tpb | Title: litex-buildenv/base.py at master · timvideos/litex-buildenv · GitHub (at github.com) | 03:32 |
ewen | cr1901_modern: Yeah, Mimas v2 definitely worked for me the week before LCA at hackfest. | 03:32 |
ewen | cr1901_modern: Just unsure *exactly* what version worked.... | 03:33 |
cr1901_modern | ewen: While I couldn't figure out why the firmware crashed last year, my stopgap was to raise the amount of RAM. | 03:33 |
cr1901_modern | ewen: This isn't unique to mimas either. I've seen it also happen with tinyfpga and mercury as well (though in those cases I had a custom lm32_config) | 03:34 |
futarisIRCcloud | I had Mimasv2 working sometime in December too. | 03:34 |
ewen | cr1901_modern: You think the gateware is okay and it's crashing in the firmware/BIOS? | 03:35 |
cr1901_modern | ewen: I don't know. My guess is the gateware miscompiled, tbh. I couldn't duplicate the issues I had last year in simulation. | 03:35 |
cr1901_modern | ewen: Try 0928c16. I'll test my own locally later | 03:41 |
futarisIRCcloud | Changing integrated_sram_size from 0x4000 to 0x8000 stops any output from happening, on ddd71f41 | 03:41 |
cr1901_modern | Try commit hash 0928c16 of litex-buildenv* | 03:42 |
cr1901_modern | According to my reflog that _should_ work? | 03:42 |
ewen | cr1901_modern: 1987531c9dda7068f2f1640da2555733e8357544 (merged 2018-01-16) didn't work with clean rebuild. | 03:43 |
ewen | cr1901_modern: It's feeling like it's tooling/buildenv related somehow. | 03:43 |
cr1901_modern | ewen: Well 0928c16 was on the 14th of Jan :) | 03:44 |
ewen | cr1901_modern: Okay, I'll try that next. | 03:45 |
ewen | IIRC there were a bunch of compiler updates as well as the Python 3.5 -> 3.6 transition that happened. So possibly that's related. (I haven't, yet, been doing full download-env.sh on each one.) | 03:46 |
futarisIRCcloud | Me either. | 03:46 |
cr1901_modern | Well Python 3.6 support is indirectly my responsibility, since I added that feature to Migen :P | 03:47 |
cr1901_modern | But the things I fixed shouldn't have had that sort of effect (source: I had to modify 3.5 to give equivalent behavior to 3.6 and LiteX got those changes in December) | 03:48 |
ewen | futarisIRCcloud: cr1901_modern: mithro: It appears if I do "make image-flash" on 1987531c9dda7068f2f1640da2555733e8357544 it does work. | 03:50 |
ewen | (But "make gateware-flash" + "make firmware-load" didn't work.) | 03:50 |
ewen | (The difference being that "image-flash" flashes a combined blob of gateware + firmware + application) | 03:52 |
ewen | On that "make image-flash" version, I can then do "make firmware-connect" and it'll serial load MicroPython successfully. | 03:52 |
cr1901_modern | ewen: That's good to know, and yes you do need the combined image. | 03:53 |
ewen | I'm going to try rebuilding with timvideos application instead, and flashing that. | 03:53 |
cr1901_modern | ewen: I don't actually use the Makefile to upload the firmware b/c my mimasv2 board is remote (thus I use a special script to upload) | 03:53 |
ewen | cr1901_modern: "make gateware-flash" + "make firmware-load" definitely worked previously, but maybe due to what had been flashed before? | 03:53 |
cr1901_modern | ewen: It's certainly probable. Also, IIRC, unless mithro changed it, the application itself also contains a copy of the BIOS | 03:54 |
cr1901_modern | So that copy might've been executing as well at the wrong addr or some other fun mismatch | 03:54 |
futarisIRCcloud | Just synthesising 1987531c9dda7068f2f1640da2555733e8357544 now. | 03:55 |
ewen | mithro: Does "make gateware-flash" also include the firmware/BIOS? Or just gateware definition? | 03:57 |
ewen | (I'm wondering if my instructions are maybe wrong, and it worked for me previously as I'd flashed something else that *did* have the BIOS in it...) | 03:57 |
futarisIRCcloud | Yep. image-flash with 1987531c9dda7068f2f1640da2555733e8357544 works. | 04:00 |
ewen | futarisIRCcloud: So sounding like my instructions are wrong / reliant on side effects of previous use of board. | 04:00 |
cr1901_modern | if memory serves, image-flash should run mkimage.py w/ gateware, bios, and application, and then invoke MimasV2Config.py? | 04:01 |
futarisIRCcloud | ewen: Possibly. Trying again on HEAD. | 04:01 |
ewen | cr1901_modern: Yes, that sounds right. "make image-flash" is supposed to be gateware + bios + application in one, loaded via MimasV2Config.py | 04:04 |
ewen | FTR, if I "image-flash" with timevideos H2U firmware, I can "make firmware-load" it into MicroPython, as expected. | 04:09 |
ewen | futarisIRCcloud: I'm also about to try going back to HEAD. | 04:09 |
futarisIRCcloud | ewen: 8528a1926987459a72e2770389652493f612e8b5 works with "make image-flash" | 04:10 |
ewen | futarisIRCcloud: Great. I'm about to try d11f5b85e7a962b3b3e55aaee70a693159f59957 which AFAICT is latest in github timvideos/litex-buildenv | 04:11 |
futarisIRCcloud | Whoops. I mean d11f5b85e7a962b3b3e55aaee70a693159f59957 works. | 04:11 |
ewen | futarisIRCcloud: Great. I'll test it here. And if so, I'll reword the Mimas v2 bit of the blog post to make it clear you have to do "make image-flash" once, and then can test later MicroPython builds with "make firmware-load" serialboot. | 04:12 |
futarisIRCcloud | https://usercontent.irccloud-cdn.com/file/lsgnaLqs/d11f5b85e7a962b3b3e55aaee70a693159f59957.png | 04:13 |
ewen | futarisIRCcloud: That's the timvideos H2U C firmware. I've also had that working in this test. | 04:13 |
futarisIRCcloud | I suppose I should test FuPY too. | 04:14 |
ewen | futarisIRCcloud: I've been testing FuPy, at least building with scripts/build-micropython.sh which builds the FuPy repository | 04:15 |
futarisIRCcloud | ewen: Uploading FuPy image-flash now. | 04:19 |
ewen | futarisIRCcloud: me too :-) | 04:19 |
ewen | Of note, arty gateware-load loads $(TARGET_ | 04:20 |
ewen | ... $(TARGET_BUILD_DIR)/gateware/top.bit | 04:20 |
ewen | mimasv2 gateware-flash loads $(GATEWARE_FILEBASE).bin | 04:21 |
ewen | which expands to $(TARGET_BUILD_DIR)/gateware/top.bin | 04:21 |
cr1901_modern | *.bit files should only be loaded via JTAG. For hdmi2usb I don't use them often | 04:22 |
ewen | cr1901_modern: Yeah, on Arty it's loading via OpenOCD. | 04:22 |
ewen | futarisIRCcloud: image-flash on latest appears to work. I'll start updating the blog post... | 04:22 |
cr1901_modern | ewen: Right, but you still have to write the firmware to flash, and as of right now AFAIK everything's written to the flash all at once | 04:23 |
futarisIRCcloud | ewen: Confirmed here too. | 04:24 |
cr1901_modern | (i.e. the gateware and the application firmware) | 04:24 |
futarisIRCcloud | https://usercontent.irccloud-cdn.com/file/CKyFZaAs/micropython-g7a4245d2.png | 04:24 |
cr1901_modern | That said I haven't looked at the Makefile that closely in a while lol | 04:24 |
ewen | cr1901_modern: I'm fairly sure that I've previously (last year) managed to write gateware + firmware + no application, and had that work. But possibly I was manually calling mkimage.py to achieve that. | 04:26 |
ewen | cr1901_modern: (And then assuming that "make gateware-flash" was doing that when retesting last month, when it seemed to work...) | 04:27 |
cr1901_modern | Well I could actually _look_ at the Makefile to check lol. Just a bit surprised that *.bit files are used at all, since litex relies on loading the application from flash (and there is a command at the h2u prompt to flash a new firmware) | 04:28 |
cr1901_modern | s/there is/will be/ | 04:28 |
*** cocaine- has joined #timvideos | 04:29 | |
futarisIRCcloud | Well, I've now got a video target running on mimasv2, so that's something. It crashes in the hdmi2usb firmware, though... | 04:30 |
ewen | cr1901_modern: Yeah, now I think about it I have a feeling I've been caught out previously with "make gateware-flash" being basically useless given it needs some firmware to get started. | 04:30 |
futarisIRCcloud | I don't think I've added s6 stuff correctly to the firmware. | 04:31 |
cr1901_modern | I've never tried the video target on mimas, so I can't comment :( | 04:31 |
futarisIRCcloud | cr1901_modern: I only wrote a video target today. ;) | 04:31 |
ewen | futarisIRCcloud: You've reached the bleeding edge then :-) | 04:32 |
cr1901_modern | oops... | 04:32 |
futarisIRCcloud | Going to see if I can get it working. :) If not I may end up just running pacman. | 04:32 |
futarisIRCcloud | http://langster1980.blogspot.com.au/2016/04/pacman-running-on-mimas-v2-fpga.html | 04:32 |
tpb | Title: The Answer is 42!!: PacMan running on the Mimas V2 FPGA Development Board (at langster1980.blogspot.com.au) | 04:32 |
ewen | futarisIRCcloud: http://ewen.mcneill.gen.nz/blog/entry/2018-01-17-fupy-fpga-micropython-on-mimas-v2-and-arty-a7/ updated. Can you have a quick look and see if the Mimas v2 section on "Loading the gateware and micropython onto the Numato Mimas v2" makes sense now? | 04:45 |
tpb | Title: FuPy (FPGA MicroPython) on Mimas v2 and Arty (at ewen.mcneill.gen.nz) | 04:45 |
ewen | futarisIRCcloud: ie, "make image-flash" except for quick tests of application. | 04:45 |
futarisIRCcloud | Looks good to me | 04:49 |
ewen | futarisIRCcloud: Thanks. I've just spotted a confusion around BIOS / Firmware which I'll fix. | 04:50 |
ewen | futarisIRCcloud: In this context BIOS is the boot loader, etc. And "firmware" is actually the application. | 04:50 |
futarisIRCcloud | Ok | 04:50 |
mithro | heyo, I'm back now | 04:57 |
ewen | mithro: Catch up is that my instructions were wrong. "make image-flash" is pretty much essential. "make gateware-flash" is not that useful for testing software builds.... (due to no BIOS) | 04:58 |
ewen | mithro: Blog post updated. | 04:58 |
ewen | mithro: meanwhile, it appears that if FIRMWARE=none the idea is that it'd build an image with no firmware (application), but other parts of Makefile fail when trying that. | 04:58 |
mithro | ewen: On the Mimas you need to do a flash because the BIOS is stored in spiflash | 04:58 |
ewen | FileNotFoundError: [Errno 2] No such file or directory: 'build/mimasv2_base_lm32//software/none/firmware.bin' | 04:59 |
mithro | ewen: Hrm - I was sure we had fixed that | 04:59 |
ewen | In python -m litex.soc.tools.mkmscimg -f build/mimasv2_base_lm32//software/none/firmware.bin -o build/mimasv2_base_lm32//software/none/firmware.fbi | 04:59 |
mithro | https://www.irccloud.com/pastebin/LcC1uhOd/ | 05:00 |
tpb | Title: Snippet | IRCCloud (at www.irccloud.com) | 05:00 |
ewen | mithro: Yeah, that's the exact bit that made me think it was fixed. | 05:00 |
ewen | mithro: But FIRMWARE=none make image-flash fails earlier in the dependencies. | 05:01 |
ewen | mithro: I *think* because the image file depends on $(FIRMWARE_FILEBASE).fbi even if there's going to be no firmware included... | 05:01 |
mithro | Yeah | 05:01 |
ewen | mithro: Let me try tweaking that... | 05:02 |
*** shorne has quit IRC | 05:03 | |
ewen | mithro: Loading file build/mimasv2_base_lm32//image-gateware+bios+none.bin... | 05:04 |
ewen | mithro: If it works, I'll create a pull request for the trivial change. | 05:04 |
mithro | Great! | 05:04 |
mithro | ewen: On the Arty we embed the BIOS inside the gateware | 05:05 |
mithro | so you can just do a gateware-load | 05:05 |
mithro | The MimasV2 is pretty much the only device which we don't have the bios embedded in the firmware | 05:06 |
cr1901_modern | Well smaller boards than mimasv2 could run fupy | 05:07 |
cr1901_modern | so it's still valuable to keep the option to put bios in flash | 05:07 |
ewen | mithro: Should we make the Mimas v2 "gateware-flash" flash the gateware+BIOS combined image? It seems to me that this issue has tripped me up 3 times before... | 05:08 |
mithro | cr1901_modern: Yes | 05:08 |
cr1901_modern | ewen: I like that idea as long as it's commented. | 05:08 |
mithro | cr1901_modern: All our images have the bios in flash -- just some also have it in the gateware too | 05:08 |
cr1901_modern | mithro: Oh right I was misremembering the details of "why do we have two copies of the bios". | 05:10 |
cr1901_modern | ^ewen: Btw, it is very possible to accidentally boot up the second copy of the BIOS by accident. I don't remember how offhand tho. | 05:11 |
cr1901_modern | Perhaps you were seeing that? | 05:11 |
cr1901_modern | Wait no, not on mimasv. I saw it on opsis* | 05:12 |
cr1901_modern | ignore | 05:12 |
mithro | We should put a check in the BIOS which makes sure it is working on the right gateware :-P | 05:12 |
cr1901_modern | Probably no harm done. Even with firmware upload from the H2U> prompt, only mimasv2 could update the BIOS for an intentional version mismatch. | 05:13 |
*** shorne has joined #timvideos | 05:14 | |
mithro | anyone know what "declare -s" is suppose to do in shell? | 05:14 |
ewen | mithro: No. declare doesn't seem to take "-s" in bash manpage. Some other shell? | 05:19 |
futarisIRCcloud | mithro: So it looks like I was generating the clocks at 10* for the arty VGA... | 05:31 |
futarisIRCcloud | https://github.com/timvideos/litex-buildenv/pull/20/commits/112ddbdf69ba1fb1e9de37304687ea06203c52e3#diff-66a6e00147360f6e8cdf86606bc53602R488 | 05:31 |
tpb | Title: arty VGA output WIP by futaris · Pull Request #20 · timvideos/litex-buildenv · GitHub (at github.com) | 05:31 |
mithro | futarisIRCcloud: That seems like an easy mistake to make | 05:32 |
futarisIRCcloud | Anyhow, on mimasv2 it looks to be stuck here: | 05:34 |
futarisIRCcloud | https://github.com/futaris/litex-buildenv/blob/master/firmware/processor.c#L554 | 05:34 |
tpb | Title: litex-buildenv/processor.c at master · futaris/litex-buildenv · GitHub (at github.com) | 05:34 |
futarisIRCcloud | Haven't checked on arty | 05:35 |
mithro | futarisIRCcloud: stuck in what way? | 05:35 |
futarisIRCcloud | mithro: Never exits that section. Probably in a while loop | 05:36 |
mithro | https://github.com/futaris/litex-buildenv/blob/master/firmware/processor.c#L456 | 05:37 |
tpb | Title: litex-buildenv/processor.c at master · futaris/litex-buildenv · GitHub (at github.com) | 05:37 |
futarisIRCcloud | mithro: That'd do it for mimasv2. ;) | 05:38 |
mithro | futarisIRCcloud: Maybe there should be a #warning in that ifdef path? | 05:38 |
futarisIRCcloud | Well it now boots on mimasv2 | 05:42 |
*** suhdood has joined #timvideos | 05:44 | |
futarisIRCcloud | https://www.irccloud.com/pastebin/SqR9dMPR/ | 05:57 |
tpb | Title: Snippet | IRCCloud (at www.irccloud.com) | 05:57 |
futaris[m] | Not sure that I'll get a chance to work on it again today. | 06:01 |
futarisIRCcloud | Didn't even use the oscilloscope or logic analyser today. | 06:02 |
ewen | futarisIRCcloud: "Debugging by thinking very hard" :-) | 06:03 |
ewen | futarisIRCcloud: mithro: I'm testing a Mimas v2 diversion of "make gateware-flash" to load gateware+BIOS. | 06:03 |
*** suhdood has quit IRC | 06:27 | |
ewen | futarisIRCcloud: mithro: https://github.com/timvideos/litex-buildenv/pull/24 with both fixes. Result is "make gateware-flash" on Mimas v2 works in a more useful way (and doesn't violate principle of least surprise). | 06:33 |
tpb | Title: Makefile: omit FIRMWARE.fbi dep if FIRMWARE=none by ewen-naos-nz · Pull Request #24 · timvideos/litex-buildenv · GitHub (at github.com) | 06:34 |
mithro | ewen: LGTM! | 06:41 |
ewen | mithro: Thanks! | 06:52 |
* ewen disappears off to Saturday evening... | 06:52 | |
*** ewen has quit IRC | 06:55 | |
*** rohitksingh has joined #timvideos | 07:43 | |
*** suhdood has joined #timvideos | 08:11 | |
*** Kripton has quit IRC | 08:21 | |
*** Kripton has joined #timvideos | 08:25 | |
*** rohitksingh has quit IRC | 08:25 | |
*** suhdood has quit IRC | 08:32 | |
*** futarisIRCcloud has quit IRC | 08:39 | |
*** futarisIRCcloud has joined #timvideos | 09:05 | |
*** rohitksingh has joined #timvideos | 09:49 | |
*** futarisIRCcloud has quit IRC | 11:14 | |
*** futarisIRCcloud has joined #timvideos | 12:11 | |
*** rohitksingh has quit IRC | 14:20 | |
*** futarisIRCcloud has quit IRC | 15:34 | |
*** MaZderMind has joined #timvideos | 16:13 | |
MaZderMind | *wink | 16:13 |
MaZderMind | been playing around with the 1920-modelines in the hdmi2usb firmware | 16:14 |
MaZderMind | did you have 1920@25 or 1920@30 running on the opsis board? | 16:14 |
MaZderMind | docs says it should be fast enough to do so but i don't seem to get any of the modelines working | 16:15 |
CarlFK | MaZderMind: foggy memory says "yes, but currently we can only do 5 or 10 fps" | 16:15 |
MaZderMind | the pixelclock of 1080p25 is actually lower then 720p50 | 16:21 |
MaZderMind | so speed should not be the problem | 16:21 |
MaZderMind | i think i might just miscalculated the timings | 16:21 |
MaZderMind | (code here: https://github.com/timvideos/HDMI2USB-litex-firmware/compare/master...MaZderMind:modeline-1920x1080-at-25-and-24?expand=1) | 16:22 |
tpb | Title: Comparing timvideos:master...MaZderMind:modeline-1920x1080-at-25-and-24 · timvideos/HDMI2USB-litex-firmware · GitHub (at github.com) | 16:22 |
CarlFK | does vocto have and tests ... im trying to send an image in and out of the Opsis and see if what comes out is expected | 16:23 |
MaZderMind | what do you mean by "have and tests"? | 16:29 |
CarlFK | do you have some code that compares 2 images and returns a pass/fail | 16:31 |
CarlFK | oh.. /and/any | 16:31 |
MaZderMind | ah, no, voctomix has no integration tests like that | 16:33 |
MaZderMind | but there were some in the gst-switch repository | 16:33 |
CarlFK | oh yeah - thanks | 16:35 |
MaZderMind | can't find them | 16:35 |
MaZderMind | it's quite long ago :) | 16:35 |
MaZderMind | oh dear, three years OO | 16:35 |
CarlFK | bah. bunch of c code :p | 16:38 |
MaZderMind | i'll see if i can check the timing wirh a scope | 17:20 |
MaZderMind | the firmware for the hdmi2usb is quite crashy, isn't it? ie. with wringly decoded characters on the uart or incorrectly formatted modelines | 17:20 |
CarlFK | it is solid for 720p production - not surprised that other things aren't solid | 17:25 |
CarlFK | characters on the uart - sounds like the bug if you send chars too fast it drops them? | 17:26 |
*** suhdood has joined #timvideos | 17:40 | |
CarlFK[m] | mithro (IRC): there are hdmi2usb builds for both Atlys and Opsis on this rev: https://github.com/timvideos/HDMI2USB-firmware-prebuilt/tree/master/archive/master/v0.0.4-122-gbc7feb5 | 17:42 |
tpb | Title: HDMI2USB-firmware-prebuilt/archive/master/v0.0.4-122-gbc7feb5 at master · timvideos/HDMI2USB-firmware-prebuilt · GitHub (at github.com) | 17:42 |
CarlFK[m] | mithro (IRC): there are 3 builds after that, no hdmi2usb for either Atlys or Opsis | 17:43 |
CarlFK[m] | mithro (IRC): is this anything I should bother pointing out, or do we just wait for another rev and hope it builds? | 17:44 |
*** suhdood has quit IRC | 17:47 | |
*** suhdood has joined #timvideos | 17:47 | |
*** suhdood has joined #timvideos | 17:49 | |
*** suhdood has quit IRC | 18:05 | |
mithro | CarlFK[m]: yes - check what happened on travis | 18:22 |
mithro | CarlFK[m]: https://github.com/timvideos/HDMI2USB-firmware-prebuilt/tree/master/archive/master/v0.0.4-144-gd11f5b8/atlys/hdmi2usb/lm32 | 18:23 |
tpb | Title: HDMI2USB-firmware-prebuilt/archive/master/v0.0.4-144-gd11f5b8/atlys/hdmi2usb/lm32 at master · timvideos/HDMI2USB-firmware-prebuilt · GitHub (at github.com) | 18:23 |
mithro | CarlFK[m]: https://github.com/timvideos/HDMI2USB-firmware-prebuilt/tree/master/archive/master/v0.0.4-144-gd11f5b8/opsis/hdmi2usb/lm32 | 18:24 |
tpb | Title: HDMI2USB-firmware-prebuilt/archive/master/v0.0.4-144-gd11f5b8/opsis/hdmi2usb/lm32 at master · timvideos/HDMI2USB-firmware-prebuilt · GitHub (at github.com) | 18:24 |
mithro | MaZderMind: Yes we should be able to do 1080p25 or 1080p30 on the IO pins -- however nobody tests with that frequently so it is likely broken | 18:24 |
CarlFK[m] | mithro (IRC): where do I see travis logs for the ones that didn't build? | 18:53 |
mithro | CarlFK[m]: https://travis-ci.org/timvideos/HDMI2USB-litex-firmware/branches and https://travis-ci.org/timvideos/HDMI2USB-litex-firmware/builds | 18:54 |
CarlFK[m] | mithro (IRC): NameError: name 'clk_polarity' is not defined | 19:00 |
mithro | CarlFK[m]: Yeah - that looks like the build was actually broken | 19:01 |
CarlFK[m] | im guessing that has been fixed? | 19:01 |
mithro | CarlFK[m]: check the latest builds | 19:05 |
CarlFK[m] | mithro (IRC): um.. I have about 10 min till I need to run, so I am ignoring that... | 19:06 |
CarlFK[m] | mithro (IRC): hdmi2usb-mode-switch -v --flash-image image-gateware+bios+firmware.v0.0.4-144-gd11f5b8.atlys.hdmi2usb.lm32.bin | 19:07 |
CarlFK[m] | (0x1818... | 19:07 |
CarlFK[m] | AssertionError: serial mode only valid on the opsis. | 19:07 |
CarlFK[m] | any hints on how to get the atlys to behave ? | 19:08 |
mithro | CarlFK[m]: The serial mode **is** only valid on the opsis? | 19:09 |
CarlFK[m] | mithro (IRC): right - so I can't use that trick to get the atlys unstuck | 19:10 |
mithro | CarlFK[m]: yes | 19:10 |
CarlFK[m] | mithro (IRC): power cycle seemed to fix it. | 19:12 |
CarlFK[m] | mithro (IRC): flashed image-gateware+bios+firmware.v0.0.4-144-gd11f5b8.atlys.hdmi2usb.lm32.bin - now term programs (flterm, tio) connect, but I don't get any chars. | 19:32 |
mithro | CarlFK[m]: which serial port are you connecting too? | 19:32 |
CarlFK[m] | out of time now, I can look more in 5 or so hours. | 19:32 |
CarlFK[m] | juser@cnt3:~/temp$ flterm --port /dev/ttyVIZ0 | 19:32 |
CarlFK[m] | [FLTERM] Starting... | 19:32 |
mithro | Okay | 19:34 |
CarlFK[m] | im off - see ya | 19:42 |
*** CarlFK has quit IRC | 19:42 | |
MaZderMind | mithro: thank you. I'll try my best to fix it *reads up on his hdmi specs* – lot's of hidden complexity here | 21:26 |
*** danielki has quit IRC | 21:40 | |
*** bunnie has quit IRC | 21:40 | |
*** froztbyte has quit IRC | 21:40 | |
*** juliusb has quit IRC | 21:40 | |
*** olasd has quit IRC | 21:40 | |
*** xfxf has quit IRC | 21:40 | |
*** deeprave has quit IRC | 21:41 | |
*** mithro has quit IRC | 21:41 | |
*** Ishan_Bansal has quit IRC | 21:41 | |
*** cyrozap has quit IRC | 21:41 | |
*** mithro has joined #timvideos | 21:45 | |
*** deeprave has joined #timvideos | 21:45 | |
*** Ishan_Bansal has joined #timvideos | 21:45 | |
*** cyrozap has joined #timvideos | 21:45 | |
*** kornbluth.freenode.net sets mode: +o mithro | 21:45 | |
*** futaris[m] has quit IRC | 21:48 | |
*** olasd has joined #timvideos | 21:48 | |
*** xfxf has joined #timvideos | 21:48 | |
*** danielki has joined #timvideos | 21:48 | |
*** bunnie has joined #timvideos | 21:48 | |
*** froztbyte has joined #timvideos | 21:48 | |
*** juliusb has joined #timvideos | 21:48 | |
*** nbags[m] has quit IRC | 21:48 | |
*** ducky[m] has quit IRC | 21:48 | |
*** CarlFK[m] has quit IRC | 21:49 | |
*** jea[m] has quit IRC | 21:49 | |
*** micolous[m] has quit IRC | 21:49 | |
mithro | MaZderMind: what are you seeing happen? | 22:01 |
*** micolous[m] has joined #timvideos | 23:11 | |
*** CarlFK[m] has joined #timvideos | 23:36 | |
*** nbags[m] has joined #timvideos | 23:36 | |
*** futaris[m] has joined #timvideos | 23:36 | |
*** jea[m] has joined #timvideos | 23:36 | |
*** ducky[m] has joined #timvideos | 23:36 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!