Contributor
ContributorOk, more info for this situation.
KEY 1: If data is kept reading on f2h_sdram0 148M no issue is found.
Once the f2h_sdram1 is enable via some control and start stream at 144M the system stall on distro.
However, the data r/w on bus f2h_sdram0 andf2h_sdram1 are functioning properly.
The only issue is the system aka the CPU is stall and terminal no longer response.
The most interesting thing is that the background FPGA fabric are all functioning like free-run w/o any stall or data stuck.
Well the same design with only slowing down the f2h_sdram1 from 144M to 100M fixed all the issue.
f2h_sdram0 <- mostly read
f2h_sdram1 <- mostly write
So when 144M is used onf2h_sdram1 and once the CPU is stall. All data read / write are still working.
read streams write streams are all functioning via some interface to verify.
Brian
Regular Contributor
From the AXI3 protocol, it does not define a maximum hold time. It would depend on the Master internal state machine to determine the timeout after signaling the WVALID to the slave.
From the test it is expected as the camera is streaming data through the bridge this causes the HPS access to the SDRAM to be limited causing the OS to stall.
