谢谢你的依赖。
我对REF设计做了一些测试。
如果将configure设置为BPI SYNC类型。
无论关键字是打开还是关闭，设计总是会有一个IPROG跳转到更新映像。
在Ug 470 doc中，它写入FPGA将以异步模式启动以读取闪存，因此快速启动头中的IPROG命令将始终作为异步模式读取。
似乎FPGA位是同步或异步应该对Quick Boot标头中的IPROG命令没有影响。
为什么设计总是在异步BPi模式下跳转到更新图像？
谢谢
以上来自于谷歌翻译
以下为原文
Thanks for your rely.
I do some test on the REF design. If Set the configure as the BPI SYNC type. The desing will ALWAYS have a IPROG jump to the update image, no matter the Critical WORD is on or off. In the Ug 470 doc, it write the FPGA will start as async mode to read the flash, so the IPROG command in the Quick boot header will always be read as the async mode. Seems the FPGA bit is sync or async should have no affect to the IPROG command in the Quick Boot header. why the design always have a Jump to the update Image in the async BPi mode ? thanks
谢谢你的依赖。
我对REF设计做了一些测试。
如果将configure设置为BPI SYNC类型。
无论关键字是打开还是关闭，设计总是会有一个IPROG跳转到更新映像。
在Ug 470 doc中，它写入FPGA将以异步模式启动以读取闪存，因此快速启动头中的IPROG命令将始终作为异步模式读取。
似乎FPGA位是同步或异步应该对Quick Boot标头中的IPROG命令没有影响。
为什么设计总是在异步BPi模式下跳转到更新图像？
谢谢
以上来自于谷歌翻译
以下为原文
Thanks for your rely.
I do some test on the REF design. If Set the configure as the BPI SYNC type. The desing will ALWAYS have a IPROG jump to the update image, no matter the Critical WORD is on or off. In the Ug 470 doc, it write the FPGA will start as async mode to read the flash, so the IPROG command in the Quick boot header will always be read as the async mode. Seems the FPGA bit is sync or async should have no affect to the IPROG command in the Quick Boot header. why the design always have a Jump to the update Image in the async BPi mode ? thanks
举报
