tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow
gsmecher has quit [Ping timeout: 272 seconds]
andrewb1999 has joined #symbiflow
andrewb1999 has quit [Quit: Konversation terminated!]
Degi has quit [Ping timeout: 260 seconds]
Degi has joined #symbiflow
Bertl_oO is now known as Bertl_zZ
OmniMancer1 has joined #symbiflow
OmniMancer has quit [Ping timeout: 246 seconds]
reces has joined #symbiflow
<reces> Hey guys
<reces> I have a question about base addresses that I find in the tilegrid files
<reces> To my understunding those are frame addresses that should have the format shown in table 5-24 of Xilinx UG470
<reces> And I do can find them when I am looking at the frame organisation produced by the x-ray tools
<reces> What I dont understand is how I can see them in the raw bitstream or maybe how they are derived from it.
<reces> I think it has to do something with self incrementation but I am not sure how, Could someone give some aid towards that ?
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
kraiskil has joined #symbiflow
kraiskil has quit [Ping timeout: 256 seconds]
Bertl_zZ is now known as Bertl
adjtm has joined #symbiflow
noopwafel has quit [Ping timeout: 256 seconds]
noopwafel has joined #symbiflow
adjtm_ has quit [Ping timeout: 256 seconds]
<daveshah> reces: You should see the frame address writes if you enable PERFRAMECRC
<daveshah> tcl set_property bitstream.general.perframecrc yes
<reces> daveshah Thanks I will try that. But how can I see that without it ?
<daveshah> You can't because of the auto-incrementation you noticed
<reces> The needed information should be there since the tool is calculating it
<daveshah> Oh, you want to calculate it from prjxray?
<reces> oh so it starts counting frames after it sees the type2 package starting ?
<daveshah> I think that is what the yaml file is for
<daveshah> Yes it autoincrements after every 93 data words or however long a frame is
<reces> Project xray has it calculated in both bitstream to frames and fasm to frames
<reces> cool
<reces> what I am not sure of is how it changes block type
<reces> In the type 2 packet is both `CLB, I/O, CLK (000), block RAM content
adjtm_ has joined #symbiflow
adjtm has quit [Ping timeout: 256 seconds]
reces has quit [Remote host closed the connection]
kraiskil has joined #symbiflow
<litghost> The block type is encoded in the upper bits of the address, per 5-24
gsmecher has joined #symbiflow
shadtorrie has joined #symbiflow
citypw has joined #symbiflow
kraiskil has quit [Ping timeout: 264 seconds]
citypw has quit [Ping timeout: 240 seconds]
kraiskil has joined #symbiflow
reces has joined #symbiflow
shadtorrie has quit [Remote host closed the connection]
kraiskil has quit [Ping timeout: 272 seconds]
reces has quit [Remote host closed the connection]
reces has joined #symbiflow
reces has quit [Remote host closed the connection]
az0re has quit [Remote host closed the connection]
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #symbiflow
kraiskil has joined #symbiflow
smkz is now known as __builtin_trap
futarisIRCcloud has joined #symbiflow
az0re has joined #symbiflow
kraiskil has quit [Ping timeout: 256 seconds]
lopsided98 has quit [Remote host closed the connection]
lopsided98 has joined #symbiflow