dh73 has quit [Read error: Connection reset by peer]
alexhw has quit [Ping timeout: 245 seconds]
alexhw has joined #yosys
<develonepi3>
mmicko are you online
<develonepi3>
davehah GM. Is QT5 needed for nextnpr only with GUI?
<daveshah>
Yes it's only needed for the gui
<daveshah>
It shouldn't be required if you build without the GUI
<develonepi3>
davehah Thanks
dh73 has joined #yosys
<develonepi3>
daveshah Thanks. I am having an issue with strip in yosys while cross compiling I needd to pass --input-target=elf64-littleaarch64. Any idea?
<daveshah>
No, I have not seen an issue like that before
fsasm has quit [Ping timeout: 265 seconds]
Jybz has joined #yosys
X-Scale has quit [Ping timeout: 265 seconds]
X-Scale` has joined #yosys
X-Scale` is now known as X-Scale
dys has quit [Ping timeout: 245 seconds]
meawoppl has joined #yosys
<meawoppl>
heyo, got a weird question for the Yosys crew
<meawoppl>
is there a way on the ice40 to use an input as both a lvds pair, and normal input pin?
<meawoppl>
I am trying to detect the mipi transition to HS mode, which looks logic-low of both of the paired elements, but I am unclear how to wire that
<meawoppl>
when I do the intuitive route I get something like:
<meawoppl>
```ERROR: PACKAGE_PIN of SB_IO 'myCamera.myMIPI.lp_compare' connected to more than a single top level IO.ERROR: Packing design failed.```
<daveshah>
No, LVDS mode cannot be used at the same time as a normal input pin
<daveshah>
You would have to connect the MIPI signals to two pairs of pins separately
<daveshah>
use one as LVDS and one as single ended (the latter needs to be either 1.2V IO or using two pairs and the LVDS comparators against a 0.6V threshold)
<piegames1>
zipcpu: Why does it check the reset on the *last* cycle instead of the current one?
<ZirconiumX>
I think it's so the condition triggers after at least one cycle has passed
<ZirconiumX>
(i.e. not on the very first cycle)
develonepi3 has quit [Quit: Leaving]
<piegames1>
ZirconiumX: I think you misunderstood me. I'm not asking why `f_past_valid` is checked, but why `$past(i_axi_reset_n)` is used instead of `i_axi_reset_n`.
<ZirconiumX>
piegames1: that's what I was answering
<ZirconiumX>
$past does not trigger on the first cycle as I understand it
<piegames1>
My concrete problem is: I have a situation where VALID is set but not READY. The assertions state that VALID must hold until READY was set. But if I have a RESET during this situation, there is one cycle where my valid went low (because of the reset), but the assert still triggers because the if only checks that there was no reset in the *last* cycle. Therefore, this fails verification of my design
<piegames1>
even if I think the bevhaviour of my component is correct.