Wednesday, 2020-01-08

*** tpb has joined #timvideos00:00
*** TheAssassin has quit IRC00:04
-_whitenotifier-5- [yosys] pull[bot] opened pull request #212: [pull] master from YosysHQ:master - https://git.io/JveWH00:13
-_whitenotifier-5- [yosys] pull[bot] closed pull request #212: [pull] master from YosysHQ:master - https://git.io/JveWH00:13
*** TheAssassin has joined #timvideos00:20
-_whitenotifier-5- [yosys] pull[bot] opened pull request #213: [pull] master from YosysHQ:master - https://git.io/JvelF01:13
-_whitenotifier-5- [yosys] pull[bot] closed pull request #213: [pull] master from YosysHQ:master - https://git.io/JvelF01:13
*** ewen has joined #timvideos02:11
ewenmithro: Looks like TinyFPGA BX / MicroPython serial/boot doesn't work after 3a9127d08d8d0be9a68331bd71bf43fc216dbb2602:39
ewenmithro: That commit and the next one don't build due to API conflicts (that's a Litex submodule update set).02:40
ewenmithro: Commits that do build after that don't show Litex BIOS or anything on serial02:42
ewen(Looks like there are 71 commits after that.)02:43
ewenmithro: e4c6ffa96f6ac4048181363f9a9be2dbea4b19c3 which is the next one that builds for me, doesn't work (no BIOS/serial console messages).02:55
ewenFTR da7488c2ab5e3d496ba4ecb5e482458302fb1c15 is the last working commit that builds, and gives BIOS/serial.02:59
ewenSo my assumption is there's something in the (huge) litex update which broke TinyFPGA BX, and wasn't sufficiently compensated.03:00
-_whitenotifier-5- [litex-buildenv] ewenmcneill opened issue #282: TinyFPGA BX: BIOS/Micropython does not start - https://git.io/JveBM03:24
mithroewen: We discovered that at 36C304:04
mithroewen: https://github.com/timvideos/litex-buildenv/issues/27704:05
tpbTitle: Ice40 HX8K EVB issues · Issue #277 · timvideos/litex-buildenv · GitHub (at github.com)04:05
-_whitenotifier-5- [litex-buildenv] mithro commented on issue #282: TinyFPGA BX: BIOS/Micropython does not start - https://git.io/JveR804:12
-_whitenotifier-5- [litex-buildenv] ewenmcneill commented on issue #282: TinyFPGA BX: BIOS/Micropython does not start - https://git.io/JveRu04:24
-_whitenotifier-5- [litex-buildenv] ewenmcneill commented on issue #282: TinyFPGA BX: BIOS/Micropython does not start - https://git.io/JveRH04:43
ewenmithro: Thanks for the pointer.  Curiously it seems like the iceBreaker *does* work, so my guess is there's something changed in the iceBreaker gateware, but not in the other two (and/or some relevant hardware differences).04:44
mithroewen: You have an icebreaker?04:45
mithroewen: Do you have a Fomu?04:46
ewenWith me I have: TinyFPGA BX, iceBreaker, Fomu EVT2/3, Fomu PVT, Arty, and Mimas V204:50
ewen(I've had MicroPython running on TinyFPGA BX / iceBreaker / Arty / Mimas V2 before; not on the Fomus.)04:50
ewenFWIW, iceBreaker changes in litex-buildenv seem very similar to the TinyFPGA BX ones (memory region type).  So maybe one of them is/was accidentally working before.04:51
mithroDoes the arty work?04:52
mithroJust working on a talk for tomorrow04:53
ewenI'll give the Arty a try.04:53
mithroewen: I think it is two things -- the SPI Flash controller and the new memory region stuff04:53
mithroewen: The Arty has the BIOS embedded in the gateware rather than executing directly from SPI flash04:54
ewenmithro: Yes, the changes I can see are for the memory regions.04:56
ewenmithro: It's possible that the SPI Flash controller is related to the issue.04:56
ewenmithro: Seems like my Arty build is broken (Vivado runs start_gui).04:56
ewen(Looks like it's almost exactly two years since I installed Vivado, which is possibly related.)04:57
ewen(Xilinx license web page claims the licenses still exist, and seem to be the same as what I've got on my system.  So I'm unclear what's triggering start_gui when I run "make gateware" :-( )05:12
mithro:-/05:20
mithroewen: By the end of this year, you won't need to use Vivado any more :-P05:20
ewen:-)05:22
ewenmithro: I'm not having much luck figuring out how vivado is being invoked, let alone what's causing start_gui to be the thing invoked.05:22
mithroewen: Did you see - https://github.com/xobs/wishbone-utils/issues/3 ?05:23
tpbTitle: Support bash tab completion · Issue #3 · xobs/wishbone-utils · GitHub (at github.com)05:23
mithroewen: And also have you done the Fomu workshop recently? workshop.fomu.im ?05:23
ewenI've done bits of that Fomu workshop recently (with PVT), but not all of it05:28
ewenwishbone-tool tab completion looks handy :-)05:29
ewen(Unfortunately it seems like it's impossible to build gateware for arty with detached head -- version_data.sh git command fails -- so I can't even test that.)05:29
mithroewen: Look at build/XXXX/gateware/top.sh for the thing which runs vivado...05:33
mithroewen: https://workshop.fomu.im got a facelift and a bunch of improvement for CCC05:34
mithroewen: There is also a new rust stuff05:40
mithroewen: And the new bootloader is *much* faster05:41
ewenmithro: Yes, I came back to the Fomu workshop when you were doing the 36c3 draft, so I did some of your version and some of xobs's version (mostly where examples were missing due to formatting issues).05:58
ewenmithro: Thanks for the gateware/top.sh hint, I'll see if I can figure out what it's trying to run at that point.05:58
xobsAlso handy if you want to manually run things to avoid a lengthy rebuild.05:59
ewenmithro: Looks like build_top.sh runs "vivado -mode batch -source top.tcl".... so for some reason that batch build isn't running in batch mode.06:01
ewenmithro: Aha.  I think that was self inflicted.  I had a /usr/local/bin/vivado wrapper script, which didn't have "$@" in the "real vivado" it ran....06:13
ewen(... so it was always running vivado without arguments.  I'm assuming PATH changes meant that wasn't previously being hit via the litex-buildenv scripts...)06:15
deepravehowdy, i'm trying to flash an opsis board following the wiki, but getting:06:28
deepraveInfo : JTAG tap: xc6s.tap tap/device found: 0x44028093 (mfg: 0x049 (Xilinx), part: 0x4028, ver: 0x4)06:28
deepraveError: Unknown flash device (ID 0x00ffffff)06:28
deepraveDo I need to change jumpers on the board? I recall having to do so at LCA2017 (?) but I think that was for the other board type.06:28
ewenmithro: FYI, MicroPython on arty *does* work (CPU=lm32, latest litex-buildenv)06:32
ewenmithro: See also above from deeprave, which I'm assumimg is AV Team install issues.06:32
deepraveyeah, actually troubleshooting, but will need to do a load/test cycle to figure the issues out06:34
mithrodeeprave: There is a page somewhere about that06:34
mithrodeeprave: Basically if it has never been flashed before it will need a special process for the first time to flash06:34
deepravethe 93) boards tested so far had previously been working06:35
deepraves/93)/(3)/06:35
-_whitenotifier-5- [litex-buildenv] ewenmcneill commented on issue #282: TinyFPGA BX: BIOS/Micropython does not start - https://git.io/JveEU06:37
ewenhttps://github.com/timvideos/HDMI2USB/wiki/Flashing-Firmware06:37
tpbTitle: Flashing Firmware · timvideos/HDMI2USB Wiki · GitHub (at github.com)06:37
ewenmithro: Is that the page you were thinking of? ^^^06:37
ewenCarl confirms those are the instructions.   And with Carl's help we have the HDMI2USB flashing working (at least on one device)06:51
deepraveso what CPU do I need to set for these (LCA) opsis boxes?07:03
deepravei think that's the issue now, need to build the correct image07:03
ewenCPU default now seems to be vexriscv (RISC-V).  I'm not sure if that's ever been tested with HDMI2USB.07:11
ewenThe older CPU default was either lm32 or or1k, I forget which.  (export CPU=.... is the override)07:12
tumbleweedwe've used lm32 in the past, yes07:13
ewendeeprave: Based on above, I think try building with "export CPU=lm32" first, and see if that helps.07:15
tumbleweedalso, master has been broken for around a year: https://github.com/timvideos/HDMI2USB-litex-firmware/issues/46507:15
tpbTitle: encoder broken: JPEG file: starts with 0x15 0x0c · Issue #465 · timvideos/HDMI2USB-litex-firmware · GitHub (at github.com)07:15
ewentumbleweed: Thanks for the link.  I think that's more subtly broken than where deeprave is currently stuck, so trying CPU=lm32 is likely to get closer to previously working config.07:16
deepraveCPU=lm32 (tried that first) but the enter script complains about not having a supporting build toolchain07:17
deepraveso lm32 is the correct one for the spartan6?07:18
ewendeeprave: You'll need to do "export CPU=lm32; scripts/download-env.sh" to get it to download the right tools.07:18
deepraveah, kk07:19
ewendeeprave: The download-env.sh script tries to just download what it thinks is needed (thus makes the same CPU assumptions...)07:19
ewendeeprave: I've also been able to build HDMI2USB from source now (helped I had most of the FPGA tools already installed), so I'll try the same thing.07:19
deepraveawesome the script is downloading the correct toolchain now07:21
mithroI'm heading to bed07:45
mithroewen: Wish I could be doing micropython hacking with you -- but should have some exciting things to share at LCA07:47
ewenmithro: It's all good.  It sounds like your week is for a good cause :-)07:47
ewenSleep well!07:47
-_whitenotifier-5- [litex-buildenv] mithro commented on issue #281: Conda Yosys package update - https://git.io/JveuG07:48
-_whitenotifier-5- [litex-buildenv] mmicko commented on issue #281: Conda Yosys package update - https://git.io/JveuC07:51
-_whitenotifier-5- [litex-buildenv] mithro commented on issue #281: Conda Yosys package update - https://git.io/JveuW07:51
mithroThanks! Good night everyone!07:53
ewendeeprave: I've got as far as the point you got stuck now (JTAG flashing not working).  I have a feeling that's udev rule related.07:56
deepraveyep,  Unknown flash device (ID 0x00ffffff)07:57
ewenIn my case: Error: Unknown flash device (ID 0x00818181)07:57
ewenBut it feels like "not getting valid data, making wild assumptions" :-)07:57
deepraveyeah string of jtag issues. but i did find that the hdmi2usb-mode-switch may be the problem07:58
deepraveinstalled separately via apt i just managed to upload a built image07:59
deepravethat is outside enter-env.sh, just used the apt installed version with hdmi2usb-mode-switch -v --flash-image <path to image>08:01
ewendeeprave: FWIW, I'm on Ubuntu 18.04 LTS (Bionic).  So it's possibly not the same hdmi2usb-mode-switch.08:01
ewen(I'm also wondering if I'm going to have to reboot to get udev rules loaded properly...)08:01
mithroThe unknown flash ID issue is caused by the default image turning on QSPI mode to the flash08:02
ewenIs there a work around?08:02
mithroYes08:02
ewen?08:02
mithroAnd there is totally a document somewhere which tells you how08:03
ewen:-)08:03
ewenI suggest you go to sleep.  We'll try to find it :-)08:03
mithrohttps://github.com/timvideos/HDMI2USB-mode-switch/issues/2408:04
tpbTitle: Detect "Error: Unknown flash device (ID 0x00ffffff)" on Digilent Atlys · Issue #24 · timvideos/HDMI2USB-mode-switch · GitHub (at github.com)08:04
mithroReally really going to bed now08:06
ewenThanks!08:07
ewenFTR, that "Unkown Flash Device" is for an Digilent Atlys; the board I'm having trouble with is a Numato Opsis.  (My guess is that JTAG to the USB just isn't detecting it, possibly due to udev rules not being applied.)08:09
*** ewen has quit IRC08:28
*** ewen has joined #timvideos08:33
*** ewen has quit IRC08:43
*** TimGremalm has quit IRC08:59
*** TimGremalm has joined #timvideos09:00
futarisIRCcloudI didn't see all this activity till now...10:29
futarisIRCcloudSo just to re-iterate, default image turning QSPI mode to the flash, is one of the causes of the issue.10:32
*** mauz555 has joined #timvideos11:19
*** mauz555 has quit IRC11:31
mithro@CarlFK[m]: we have finally captured pdp7's attention! https://twitter.com/pdp7/status/1214641397850103808?s=2012:44
*** SpaceCoaster has joined #timvideos13:16
-_whitenotifier-5- [HDMI2USB-fx2-firmware] jedrzejboczar opened pull request #50: libfx2-migration: serial examples - https://git.io/JveKo14:10
-_whitenotifier-5- [HDMI2USB-fx2-firmware] todo[bot] commented on pull request #50: libfx2-migration: serial examples - https://git.io/JveKK14:10
-_whitenotifier-5- [HDMI2USB-fx2-firmware] todo[bot] commented on pull request #50: libfx2-migration: serial examples - https://git.io/JveK614:10
-_whitenotifier-5- [HDMI2USB-fx2-firmware] todo[bot] commented on pull request #50: libfx2-migration: serial examples - https://git.io/JveKP14:10
-_whitenotifier-5- [HDMI2USB-fx2-firmware] jedrzejboczar opened pull request #51: libfx2-migration: audio example - https://git.io/Jve6014:34
-_whitenotifier-5- [HDMI2USB-fx2-firmware] todo[bot] commented on pull request #51: libfx2-migration: audio example - https://git.io/Jve6E14:34
-_whitenotifier-5- [HDMI2USB-fx2-firmware] todo[bot] commented on pull request #51: libfx2-migration: audio example - https://git.io/Jve6u14:34
-_whitenotifier-5- [HDMI2USB-fx2-firmware] jedrzejboczar opened pull request #52: WIP: libfx2-migration: video example - https://git.io/Jve6V14:39
-_whitenotifier-5- [HDMI2USB-fx2-firmware] todo[bot] commented on pull request #52: WIP: libfx2-migration: video example - https://git.io/Jve6w14:39
-_whitenotifier-5- [HDMI2USB-fx2-firmware] todo[bot] commented on pull request #50: libfx2-migration: serial examples - https://git.io/JveiG15:05
-_whitenotifier-5- [litex-buildenv] mithro opened issue #283: Yosys + nextpnr should have versions in scripts/settings.sh - https://git.io/JveiB15:09
mithroCarlFK[m]: https://github.com/antmicro/litex-buildenv/pull/1/files#diff-61fc1605dc515710f3394cbad285426b15:23
tpbTitle: [WIP] Renode CI by mateusz-holenko · Pull Request #1 · antmicro/litex-buildenv · GitHub (at github.com)15:23
mithroCarlFK[m]: automated testing!15:23
-_whitenotifier-5- [HDMI2USB-fx2-firmware] todo[bot] commented on pull request #51: libfx2-migration: audio example - https://git.io/JvePJ15:29
-_whitenotifier-5- [HDMI2USB-fx2-firmware] todo[bot] commented on pull request #51: libfx2-migration: audio example - https://git.io/JvePP15:42
-_whitenotifier-5- [litex-buildenv] mithro commented on issue #281: Conda Yosys package update - https://git.io/JveXl16:04
-_whitenotifier-5- [HDMI2USB-fx2-firmware] mithro commented on pull request #47: WIP: Migration from fx2lib to whitequark's libfx2 - https://git.io/Jve1z16:35
-_whitenotifier-5- [HDMI2USB-fx2-firmware] mithro closed pull request #47: WIP: Migration from fx2lib to whitequark's libfx2 - https://git.io/Jeryb16:35
*** rvense has joined #timvideos17:46
-_whitenotifier-5- [litex-buildenv] mmicko closed issue #281: Conda Yosys package update - https://git.io/JejIL18:56
-_whitenotifier-5- [litex-buildenv] mmicko commented on issue #281: Conda Yosys package update - https://git.io/JveS618:56
-_whitenotifier-5- [litex-buildenv] mmicko commented on issue #281: Conda Yosys package update - https://git.io/Jve9e19:10
futarisIRCcloudRenode CI - Yay. Automated testing.20:07
-_whitenotifier-5- [litex-buildenv] mithro commented on issue #281: Conda Yosys package update - https://git.io/JveHg20:09
-_whitenotifier-5- [litex-buildenv] niklasnisbeth commented on issue #277: Ice40 HX8K EVB issues - https://git.io/JveFL23:07
-_whitenotifier-5- [litex-buildenv] niklasnisbeth commented on issue #282: TinyFPGA BX: BIOS/Micropython does not start - https://git.io/JveFg23:20
*** ewen has joined #timvideos23:55
ewenfutarisIRCcloud: Re Opsis flashing "default image turning QSPI mode to the flash" is there a known work around to that?23:56
ewenfutarisIRCcloud: Eg, "default image" of what bit?  Are there build flags that would avoid that.23:57

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