| *** tpb has joined #litex | 00:00 | |
| *** femto has joined #litex | 00:43 | |
| femto | mithro: fwiw, tinyprog writes, but the final read to compare the data is always cut off | 00:45 |
|---|---|---|
| mithro | femto: Are you using a vm? | 00:53 |
| *** femto has quit IRC | 01:08 | |
| *** femto has joined #litex | 01:18 | |
| *** femto has quit IRC | 01:29 | |
| *** femto has joined #litex | 04:24 | |
| *** futarisIRCcloud has joined #litex | 08:42 | |
| futarisIRCcloud | https://opensource.googleblog.com/2019/05/google-fosters-open-source-hardware.html | 08:54 |
| tpb | Title: Google fosters the open source hardware community | Google Open Source Blog (at opensource.googleblog.com) | 08:54 |
| keesj | How, nice.. I was literaly writing notes down on the why of open silicon! thanks | 09:04 |
| keesj | https://www.linuxfoundation.org/press-release/2019/03/linux-foundation-to-host-chips-alliance-project-to-propel-industry-innovation-through-open-source-cpu-chip-and-soc-design/ | 09:05 |
| keesj | (linked from the other atricle) | 09:05 |
| keesj | Google is planning to contribute a Universal Verification Methodology (UVM)-based instruction stream generator environment for RISC-V cores. | 09:05 |
| keesj | sounds .. cool/ scarry / AI?? | 09:05 |
| femto | Anyone else run into the gateware flash size issue on the TinyFPGA BX board? https://github.com/timvideos/litex-buildenv/issues/137 | 10:51 |
| tpb | Title: make gateware-flash "FAILED!" on TinyFPGA BX · Issue #137 · timvideos/litex-buildenv · GitHub (at github.com) | 10:51 |
| *** femto has left #litex | 10:57 | |
| *** futarisIRCcloud has quit IRC | 11:01 | |
| keesj | I am wondering why I see 2 times python -m litex.soc.tools.mkmscimg -f firmware.bin -o firmware.fbi | 11:35 |
| keesj | a.. gone | 11:35 |
| somlo | _florent__: with the LiteDRAM generator, assuming one specifies an AXI user port, at what physical address is the DRAM actually mapped (e.g., on nexys4ddr)? | 13:43 |
| _florent__ | somlo: in this case there is no mapping, you are just accessing the DRAM | 14:24 |
| somlo | so the DRAM essentially starts at AXI address 0x0000_0000 | 14:28 |
| somlo | if the AXI master wanted to write/read to/from it, that is, via the AXI user port | 14:29 |
| somlo | which would mean that a simple offset inserted into the master/slave AXI link *should* take care of translating that to whatever region the CPU thinks its RAM is mapped to, internally | 14:30 |
| somlo | feel free to kick me if I'm spouting nonsense :) | 14:30 |
| somlo | s/CPU/master/ | 14:31 |
| _florent__ | yes that's it | 14:43 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!