cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #openFPGALoader
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #openFPGALoader
cr1901 has quit [Read error: Connection reset by peer]
cr1901 has joined #openFPGALoader
cr1901 has quit [Remote host closed the connection]
cr1901 has joined #openFPGALoader
GuanYung has joined #openFPGALoader
<GuanYung>
Hi all, I bump to this tool when I search for the FPGA bitstream programming. I would like to ask how do I add bitsream programming support to a new FPGA ?
* trabucayre
REALLY has to improve documentation :-/
<GuanYung>
No worry. You are really doing super awesome work to open source your project
<GuanYung>
Another quick question in my mind..
<GuanYung>
openFPGALoader -b arty arty_bitstream.bit # Loading in SRAM
<GuanYung>
Assuming the hardware are setup correctly, with this command, we will load the bitstream to SRAM
<GuanYung>
I am curious how the program knows the address of memory?
<GuanYung>
Looking at the code, it seems like I need to write a vendor specific parser to parse the header of the bitstream information? and write them to certain memory address?
<trabucayre>
for SRAM there is no memory address: the bitstream contains configuration for all memory
<trabucayre>
but SRAM isn't BRAM nor external RAM :)
<GuanYung>
Is this the industry standard for bitstream programming? I mean the statement `bitstream contains configuration for all memory`
<trabucayre>
memory is primitive configuration, routing, etc.