描述

ACE报告路由错误，如何调试出了什么问题？

回答

There are several reports that you can use to debug the issue yourself. These are listed below. If you need help from Achronix to find a solution, the following information is critical in debugging routing issues. Please collect as much of this information as possible and send it to Achronix to aid in your debug. The reports can be found in your <implementation>/reports/ directory or in some cases <implementation>/.debug/ directory.

1. 记下在路由错误之前报告的任何其他警告或错误。
2. ACE路由报告
   
   1. 该报告总结了路由，并列出了错误的类型（如果有）。如果有溢出或无法路由的网段，则在此处列出网络。此外，还有时钟路由信息。
   2. The routing report can be found in <implementation>/.debug/<project>_routing.html or view it in ACE.
   3. If ACE errors out before printing the 路由 report, simply run 'report_routing' in the TCL console.
   4. 阅读完此报告后，您应该能够确定发生了哪种路由错误，以及有问题的网络是数据路由，时钟路由还是两者。
3. PDC文件中的任何放置限制。应该研究这些内容以确保放置约束不会引起问题。
   
   1. 尤其要注意任何异常约束，例如将数据信号放置在时钟引脚上，或将时钟信号放置在数据引脚上。
   2. 还请注意请求ACE在时钟网络上路由数据信号的任何限制，因为这可能会影响路由。
   3. 如果在I / O引脚附近发生布线错误（您可以在ACE的planplanner透视图中查看溢出和丢失的段位置），则应考虑引脚位置。
4. SDC时序限制
   1. Check any clock definitions, and make sure all clocks are defined properly. If using generated clocks, make sure these are defined using create_generated_clock in the SDC.
   2. 检查其他任何时序约束，尤其是任何时序异常。
5. 时钟报告
   1. 该报告列出了所有时钟，ACE理解的时钟定义，它们之间的关系，并显示了在设备中每个时钟区域中路由的所有时钟的摘要。
   2. The clock report can be found in <implementation>/reports/<project>_clocks_<flow_step>.txt or you can view the .html version of the reports in ACE.
   3. If a clock report is not generated, simply run 'report_clocks' in the TCL console to print out information on the clocks in the design, or 'report_regions' to print a summary of clock usage in each region.
   4. 您可以使用该报告来确保您的设计不会过度订购时钟网络。