ContributionsMost RecentMost LikesSolutionsRe: ERROR: Nothing PROVIDES 'u-boot-socfpga' Yes , did I miss out any steps ? Re: ERROR: Nothing PROVIDES 'u-boot-socfpga' Yes, I executed the three commands before running the bitbake ERROR: Nothing PROVIDES 'u-boot-socfpga' I am following the steps in https://www.rocketboards.org/foswiki/Documentation/AgilexSoCGSRDDEVAGF027 When I run the bitbake_image, error occur ERROR: Nothing PROVIDES 'u-boot-socfpga' I am following the steps in https://www.rocketboards.org/foswiki/Documentation/AgilexSoCGSRDDEVAGF027 When I run the bitbake_image, error occur How to determine the RTile PCie revisionIn the R tile PCIe user guide , there are configuration space register for rev A and rev B, how to determine which rev I am using ?Re: How to fix setup violation for signal tap? Hi Richard, The timing violation is actually a hold but not setup. I apologies for the mistake about the setup violation -Try to add pipeline factor (maximum 5) It is a clock input signal and not the real data signal. I am not sure can add the pipeline to clock signal or not Could you share screenshot of the failed timing path's "Data Arrival Path" in the "Data Path" and the "Statistic" Report in the Timing Analyzer? What is the number of logic levels? Re: How to fix setup violation for signal tap? Please let me check the suggestion and I will get back to you. Re: Programming sof using different firmware Hi Aiman, I just want to understand the usage of the firmware in this folder, when and how it is being used. Re: How to fix setup violation for signal tap? Hi Richard, I cannot share the design for confidential information. I tried to create a simple design but the timing violation does not occur in the simple design. The timing violation occur from the input clock port to the signal tap data signal, what we can try to fix this? Re: How to fix setup violation for signal tap? Hi Richard, The suggestion does not help for this scenario. The timing violation occurs between the clk to the signal tap signal. How to resolve this? It is a clock to signal tap timing path violation, not between the logic in the core design.