Forum Discussion
Hi,
Any follow up from your side?
- hsaee65 years ago
New Contributor
As mentioned in my question.
the FPGA and the HPS are booting from its respective QSPI.
HPS is connected to QSPI, and FPGA is connected to another QSPI.
They are booting up independently.
Here is what is found.
1) when i use a baremetal project and GOD forbid if i have some where in my HPS c baremetal code a "printf" used. then the HPS is not booting up at all.
when we checked from the debugger it was running perfectly. but as soon we make a boot image for the HPS code with "printf" in it the HPS is not booting. the HPS traps somewhere.
2) the HPS and the FPGA boots up independently. The HPS boots up faster then the FPGA in independent booting mechanism. The HPS code waits on the line of the c code where it will communicate with FPGAs pio peripheral. As soon as the FPGA boots. the peripheral is available for the HPS to and then the HPS proceeds onwards.
Analysis
so what i analyzed is that it doesn't matter if the HPS starts up first or FPGA. if the HPS is using the peripherals it will wait on the same line of c code as soon as it is available it will proceed.