sb0 changed the topic of #m-labs to: https://m-labs.hk :: Mattermost https://chat.m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
<Astro-_> right now I'm fighting with zc706 qspi transfers leaking into each other, though I stop the peripheral in between.
<Astro-_> flash chip timing for SPI CS is at 5ns which is way faster than my println!() call...
Stormwind_mobile has quit [Remote host closed the connection]
airwoodix7 has joined #m-labs
airwoodix has quit [Ping timeout: 265 seconds]
airwoodix7 is now known as airwoodix
_whitelogger has joined #m-labs
Stormwind_mobile has joined #m-labs
<mtrbot-ml> [mattermost] <sb10q> @hartytp @weidazhang does WRPLL still work if we put the transceiver PLL into the loop? i.e. use TXOUTCLK as "main DCXO input" for the DDMTD core
<mtrbot-ml> [mattermost] <sb10q> the advantage of doing this is the stupid xilinx divider non-determinism is dealt with without additional components. the disadvantage is I don't know if the loop is still low-noise or even stable
<mtrbot-ml> [mattermost] <sb10q> otherwise we have to take the auxiliary output of IBUFDS_GTE as "main DCXO input", and then add something that compares IBUFDS_GTE vs. TXOUTCLK and uses the TXPI to fix the divider issue
<mtrbot-ml> [mattermost] <sb10q> (that's for the "no external FFs" case, on kasli2 and sayma rtm)
<mtrbot-ml> [mattermost] <sb10q> the TXPI is rather annoying in multi-channel mode
<mtrbot-ml> [mattermost] <sb10q> well, on the other hand the TXPI solution has the additional advantages that 1. we can use it to tune S/H timing in the DRTIO RXSynchronizer 2. it is required for the external FF solution anyway
<mtrbot-ml> [mattermost] <sb10q> and 3. the GTP PLL craps out, sometimes irreversibly until FPGA is reconfigured it would seem, when enabled and not clocked properly - which would make wrpll experimentation tedious
proteusguy has quit [Ping timeout: 268 seconds]
electronic_eel has quit [Ping timeout: 265 seconds]
electronic_eel has joined #m-labs
proteusguy has joined #m-labs
electronic_eel has quit [Ping timeout: 265 seconds]
electronic_eel_ has joined #m-labs
_whitelogger has joined #m-labs
electronic_eel_ is now known as electronic_eel
_whitelogger has joined #m-labs
Getorix_ has joined #m-labs
Getorix has quit [Ping timeout: 245 seconds]
mauz555 has joined #m-labs
Getorix has joined #m-labs
Getorix_ has quit [Ping timeout: 268 seconds]
mauz555 has quit []
Sarayan has quit [Remote host closed the connection]
<mtrbot-ml> [mattermost] <sb10q> well the si549 helper clock (at least as received by FPGAs) is flimsy, both on amc and rtm ...
Stormwind_mobile has quit [Ping timeout: 276 seconds]
Stormwind_mobile has joined #m-labs
X-Scale has quit [Ping timeout: 276 seconds]
X-Scale has joined #m-labs
X-Scale has quit [Ping timeout: 265 seconds]
X-Scale` has joined #m-labs
X-Scale` is now known as X-Scale
mumptai has joined #m-labs
<ZirconiumX> So, I downloaded Quartus Pro (Cyclone 10GX support is free)
<ZirconiumX> They changed
<ZirconiumX> *everything*
<ZirconiumX> quartus_map? Gone, use quartus_syn instead
<ZirconiumX> altiobuf_*? Gone, use gpio instead
<ZirconiumX> altddio_*? Gone, use gpio instead
<ZirconiumX> Even better, the naming of ports of gpio is not compatible with that of altiobuf/altddio
* ZirconiumX cries
balrog has quit [Quit: Bye]
balrog has joined #m-labs
mumptai has quit [Quit: Verlassend]
electronic_eel_ has joined #m-labs
electronic_eel has quit [Ping timeout: 268 seconds]
electronic_eel has joined #m-labs
electronic_eel_ has quit [Ping timeout: 240 seconds]