Thursday, 2018-09-20

*** tpb has joined #timvideos00:00
*** CarlFK has joined #timvideos00:19
*** ChanServ sets mode: +v CarlFK00:19
*** mauz555 has joined #timvideos01:18
*** meldron4 has joined #timvideos01:36
*** meldron4 has quit IRC01:41
CarlFKhttps://github.com/timvideos/litex-buildenv/wiki/Xilinx-Vivado-screen-shots03:50
tpbTitle: Xilinx Vivado screen shots · timvideos/litex-buildenv Wiki · GitHub (at github.com)03:50
*** rohitksingh_work has joined #timvideos03:54
*** futarisIRCcloud has joined #timvideos04:09
*** Sc00bz has quit IRC05:30
*** CarlFK has quit IRC05:35
cr1901_modernmithro: http://ix.io/1n5B nextpnr can't find the correct version of libboost_python05:49
cr1901_modernFrom the build log output, it doesn't even look like yosys or nextpnr ran at all05:51
cr1901_modernI know in a previous build you created a dummy gateware. Is it possible it got cached and the build step was skipped?05:52
cr1901_moderngateware build step*05:52
*** sc00bz has joined #timvideos05:59
cr1901_modernOkay, making a whole new clean conda env fixes this06:01
cr1901_modernMaybe conda decided not to upgrade my existing libboost_python06:03
mithrocr1901_modern: looks like it ran to me06:04
mithrohttps://travis-ci.org/timvideos/litex-buildenv/jobs/43077072606:04
cr1901_modernmithro: Yes I stand corrected, it did run. But I was expecting all the nextpnr [Info] messages06:05
cr1901_modernlooks like you redirected them all to a file06:05
cr1901_modernI would like to know why there's a libboost mismatch tho w/ my current repo06:06
mithrocr1901_modern: the Travis wrapper turns them into dots06:06
cr1901_moderns/repo/env/06:06
mithroOtherwise with Xilinx tools you end up with the log output being too much and Travis killing your build06:07
*** Guest90018 has joined #timvideos06:08
*** Guest90018 has quit IRC06:13
cr1901_modernmithro: Yea for some inexplicable reason, conda has decided in my existing env that nextpnr is tied to "libboost: 1.65.1-habcd387_4" (wrong version).06:14
cr1901_modernBut when I create a fresh conda env, that dependency becomes: "libboost: 1.67.0-h46d08c1_4"06:14
cr1901_modernObviously, "just nuke the old environment" is a solution. But I'm wondering if you know of a more gentle solution. Like is there a way to refresh how conda decides which version of a package to use (since my existing metadata appears to be stale)?06:15
mithroconda install nextpnr06:16
*** sc00bz has quit IRC06:16
cr1901_modernThat doesn't update the deps06:16
cr1901_modernin fact, even if I uninstall libboost, and install nextpnr, it'll still use libboost 1.65.106:17
*** CarlFK has joined #timvideos06:30
*** ChanServ sets mode: +v CarlFK06:30
*** sc00bz has joined #timvideos06:56
*** Teeed9 has joined #timvideos07:16
*** Teeed9 has quit IRC07:19
cr1901_modernmithro: Solution for now is to make sure libboost is installed _before_ nextpnr07:21
cr1901_modernotherwise nextpnr will pull in the wrong version07:21
cr1901_modernjust in case this bites someone else07:21
xobsThat sounds so helpful.07:22
* cr1901_modern invokes poe's law07:22
cr1901_modernbeing serious or facetious :P?07:22
xobslibboost is magical, and I don't understand it.  I'm having a similar problem installing Coriolis on 16.04 -- it seems confused as to whether it's linking against libboost_python2 or libboost_python3, and I've never figured out how to tell it what's what.07:23
xobsSo genuine helpful.07:23
mithrocr1901_modern: need to check why conda isn't seeing the deps correctly07:23
cr1901_modernmithro: I wouldn't know how to do that07:25
cr1901_modernmithro: It's also worth noting that this does _not_ happen in a fresh environment07:25
cr1901_modernmithro: Btw, we should prob add tinyprog to litex-buildenv :)07:26
cr1901_modern(it works w/ the makefile, I've tried it)07:26
mithroHrm, I was sure I had added that...07:28
mithroBut it seems to have gotten lost...07:29
cr1901_modernxobs: Fair :D, was just wondering. B/c rereading my solution, it sounded pretty vague07:34
xobscr1901_modern: I wonder if it isn't any better on 18.04.  I say that because despite all of the other problems I've experienced under 18.04, libboost just worked there unlike in 16.04.07:35
cr1901_modernI wouldn't know, I don't upgrade Ubuntu until LTS ends :P07:36
cr1901_modernWhich reminds me... I still have 14.04 on my dying netbook07:36
cr1901_modernwhich I somehow managed to revive today07:36
xobsIt's what's installed on Windows.  You can pick from Debian, 18.04, 16.04, or some Suse flavour.07:37
cr1901_modernOh, yea I use 7. No plans to upgrade until I'm forcefully coerced into doing it.07:37
xobsIt's kind of a weird mindset.  They're more-or-less a chroot.07:38
cr1901_modernOh _now_ the deps have been updated when I install nextpnr by itself07:44
cr1901_modernwell problem solved I guess07:45
cr1901_modernmithro: Let me know when tinyprog is avail please?07:50
cr1901_modern(from conda)07:50
*** jonh29 has joined #timvideos07:53
*** jonh29 has quit IRC07:57
cr1901_modernewen: What's the purpose of running "make firmware-cmd" after ./scripts/download-prebuilt.sh? How does rebuilding the firmware affect prebuilt gateware and vice versa?08:04
cr1901_modernmithro: This line never runs, does it? https://github.com/timvideos/litex-buildenv/blob/47afea2b3a444ec6d1ad9334e364e6361fd8c6bc/Makefile#L19208:05
tpbTitle: litex-buildenv/Makefile at 47afea2b3a444ec6d1ad9334e364e6361fd8c6bc · timvideos/litex-buildenv · GitHub (at github.com)08:05
cr1901_modernSee: https://github.com/timvideos/litex-buildenv/blob/47afea2b3a444ec6d1ad9334e364e6361fd8c6bc/Makefile#L11908:05
tpbTitle: litex-buildenv/Makefile at 47afea2b3a444ec6d1ad9334e364e6361fd8c6bc · timvideos/litex-buildenv · GitHub (at github.com)08:05
cr1901_modernmithro: Wait ignore08:05
*** spruit1112 has joined #timvideos08:07
cr1901_modernmithro: What is the purpose of args.override_firmware to make.py?08:07
cr1901_modernWhen I set FIRMWARE=micropython, the stub firmware gets built anyway08:07
cr1901_modern(stub being default firmware for devices like tinyfpga)08:08
*** Neg127 has joined #timvideos08:19
*** Neg127 has quit IRC08:22
cr1901_modern"/home/william/Projects/litex-buildenv/build/conda/bin/../lib/gcc/lm32-elf/5.4.0/../../../../lm32-elf/bin/ld:litex.ld:19: warning: memory region `main_ram' not declared" Yes, thank you. I would've liked to know that _before_ I crashed08:23
cr1901_modernobviously we'll need a separate linker script for running from flash08:24
cr1901_modernfor now I'm just gonna use the current one08:24
*** futarisIRCcloud has quit IRC08:48
*** sc00bz has quit IRC08:51
*** sc00bz has joined #timvideos09:10
*** sc00bz has joined #timvideos09:16
cr1901_modernmithro: For micropython to work on tinyfpga, we're gonna have to change the startup code in libbase09:24
cr1901_modernspecifically, micropython has a .data section you can't opt out of- i.e. initialized memory. This is stored on the flash. Normally, we run firmware from DRAM, and we don't have to worry about manually initializing this code.09:25
cr1901_modernThe bootloader in the BIOS will take care of this when copying the whole program (including the .data section) to DRAM09:26
cr1901_modernWith tinyfpga, we don't have this luxury09:26
cr1901_modernMy suggestion is to provide an alternate startup code in libbase for each arch that copies the .data section from flash to RAM (for targets not executing from DRAM)09:28
cr1901_moderncc: _florent_, have any issues w/ this? I understand RISC-V forces the use of a .data section, but Idk if it conflicts with my idea.09:28
*** CarlFK has quit IRC09:40
*** MB_Adriaan has joined #timvideos11:24
*** MB_Adriaan has quit IRC11:27
*** cRaNnK5 has joined #timvideos11:55
*** cRaNnK5 has quit IRC11:56
*** rohitksingh_wor1 has joined #timvideos12:40
*** rohitksingh_work has quit IRC12:41
*** rohitksingh_wor1 has quit IRC12:43
*** CarlFK has joined #timvideos12:55
*** ChanServ sets mode: +v CarlFK12:55
*** rohitksingh has joined #timvideos13:44
CarlFKxobs: did you want something tested on 18.04?  I got a box...13:55
xobsCarlFK: thanks, I'll keep that in mind. For now I'm using the WSL Ubuntu 18.04 install, which I'm hoping is "good enough".13:56
CarlFKk - I have like 4-10 boxes that are used for recording now and then, but most of the time they sit around doing nothing.  the recording setup is all automated, so I don't mind destroying them between shows13:58
xobsThat's very good to know.13:58
xobsNice that you have the reimaging process well defined, too.13:59
CarlFKpxe boot the installer, preseed the os install, ansible all the rest.14:01
*** thaytan has quit IRC14:05
*** thaytan has joined #timvideos14:06
*** ChanServ sets mode: +v thaytan14:06
CarlFK"The Crickit is powered by seesaw, our I2C-to-whatever bridge firmware."  https://www.adafruit.com/product/309314:11
tpbTitle: Adafruit CRICKIT for Circuit Playground Express ID: 3093 - $29.95 : Adafruit Industries, Unique & fun DIY electronics and kits (at www.adafruit.com)14:11
CarlFKI2C-to-whatever bridge  :p14:11
*** rohitksingh has quit IRC14:50
*** rohitksingh has joined #timvideos14:54
*** rohitksingh has quit IRC15:08
*** mauz555 has joined #timvideos15:45
*** mauz555 has quit IRC16:37
*** waldo323 has quit IRC16:55
*** waldo323 has joined #timvideos16:57
*** waldo323 has quit IRC17:03
*** waldo323 has joined #timvideos17:10
*** tac-tics has joined #timvideos17:16
*** L0j1k4 has joined #timvideos17:21
*** L0j1k4 has quit IRC17:23
*** Kripton has quit IRC17:43
*** mauz555 has joined #timvideos17:56
*** Kripton has joined #timvideos17:56
*** john_doe_jr5 has joined #timvideos19:06
*** mauz555 has quit IRC19:11
*** rme16 has joined #timvideos19:12
*** dcousens5 has joined #timvideos20:33
*** dcousens5 has quit IRC20:37
*** Throttled0 has joined #timvideos21:43
*** Throttled0 has quit IRC21:51
*** nitdega4 has joined #timvideos22:15
*** g11 has joined #timvideos22:26
*** g11 has quit IRC22:31
*** wildermind has joined #timvideos22:42
*** mauz555 has joined #timvideos23:56

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!