Vybrid ProcessorsのトピックRe: Adding delay to Vybrid Quad SPI boot

Adding delay to Vybrid Quad SPI boot

jefy — Thu, 04 Jun 2015 18:13:13 GMT

Hello All,

I am working on Vybrid tower VF65GS10_A5. I have an application which is configured to run from DDR in the linker script file. I am flashing the application to Quad SPI so that on power-on reset it would boot from Quad SPI and run from DDR. The application currently boots from Quad SPI and runs successfully from DDR. I don't have an explicit copy program to copy my application from QSPI to DDR, so I assume it would be copied from QSPI to DDR on boot-up automitically (Not sure how this works, any more detail on this would also be helpful)

So I don't have a problem with booting from Quad SPI and executing from DDR. But the problem is that the application is actually a GUI application and has some graphics and font data which is not displayed on the screen properly. So I am thinking that on boot up these data are not copied to DDR completely due to which i am seeing incomplete and distorted graphics on the screen.

One probable solution to this which i am thinking would be to add some delay before booting from QuadSPI so that it gets enough time to copy the data completely to DDR. Any help on how to do this or any other options would be greatly appreciated

Thanks & Regards,

Jefy

Re: Adding delay to Vybrid Quad SPI boot

karina_valencia — Mon, 08 Jun 2015 21:49:35 GMT

timesyssupport can you attend this case?

Re: Adding delay to Vybrid Quad SPI boot

timesyssupport — Tue, 09 Jun 2015 14:23:11 GMT

Hello Jefy,

To clarify - this is not a Linux system running, but a bare-metal application flashed, booted, and copied from QSPI to DDR and executed to run?

Thank you,

Timesys Support

Re: Adding delay to Vybrid Quad SPI boot

jefy — Wed, 10 Jun 2015 14:44:34 GMT

Hello,

Thanks for looking into this. Yes, this isn't a Linux system.

However, i managed to make this work without adding a delay, by making some modifications to quadspi_boot.c and the linker script file.. The application now boots from QSPI and copies the application properly to DDR and runs from there.

Thanks & Regards,

Jefy