Hi Pavel,
While using your wonderful project as a base for my custom development, I encountered a problem with the AXIS DAC IP.
I couldn't get it to latch a single data transfer (1 clock tvalid). Turns out dac_rst had to be delayed to let the IP clock out the data and then instruct the AD9767 DAC to latch it (see attached image from the datasheet). Without delay, the DAC would latch the 'b0 frame which is clocked out whenever tvalid is not present.
The DAC is perfectly happy keeping the value latched indefinitely.
I've tested the IP with a sparse stream on a RedPitaya board. I expect no significant change to continuous streams apart from skipping erroneous 'b0 sample "injection" at the start of the stream.
Hi Pavel, While using your wonderful project as a base for my custom development, I encountered a problem with the AXIS DAC IP. I couldn't get it to latch a single data transfer (1 clock tvalid). Turns out dac_rst had to be delayed to let the IP clock out the data and then instruct the AD9767 DAC to latch it (see attached image from the datasheet). Without delay, the DAC would latch the 'b0 frame which is clocked out whenever tvalid is not present.
The DAC is perfectly happy keeping the value latched indefinitely.
I've tested the IP with a sparse stream on a RedPitaya board. I expect no significant change to continuous streams apart from skipping erroneous 'b0 sample "injection" at the start of the stream.
Please consider checking this PR. Thanks!