tpb has quit [Remote host closed the connection]
tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow
tpb has joined #symbiflow
craigo has quit [Quit: Leaving]
craigo has quit [Quit: Leaving]
Raito_Bezarius has quit [Remote host closed the connection]
Raito_Bezarius has quit [Remote host closed the connection]
Raito_Bezarius has joined #symbiflow
Raito_Bezarius has joined #symbiflow
kgugala has joined #symbiflow
kgugala has joined #symbiflow
Degi_ has joined #symbiflow
Degi_ has joined #symbiflow
Degi has quit [Ping timeout: 276 seconds]
Degi has quit [Ping timeout: 276 seconds]
Degi_ is now known as Degi
Degi_ is now known as Degi
citypw has joined #symbiflow
citypw has joined #symbiflow
maartenBE has quit [Ping timeout: 245 seconds]
maartenBE has quit [Ping timeout: 245 seconds]
maartenBE has joined #symbiflow
maartenBE has joined #symbiflow
_whitelogger_ has quit [Remote host closed the connection]
_whitelogger_ has joined #symbiflow
_whitelogger_ has joined #symbiflow
citypw has quit [Ping timeout: 268 seconds]
citypw has quit [Ping timeout: 268 seconds]
kgugala_ has joined #symbiflow
kgugala_ has joined #symbiflow
kgugala has quit [Ping timeout: 264 seconds]
kgugala has quit [Ping timeout: 264 seconds]
kraiskil has joined #symbiflow
kraiskil has joined #symbiflow
kgugala_ has quit [Read error: Connection reset by peer]
kgugala_ has quit [Read error: Connection reset by peer]
kgugala has joined #symbiflow
kgugala has joined #symbiflow
kraiskil has quit [Ping timeout: 256 seconds]
kraiskil has quit [Ping timeout: 256 seconds]
kraiskil has joined #symbiflow
kraiskil has joined #symbiflow
kraiskil has quit [Ping timeout: 245 seconds]
kraiskil has quit [Ping timeout: 245 seconds]
citypw has joined #symbiflow
citypw has joined #symbiflow
citypw has quit [Ping timeout: 268 seconds]
citypw has quit [Ping timeout: 268 seconds]
Raito_Bezarius has quit [Ping timeout: 260 seconds]
Raito_Bezarius has quit [Ping timeout: 260 seconds]
kraiskil has joined #symbiflow
kraiskil has joined #symbiflow
phire has quit [*.net *.split]
phire has quit [*.net *.split]
phire has joined #symbiflow
phire has joined #symbiflow
kraiskil has quit [Ping timeout: 265 seconds]
kraiskil has quit [Ping timeout: 265 seconds]
<sf-slack> <nils.albartus> Following up on my question yesterday, we went hunting down the missing bits in the zedboard database. As suggested I tried to locate the tile / column with the help of the `tilegrid.json` . Here is what I did: ```{ unknown_bit = "0042001a_16_7", unknown_segment = "0x00420000", unknown_segbit = "26_519" }``` First we checked `INT_L` , since the base address matched. The given seg_bits are `26_519` (or rather
<sf-slack> <nils.albartus> Following up on my question yesterday, we went hunting down the missing bits in the zedboard database. As suggested I tried to locate the tile / column with the help of the `tilegrid.json` . Here is what I did: ```{ unknown_bit = "0042001a_16_7", unknown_segment = "0x00420000", unknown_segbit = "26_519" }``` First we checked `INT_L` , since the base address matched. The given seg_bits are `26_519` (or rather
<sf-slack> `26_07` ) which are not responsible for the tile anymore ((https://symbiflow.github.io/prjxray-db/zynq7/tile_int_l.html). so, this is not what we are looking for. is this correct so far? so we had a look at what else is starting at the baseaddr `0x00420000` and found `HCLK_IOI3_X1Y26` . looking at the database file `segbits_hclk_ioi3.db` we found a bunch of entries with segbits `26_XY` , but not `26_07` . So we currently
<sf-slack> `26_07` ) which are not responsible for the tile anymore ((https://symbiflow.github.io/prjxray-db/zynq7/tile_int_l.html). so, this is not what we are looking for. is this correct so far? so we had a look at what else is starting at the baseaddr `0x00420000` and found `HCLK_IOI3_X1Y26` . looking at the database file `segbits_hclk_ioi3.db` we found a bunch of entries with segbits `26_XY` , but not `26_07` . So we currently
<sf-slack> assume that the missing bits are related to `HCLK_IOI3` . Is our assumption correct this far? if our assumption is correct, what would the next step be? i guess we need to look at fuzzer `047-hclk-ioi-pips` ? any tips on how to go on from here?
<sf-slack> assume that the missing bits are related to `HCLK_IOI3` . Is our assumption correct this far? if our assumption is correct, what would the next step be? i guess we need to look at fuzzer `047-hclk-ioi-pips` ? any tips on how to go on from here?
<tpb> Title: X-Ray ZYNQ7 Database: INT_L (at symbiflow.github.io)
<tpb> Title: X-Ray ZYNQ7 Database: INT_L (at symbiflow.github.io)
citypw has joined #symbiflow
citypw has joined #symbiflow
<sf-slack> <acomodi> nils1994: So, I think that it is not the HCLK_IOI3 tile as that one is found at word offset == 50. In this case, your unknown bit is at word 16 (`0042001a_16_7` where `0042001a` is the base_address + frame in hex, 16 is the word in the frame, and 7 is the bit in the word)
<sf-slack> <acomodi> nils1994: So, I think that it is not the HCLK_IOI3 tile as that one is found at word offset == 50. In this case, your unknown bit is at word 16 (`0042001a_16_7` where `0042001a` is the base_address + frame in hex, 16 is the word in the frame, and 7 is the bit in the word)
<sf-slack> <acomodi> There are many different tiles found at that base address though, which include IOBs and IOIs
<sf-slack> <acomodi> There are many different tiles found at that base address though, which include IOBs and IOIs
<sf-slack> <acomodi> If I were to guess, those unknowns might be related to those tiles
<sf-slack> <acomodi> If I were to guess, those unknowns might be related to those tiles
citypw has quit [Ping timeout: 268 seconds]
citypw has quit [Ping timeout: 268 seconds]
umarcor has joined #symbiflow
umarcor has joined #symbiflow
<sf-slack> <nils.albartus> mh okay. i guess than i am quite lost on how to start…
<sf-slack> <nils.albartus> mh okay. i guess than i am quite lost on how to start…
<sf-slack> <acomodi> So, the idea here is to be able first to identify what is causing these unknown bits. We know that they are in the area of the IOB/IOI/INT_L tiles in the bottom left clock region.
<sf-slack> <acomodi> So, the idea here is to be able first to identify what is causing these unknown bits. We know that they are in the area of the IOB/IOI/INT_L tiles in the bottom left clock region.
<sf-slack> <acomodi> Given that the same unknown bits appear in different words (as per in the snippet above) may be a hint that these are corresponding to a configuration parameter (this may be untrue, but it is just a hint)
<sf-slack> <acomodi> Given that the same unknown bits appear in different words (as per in the snippet above) may be a hint that these are corresponding to a configuration parameter (this may be untrue, but it is just a hint)
rj has joined #symbiflow
rj has joined #symbiflow
<litghost> If that is near the IO column, it could just be IO standard stuff
<litghost> If that is near the IO column, it could just be IO standard stuff
<litghost> What IO standards are you using?
<litghost> What IO standards are you using?
krogozinski has quit [Ping timeout: 264 seconds]
krogozinski has quit [Ping timeout: 264 seconds]
krogozinski has joined #symbiflow
krogozinski has joined #symbiflow
shivampotdar has quit [Ping timeout: 265 seconds]
shivampotdar has quit [Ping timeout: 265 seconds]
duck2 has quit [Quit: Ping timeout (120 seconds)]
duck2 has quit [Quit: Ping timeout (120 seconds)]
duck2 has joined #symbiflow
duck2 has joined #symbiflow
b33p[m] has quit [Ping timeout: 265 seconds]
b33p[m] has quit [Ping timeout: 265 seconds]
citypw has joined #symbiflow
citypw has joined #symbiflow
fevv8[m] has quit [Ping timeout: 264 seconds]
fevv8[m] has quit [Ping timeout: 264 seconds]
unrznbl[m] has quit [Ping timeout: 240 seconds]
unrznbl[m] has quit [Ping timeout: 240 seconds]
xobs has quit [Ping timeout: 268 seconds]
xobs has quit [Ping timeout: 268 seconds]
promach3 has quit [Ping timeout: 258 seconds]
promach3 has quit [Ping timeout: 258 seconds]
lopsided98 has quit [Ping timeout: 256 seconds]
lopsided98 has quit [Ping timeout: 256 seconds]
lopsided98 has joined #symbiflow
lopsided98 has joined #symbiflow
shivampotdar has joined #symbiflow
shivampotdar has joined #symbiflow
unrznbl[m] has joined #symbiflow
unrznbl[m] has joined #symbiflow
b33p[m] has joined #symbiflow
b33p[m] has joined #symbiflow
xobs has joined #symbiflow
xobs has joined #symbiflow
promach3 has joined #symbiflow
promach3 has joined #symbiflow
fevv8[m] has joined #symbiflow
fevv8[m] has joined #symbiflow
<_whitenotifier-4> [sv-tests] tgorochowik opened issue #1411: Kokoro doesn't always start - https://git.io/JmjDi
<_whitenotifier-4> [sv-tests] tgorochowik opened issue #1411: Kokoro doesn't always start - https://git.io/JmjDi
citypw has quit [Ping timeout: 268 seconds]
citypw has quit [Ping timeout: 268 seconds]
yeti has quit [Quit: WeeChat 3.1]
yeti has quit [Quit: WeeChat 3.1]
yeti has joined #symbiflow
yeti has joined #symbiflow
<mithro> umarcor: thoughts -^
<mithro> umarcor: thoughts -^
<umarcor> until now we have avoided debug symbols (not added them explicitly, unless created by default) because the main use case is CI. size matters because it has direct impact on startup and traffic.
<umarcor> until now we have avoided debug symbols (not added them explicitly, unless created by default) because the main use case is CI. size matters because it has direct impact on startup and traffic.
<umarcor> however, we have full control of the build procedure for each tool, and we do already publish some 'pkg' images which contain artifacts. therefore, we might "easily" generate build symbols and distribute them there or elsewhere.
<umarcor> however, we have full control of the build procedure for each tool, and we do already publish some 'pkg' images which contain artifacts. therefore, we might "easily" generate build symbols and distribute them there or elsewhere.
<umarcor> is debuginfod just a tool or also a service? i.e. do we need to setup our own debuginfod server?
<umarcor> is debuginfod just a tool or also a service? i.e. do we need to setup our own debuginfod server?
<mithro> umarcor: Well there are two seperate things, running debuginfod for the FPGA tooling
<mithro> umarcor: Well there are two seperate things, running debuginfod for the FPGA tooling
<mithro> umarcor: Creating something like debuginfod for FPGA bitstreams
<mithro> umarcor: Creating something like debuginfod for FPGA bitstreams
<umarcor> oh, sorry. I completely overlooked the "for FPGA bitstreams" part!
<umarcor> oh, sorry. I completely overlooked the "for FPGA bitstreams" part!
kraiskil has joined #symbiflow
kraiskil has joined #symbiflow
<mithro> umarcor: debuginfod is a protocol / server which takes basically locals debug symbols and then publishes them as a HTTP server
<mithro> umarcor: debuginfod is a protocol / server which takes basically locals debug symbols and then publishes them as a HTTP server
<mithro> umarcor: So it would be good if the FPGA tooling was build with "split debug symbols" and then the split debug symbols are saved somewhere and then published in a debuginfod compatible form.
<mithro> umarcor: So it would be good if the FPGA tooling was build with "split debug symbols" and then the split debug symbols are saved somewhere and then published in a debuginfod compatible form.
gromero has joined #symbiflow
gromero has joined #symbiflow
<tpb> Title: Sphinx aafigure 0.5 documentation (at aafigure.readthedocs.io)
<tpb> Title: Sphinx aafigure 0.5 documentation (at aafigure.readthedocs.io)
<sf-slack> <mgielda> yeah, it's cool. pondered id for diagrams until I had to redraw one ;)
<sf-slack> <mgielda> yeah, it's cool. pondered id for diagrams until I had to redraw one ;)
<sf-slack> <mgielda> *it
<sf-slack> <mgielda> *it
kgugala_ has joined #symbiflow
kgugala_ has joined #symbiflow
kgugala has quit [Ping timeout: 245 seconds]
kgugala has quit [Ping timeout: 245 seconds]
rj has quit [Ping timeout: 268 seconds]
rj has quit [Ping timeout: 268 seconds]
rj has joined #symbiflow
rj has joined #symbiflow
ktemkin is now known as gsg-bridge
ktemkin is now known as gsg-bridge
gsg-bridge has quit []
gsg-bridge has quit []
gsg-bridge has joined #symbiflow
gsg-bridge has joined #symbiflow
gsg-bridge is now known as ktemkin
gsg-bridge is now known as ktemkin
ktemkin has quit [Client Quit]
ktemkin has quit [Client Quit]
ktemkin has joined #symbiflow
ktemkin has joined #symbiflow
<mithro> litghost: I just discovered https://github.com/olsner/jobclient
<mithro> litghost: I just discovered https://github.com/olsner/jobclient
<litghost> Huh, might be handy
<litghost> Huh, might be handy
kraiskil has quit [Ping timeout: 260 seconds]
kraiskil has quit [Ping timeout: 260 seconds]
<mithro> Also, rust implementation if anyone is interested -- https://docs.rs/jobserver/0.1.21/jobserver/
<mithro> Also, rust implementation if anyone is interested -- https://docs.rs/jobserver/0.1.21/jobserver/
<tpb> Title: jobserver - Rust (at docs.rs)
<tpb> Title: jobserver - Rust (at docs.rs)
<umarcor> mgielda: https://asciiflow.com is quite nice for text representation of diagrams
<umarcor> mgielda: https://asciiflow.com is quite nice for text representation of diagrams
<tpb> Title: ASCIIFlow (at asciiflow.com)
<tpb> Title: ASCIIFlow (at asciiflow.com)
Raito_Bezarius has joined #symbiflow
Raito_Bezarius has joined #symbiflow