You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 5, 2022. It is now read-only.
I was updating the meta-de10-nano recipes in order to use the latest Angstrom branch (2018/Sumo) and also the latest de10-nano-hardware release (RELEASE-20180612_19.29.23) here: https://github.com/feddischson/meta-de10-nano/tree/sumo
I was not able to get the FFT apllications working (with the new mentioned de10-nano-hardware release).
To be honest, I am not sure if it is a issue on the FPGA side or within the driver.
I figured out that the driver hangs always while waiting for the last descriptors to be finished.
As far as I can see, the status register (CSR_STATUS_REG) returnes 0x03 all the time (see here)
Do you have an idea if there have been changes within the soc or fft_sub between the first and latest release which could explain this?
The text was updated successfully, but these errors were encountered:
I have seen this issue but as of yet have not resolved it. No, the hardware for the fft was not changed, but that doesnt mean that the underlying IP in quartus wasn't updated.
Hi,
I was updating the meta-de10-nano recipes in order to use the latest Angstrom branch (2018/Sumo) and also the latest de10-nano-hardware release (RELEASE-20180612_19.29.23) here: https://github.com/feddischson/meta-de10-nano/tree/sumo
I was not able to get the FFT apllications working (with the new mentioned de10-nano-hardware release).
To be honest, I am not sure if it is a issue on the FPGA side or within the driver.
I figured out that the driver hangs always while waiting for the last descriptors to be finished.
As far as I can see, the status register (CSR_STATUS_REG) returnes 0x03 all the time (see here)
Do you have an idea if there have been changes within the soc or fft_sub between the first and latest release which could explain this?
The text was updated successfully, but these errors were encountered: