alt_qspi_read() QSPI addressing problem

I see, that's the same IC as I have on the Dev Kit board. My gut is that the Altera C code is to blame rather than the IC/board...... something in the QSPI indirect read code............. but no comment yet from Intel/Altera....

I've worked around the issue by adjusting the requests into alt_qspi_read(). I wrote a wrapper around this function and I read to address -4 with size +4. Hence I read the preceeding 4 bytes also.... then I pull out the data that I really want........ it's a total HACK of course but it is a reliable HACK for now until I find out the real source of the issue.

@INTEL ----- please give us some more input guys/girls.... your FPGA SoC is awesome.... loadsa folks wanna make solutions out of it and give you loads more money for these ICs but you really need to support us better..... pleeeease

We are using a board that’s is designed using Cyclone V SX SoC development kit as reference. Our software tools are Quartus Prime Lite 17.1 and Intel SoC FPGA Embedded Development Suite 14.1.

Are you using the same QSPI IC on your board?

We are using N25Q512A83GSF40F.

We are also stuck with a workaround solution for the moment.

Forgive me if I'm telling you something that you already know here but you have to word align your read requests in your workaround....... Hence you cannot read address-1 as a work around.... you have to read address-4 -- to the end of where you want to read and then copy the data out of the buffer....... forgive me if I'm teaching grannies to suck eggs 🙏

Good luck

Mike

Hi,

May I know which Quartus Version and SoC EDS that you are using?

Regards.

HI

Quartus Prime Lite Edition v18.1.1

"Intel FPGA 18.1.0.625