Friday, 2021-10-22

*** tpb <[email protected]> has joined #litex00:00
shenki_florent_: hey, I tried building the microwatt soc following the fixes you merged and I still don't see any signs of life on my arty00:14
shenki(i see blinking leds, but no signs of software running from the uart)00:14
shenkido you have any ideas?00:15
sajattack[m] 👀02:20
sajattack[m]linux-on-litex-xuantie wen?02:21
sajattack[m]I don't suppose this is very easy to get uboot onto but gosh darnit, I'm gonna compile it for acorn and see what happens02:22
*** mithro <[email protected]> has quit IRC (Ping timeout: 260 seconds)02:28
*** mithro <[email protected]> has joined #litex02:29
*** Degi_ <[email protected]> has joined #litex02:33
*** Degi <[email protected]> has quit IRC (Ping timeout: 258 seconds)02:33
*** Degi_ is now known as Degi02:33
sajattack[m]wow ok03:07
sajattack[m]vivado says it requires 673054 logic cells :(03:07
*** lexano <[email protected]> has quit IRC (Ping timeout: 260 seconds)04:16
*** lexano <[email protected]> has joined #litex04:23
*** TMM_ <[email protected]> has quit IRC (Quit: - Chat comfortably. Anywhere.)06:55
*** TMM_ <[email protected]> has joined #litex06:55
*** FabM <[email protected]> has joined #litex07:00
*** cr1901 <[email protected]:8d:8600:911:4167:ef6b:ec8f:a1fb> has quit IRC (Read error: Connection reset by peer)07:10
_florent_cr1901, tnt: Thanks for the Ice40fix, it has been merged.07:14
_florent_somlo: For openrisc, I tested the one from bootlin recently with litex_sim, you can probably use this one:
_florent_shenki: I've been able to use microwatt with litex_sim and also on arty with the recent changes07:17
_florent_shenki: litex_sim --cpu-type=microwatt --cpu-variant=standard+ghdl07:18
_florent_shenki: python3 litex_boards.targets.digilent_arty --cpu-type=microwatt --build --load07:18
_florent_^ this was probably what I tested07:18
_florent_with this toolchain (also from bootlin):
_florent_shenki: can you check if the simulation is working (requires installing the GHDL-synth plugin)?07:20
leonsDoes LiteX have a module for collecting/buffering a stream transaction with a size limit, such that it's guaranteed to be readable with valid == 1 over the whole transaction?07:31
leonsSpecifically, I'm upconverting a 32-bit stream to 64 bit for XGMII Ethernet and the stream through the Ethernet pipeline must never have valid == 0 in a transaction. So my naive solution, because I know that this stream is only a few bytes in size, is to collect a transaction entirely and then allow the consumer to read it in one go07:34
leonsAh, the moment you ask... PacketFIFO looks promising07:36
_florent_leons: yes I was going to suggest you this, that's the purpose of PacketFIFO07:38
leons_florent_: by the way, is there any progress in the Packetizer/Depacketizer side? Would it be possible to get the fixed version in first and then eventually rework the data qualifier? I've been using this version quite successfully without any issues for some time now, so it seems strictly better than the upstream version.07:44
*** ewen <[email protected]> has joined #litex07:46
_florent_leons: Sorry, too much things ongoing currently, I would be ok to merge the changes in litex/soc/interconnect/ but not the test. Could you do a PR with just the logic changes? I'll be able to merge it. We could discuss changing the approach for the test during the data qualifier rework.08:03
leonsOkay, though is there any specific reason why you wouldn't want the tests to be merged?08:03
_florent_Because 1) Without spending the time to fully understand it (which I don't have now) I lose the ability to maintain it 2) I'd also like to keep the previous test 3) We could maybe try to allow the new packet simulation classes to be used more widely but also need to discuss a bit.08:14
leonsOkay, that makes sense.08:15
_florent_But if you keep the previous test and rename yours to test_packet2, I'm OK to merge it now and eventually merge both tests together in the future.08:16
leonsI was asking whether there's some specific aspect I didn't cover (because I'm happy to further work on that) but it sounds like the concepts are good in general, just need to spend more time on it08:16
leonsI'm fine with splitting it out - no worries. I was just asking because developing the Packetizer/Depacketizer without tests is, at least in my experience, pretty insane 😀08:17
_florent_So if you update the PR, keeping the previous test_packet and renaming yours to test_packet2, I'll merge it.08:22
*** AndrewD <[email protected]> has joined #litex09:05
AndrewDI've switched my Nick from mc6808 to match my GitHub pull requests09:06
AndrewD_florent_: thanks for getting litespi and everything else together so xyloni builds with uartbone09:08
AndrewDI tried uartbone briefly today with no success. Did you get anywhere?09:09
AndrewDI wonder if we need to drop the clock a bit.09:10
AndrewDI started experimenting to support the v1 pll on T8 the other day but didn't get it completed09:12
_florent_AndrewD: python3 -m litex_boards.targets.efinix_xyloni_dev_kit --build --flash should now produce a working bitstream09:15
_florent_AndrewD: with updated LiteX to have
*** AndrewD <[email protected]> has quit IRC (Quit: Client closed)09:20
*** AndrewD <[email protected]> has joined #litex09:21
AndrewD_florent_: thanks for the email indicating you  got this working!09:22
AndrewDI checked IRC and posted before I noticed it.09:24
*** AndrewD <[email protected]> has quit IRC (Quit: Ping timeout (120 seconds))09:32
trabucayre_florent_: jtag proof of concept is done. Now I need a cleanup09:36
trabucayreI like T8 idcode: 0x0000000109:36
_florent_trabucayre: great!09:41
trabucayrelast step is a bridge to access flash through jtag :)09:42
_florent_The SPI Flash seems to always be connected to the FTDI directly on the Efinix dev kits, but this would be useful for custom boards yes09:46
trabucayrean006-configuring-trion-fpgas-v4.6.pdf p.1609:50
trabucayrethis mode allows to have something similar to xilinx, intel, ...09:51
trabucayreit's avoid to have two interfaces :)09:52
*** AndrewD <[email protected]> has joined #litex10:02
AndrewDtrabucayre: can jtag access spi flash on T8? There are some limitations on the v1 trion devices10:04
AndrewDBut I don't remember all the details from what I read early this week10:05
AndrewDI thought this was the reason they have direct spi connection on the T8 Dev board10:07
trabucayreto have access to jtag, you need to reset device with cs low...10:07
AndrewDBut I don't think T20 and higher required this10:07
trabucayreI need to check. But T20/T120 are to expensive...10:08
*** ewen <[email protected]> has quit IRC (Ping timeout: 258 seconds)10:09
AndrewDThe T20 in CSP package is not too bad, but still twice the cost of T810:09
trabucayreboards are expensive :)10:11
AndrewDI would definitely like to use T8 of we can though to keep cost under control10:11
AndrewDThe dev boards?10:11
AndrewDWe are going to do a simple T20 csp Dev board10:12
trabucayreok. Good to know10:13
AndrewDJust for internal use, but I might be able to build a few more10:13
trabucayreI have xyloni & fireant but nothing higher10:13
AndrewDBasically xyloni but with T20 is what I had in mind10:14
trabucayrelooks good10:14
AndrewDWill be useful in development so we can avoid premature optimisation10:15
*** AndrewD <[email protected]> has quit IRC (Ping timeout: 256 seconds)10:27
*** cr1901 <[email protected]:8d:8600:911:a870:7807:f9b0:ad06> has joined #litex10:31
somlo_florent_: thanks for the link! It provides or1k-buildroot-* and or1k-linux-*, but apparently litex insists on or1k-elf-* (and throws an error when all I have is the openrisc--musl toolchain you linked me to:
tpbTitle: $ rm -rf build/sim; litex/litex/tools/ --cpu-type mor1kxINFO:SoC: - (at
*** shorne <[email protected]> has quit IRC (Ping timeout: 268 seconds)12:03
*** shorne <[email protected]> has joined #litex12:05
_florent_somlo: I added *or1k-linux-* 3 days ago while testing this toolchain:
somlo_florent_: the error I'm getting is with the most current litex git master (including that commit); Maybe this might still have something to do with it: ?14:09
somlo_florent_: and if I comment that out, it starts to compile the bios, then errors out with a whole bunch of picolibc syntax errors:
tpbTitle: $ rm -rf build/sim; litex/litex/tools/ --cpu-type mor1kxINFO:SoC: - (at
somloso assuming we're both using the latest git master of everything, I wonder what else is different between your setup (which I assume worked for you) and mine (which crashes and burns, spectacularly, as shown in the paste) :)14:15
*** FabM <[email protected]/team/FabM> has quit IRC (Quit: Leaving)14:48
cr1901_florent_: I took a brief look at trying to migrate litex to meson. I think it's possible, but it would require some rearchitecting and not really appropriate for now. 14:56
cr1901Specifically, I think Builder() shouldn't directly generate any files except a meson cross file, and meson calls back into Builder() to generate the linker script, headers, etc.14:56
cr1901Would you be receptive to a rearchitecting like this in the medium term?14:56
cr1901The short version is that "meson wants to find everything in either your source or build dir", and litex violates this a lot :P.15:03
_florent_Thanks cr1901, sorry I would also need to have a closer look at meson to see the pros/cons to be able to answer. I will try to take a bit of time in the next weeks to look at it and be able to answer.16:27
*** futarisIRCcloud <[email protected]> has joined #litex17:33
nickoe_florent_: OK   (Re. the flashing of the flash)18:29
*** _franck_3 <[email protected]> has joined #litex18:46
*** _franck_ <[email protected]> has quit IRC (Ping timeout: 258 seconds)18:48
*** _franck_3 is now known as _franck_18:48
cr1901_florent_: I can still do a proof-of-concept/WIP PR if you want19:41
cr1901If you don't like it/decide it's not a direction worth going, you can close it :).19:42
*** futarisIRCcloud <[email protected]> has quit IRC (Quit: Connection closed for inactivity)19:42
_florent_cr1901: I'm not very confortable knowing you'll spend time on something without knowing it's the direction to go20:12
_florent_cr1901: so if you do it, just do a very quick proof-of-concept and don't spend too much time on it20:13
cr1901_florent_: Ack20:16
cr1901I'm gonna hold off then b/c I don't think it can be done quickly. The system we have works fine now. I just feel bad we need all of meson, make, and ninja lol20:17
*** TMM_ <[email protected]> has quit IRC (Quit: - Chat comfortably. Anywhere.)20:38
*** TMM_ <[email protected]> has joined #litex20:38
*** linear_cannon <[email protected]> has quit IRC (*.net *.split)21:31
*** tpw_rules <[email protected]> has quit IRC (*.net *.split)21:31
*** awordnot <[email protected]/awordnot> has quit IRC (*.net *.split)21:31
*** awordnot <[email protected]> has joined #litex21:31
*** tpw_rules <[email protected]> has joined #litex21:33
*** linear_cannon <[email protected]> has joined #litex21:36
*** ewen <[email protected]> has joined #litex22:51

Generated by 2.17.2 by Marius Gedminas - find it at!