azonenberg changed the topic of ##openfpga to: Open source tools for FPGAs, CPLDs, etc. Silicon RE, bitfile RE, synthesis, place-and-route, and JTAG are all on topic. Channel logs: https://libera.irclog.whitequark.org/~h~openfpga
eightdot has quit [Ping timeout: 264 seconds]
eightdot has joined ##openfpga
nelgau_ has joined ##openfpga
nelgau_ has quit [Remote host closed the connection]
nelgau has quit [Read error: Connection reset by peer]
nelgau has joined ##openfpga
Degi has quit [Ping timeout: 260 seconds]
Degi has joined ##openfpga
jn has quit [Ping timeout: 256 seconds]
jn has joined ##openfpga
thaytan has quit [Ping timeout: 264 seconds]
enok has quit [Remote host closed the connection]
enok has joined ##openfpga
emeb_mac has joined ##openfpga
nelgau has quit [Read error: Connection reset by peer]
nelgau has joined ##openfpga
Hammdist has quit [Quit: Client closed]
Hammdist has joined ##openfpga
<Hammdist>
is there any support in open source for loading a program onto the SoC of a zynq fpga? and, preferably, being able to communicate between the soc and the fabric ...
V has quit [Ping timeout: 255 seconds]
<Hammdist>
ok so I'm finding it's complicated. if I understand correctly, on the SoC parts, one does not simply program the bitfile. Instead, the SoC boots first and programs the fabric, so everything must be embedded in a boot.bin file which can be generated using bootgen, which is open source
<Hammdist>
still I'm skeptical that all these stages are entirely free of closed-source tools, would be good if someone could confirm one way or another
V has joined ##openfpga
<mwk>
in a pinch, the zynq TRM does contain enough information to just generate a boot.bin yourself
<mwk>
as in, I brought up the SoC with nothing but arm-gcc at one point, and used amaranth+vivado for the FPGA side; had ARM-FPGA communication working, too
<mwk>
it did involve initializing a lot of registers myself though, and I didn't even try bringing up the DDR which would presumably be a bunch of Fun
<Hammdist>
ah nice that's solid info, thanks. I do need arm-fpga communication, and I (hopefully) won't need DDR either
<Hammdist>
maybe with u-boot in there I can boot a minimal kernel that can do the communication I need and even have DDR