无法让SIM卡运行

谢谢florent  - 我明天会创建另一个帖子。
在原帖中查看解决方案



以下为原文

Thanks florent - I'll create the other thread tomorrow.
 
 
 
 
View solution in original post

你好@ john321
您正在关注哪个教程？
在此处分享教程链接。
谢谢，
维奈
--------------------------------------------------
------------------------------------------您是否尝试在Google中输入问题？
？
如果没有，你应该在发布之前。
此外，MARK这是一个答案，以防它有助于解决您的查询/问题。给予帮助您找到解决方案的帖子。



以下为原文

Hi @john321
 
Which tutorial are you following?
Share the tutorial link here.
 
Thanks,
Vinay
--------------------------------------------------------------------------------------------
Have you tried typing your question in Google? If not you should before posting. Also, MARK this is as an answer in case it helped resolve your query/issue.Give kudos to the post that helped you to find the solution.

嗨Vuppala
对不起 - 这不会有帮助！
我正在做Vivado设计套件教程高级综合
UG871（v2017.1）2017年5月5日
这是PDF Vivado HLS首次启动时提出的第一个教程。
第1-8章很好。
第9章在IP Integrator中使用HLS IP
一切似乎工作正常，直到我到达最后一步，它需要
顶级模块名称，因此出错。
我试图手动插入我认为它可以使用但无济于事的东西。
我已经重复了上一章（RTL验证）并遵循了
如果应该留下一些东西，但也没有用。
从某种意义上来说它很好，因为它迫使我环顾四周
文件和界面更多，但如果我可以排序它会很好。
最后的第10步说运行行为模拟它出错了
由于缺少模块名称而无法运行，因此步骤11无法运行。
这可能是非常简单的事情 - 我还不够了解
发现我认为。
谢谢
学家



以下为原文

Hi Vuppala
 
Yes sorry - it would help wouldn't it!
 
I'm doing the Vivado Design Suite Tutorial High-level synthesis
UG871 (v2017.1) May 5 2017
This is the first tutorial PDF Vivado HLS brings up when first started.
 
Chapters 1-8 went fine.
 
Chapter 9  Using HLS IP in IP Integrator
Everything seems to work fine until I get to the final step and it requires
the top level module name and so errors out.
 
I've tried to manually insert what I think it could use but to no avail.
And I've repeated the previous chapter (RTL Verification) and followed
on in case that should have left something but that hasnt worked either.
 
In one respect its good because it has forced me to look around the
files and interface more but it would be good if I could sort it.
 
Step 10 at the end says to Run Behavioral Simulation which it errors
out on because of the lack of module name and so step 11 can't be run.
 
It might be something very simple - I just don't know enough yet to
spot it I think.
 
thanks
 
j.
 
 

我无法解决该教程的问题所以我已经转移到下一个（在同一个PDF中）Ch。
10在Zynq AP Soc设计中使用HLS IP。
这会产生相同的错误。
慢慢地看一遍，我注意到“创建HDL Wrapper”阶段（指令第4段）创建了包装文件，并将其放在文件夹名称“Non-Module Files（1）”下的sources窗格中。
这与教程中的屏幕捕获不符，后者将包装器直接放在Design Sources（2）下。
这可能是问题吗？
此外，我现在有一个错误列表，显示从Zynq_Design_Wrapper（8）开始的32个块设计错误
我可以在包装文件中看到... / bd / hdl文件夹。
谁能提出我在这里弄错了什么？
谢谢
学家



以下为原文

I can't resolve the issue with that tutorial so I've moved onto the next (in the same PDF) Ch. 10 Using HLS IP in a Zynq AP Soc design.
 
This produces the same error.
 
Going through this slowly I notice that the stage "Create HDL Wrapper" (instruction paragraph 4. ) creates the wrapper file and puts it in the sources pane under the folder name "Non-Module Files (1)"
 
This does not tally with the screen capture in the tutorial which puts the wrapper directly under Design Sources(2).
Could this be the issue?
 
Also I now  have an error listing showing 32 block design errors starting with the Zynq_Design_Wrapper (8)
I can see in the wrapper file itself in .../bd/hdl folder.
 
Can anyone suggest what I'm getting wrong here please?
 
thanks
 
j.

有人可以试试这个教程吗？
大约需要5分钟才能完成。
（消息2为哪一个）
我开始认为它可能与我的系统（win7-64 SP1）不兼容，这意味着我需要
修复一些东西 - 或者一个bug。
如果这是一个错误我会期望别人遇到它，但后来如何
很多人正在运行教程？
在所有运行中遇到的第一个错误（从上面的一个开始）是一个报告的“语法或路径错误” - 它没有具体关于哪个，我找不到它想要做什么，除了它的下一步
在创建包装器之后。



以下为原文

Could someone try this tutorial for me? It takes about 5 minutes to run through. (message 2 for which one)
I'm starting to think it may be either an incompatibility with my system (win7-64 SP1)  which means I need to
fix something- or a bug. If it was a bug I'd have expected others to encounter it but then how
many people run tutorials right through?
 
The first error encountered in all the runs (starting from the one above) is a reported "syntax or path error" - it isn't specific about which and I can't find what it is trying to do except its the next step right after creating the wrapper.
 
 
 

我回过头来对每个教程和示例都有同样的问题 -
（加载微胶片示例 - 尝试合成并且它无法找到顶部模块） - 错误说明了
不是任何或他们是错误的，这取决于你是否尝试创建一个包装或其他什么。
我花了一些时间来处理这些非常无益的消息和日志
并得出结论，某处必须有一个硬编码的安装路径
在搜索顶部文件时，不考虑非默认位置的安装
级别模块。
（其他一切似乎都有效）
因为我在驱动器D上安装而不是驱动器C这可能是问题???
无论如何 - 我将尝试重新安装到默认设置，看看问题是否解决
（特别是因为这里无处不在，没有其他人报道它）
（我确实尝试重新安装到我的位置，因此它不仅仅是随机安装错误。）
如果有人有更好的主意，请告诉我！



以下为原文

I've come back to this and still have the same issue with every tutorial and example -
 
(load the microblaze example - try the sythesis and it cant find the top module) - the error says there
arent any or they are faulty depending on if you try and create a wrapper or whatever.
 
I've spent some time with this and trawling through the very unhelpful messages and logs
and have come to the conclusion that there must be a hard coded installation path somewhere
that does not account for installations in non default locations when searching files for the top
level module. (everything else seems to work)
 
As I installed on drive D not drive C this may be the issue ???
 
anyway - I will try and re-install to default settings and see if the problem resolves
(especially since this is ubiquitous here and no one else is reporting it)
(I did try re-installing to my locations  so its not just a random install error.)
 
If anyone has a better idea please let me know !
 
 
 
 
 
 
 

HI @ john321，
你能分享你的源窗口（在vivado中）的截图吗？
你是否每次都看到包装器（它们是否生成？）？
如果是，您是否可以尝试右键单击它并单击设置为顶部？
希望有所帮助，
问候，
FlorentProduct应用工程师 -  Xilinx技术支持EMEA ------------------------------------------
--------------------------------------------------
----------------------------不要忘记回复，kudo，并接受作为解决方案。



以下为原文

HI @john321,
 
Could you share a screenshot of what your sources window (in vivado) looks like?
 
Are you seeing the wrappers each time (are they generated?)? If yes, could you try to right click on it and click set as top?
 
Hope that helps,
 
Regards,
Florent
Product Application Engineer - Xilinx Technical Support EMEA
------------------------------------------------------------------------------------------------------------------------
Don't forget to reply, kudo, and accept as solution.

嗨弗洛朗
我有一些时间来检查这一点 - 我会考虑明天做你的捕获请求 - 我似乎能够在源列表中创建和查看包装器 - 但我还不知道检查它们的内容。
我现在意识到去年我第一次安装V2017.1时遇到了vcredist_x64问题 - 我猜这可能与此有关吗？
其他人在安装过程中遇到了vcredist_x64.exe问题但我看不到“特定”的解释或修复
除了我在下面列出的页面之外的任何地方都提到过 - 这里不起作用。
回顾这些消息，建议是用系统变量有效地“躲避”安装
它具有允许安装的效果。
当时我从未见过Vivado，并且假设我做了一些愚蠢的事情（仍然可以？）和
将愚蠢的值放在顶部模块框中。
无论如何 -
今天我已经对硬盘进行了分区并安装了Centos 6.9（最终版）并在没有安装的情况下安装了vivado
任何问题，一切正常 - 我测试了micrlaze示例和顶级模块没有发现任何问题。
唯一的麻烦是我必须使用win7-64，它提供完全相同的顶级模块错误和故障
如果我选择新安装的2017.4搜索也会找到它们，这也报告了vcredist错误 - 但确实如此
允许安装以其他方式完成。
看看我的系统，我实际上从其他地方安装了vcredist 2015  - 版本是：14.0.23026
（我不知道安装了什么 - 所以我不愿意删除它） -  vivado日志中没有进一步的信息
除了简单的安装通知失败或两个。
（没有说什么或为什么）
（我不知道vcredist文件版本之间是否有重大变化，或者它们是否可以共同存在）
我已经完成了所有的建议和检查：https：//www.xilinx.com/support/answers/69076.html
所以我安装了vcredist，但也许不是正确的版本？
（去年我把win7修补到SP1  - 或之前...）
尝试安装vivado提供的vcredist时给出的错误消息是“无法创建受信任源的路径”，错误代码为0x800b010a
这可能是微软证书系统，所以我搜索了错误代码并尝试了我能找到的所有证书复制建议 - 但这并没有解决“顶层模块”问题。
最重要的模块问题可能完全不相关，但如果是这样的话，这有点巧合。
如果是的话 - 还有什么
我能检查一下吗？
这是我唯一的问题 - 未能找到顶级模块名称 - 但当然可以解决问题。
哦是的 -  DEP已关闭 - 我以管理员身份登录 - 根本没有防火墙（机器空气不足 - 没有网络/ wifi等）
我已经尝试取消隐藏和取得树木的所有权等。我已经应用了所有权利（系统/管理员/用户等）。
不用找了。
PS
对不起，这有点长，但我浪费了大量的时间在这上面，想得到什么信息
我可以记录，万一你可以看到我做一些愚蠢的事情（或不做...等）
我希望我不必在不知道更多的情况下运行完全干净的win7-64安装
（它是一台很好的机器）但我现在想不出任何其他的东西。
欢迎提出保护我的理智的建议！
（我现在把苏格兰威士忌......）



以下为原文

Hi Florent
 
I've had some time to check this out - I'll look into doing your capture request tomorrow - I seem to be able to create and see wrappers in the sources list though - but I dont know enough to check their content yet.
 
I now realise I had the vcredist_x64 issue last year when I first installed V2017.1 - I'm guessing this may be related to that?
Others have had the vcredist_x64.exe issue during installation but I cant see a "specific" explanation or fix
mentioned anywhere but the page I listed below - which doesnt work here.
 
Looking back at those messages the advice was to effectively "bodge" the installation with a system variable
which had the effect of allowing the install.
 
at the time I'd never seen Vivado before and assumed It was me doing something stupid (still could be ?) and
putting silly values in the top module box or something.
 
Anyway -
 
Today I've partitioned a hard drive and installed Centos 6.9(final) and installed vivado on that without
any problems and everything works fine - I tested with the microblaze example and top modules are found no trouble.
 
The only trouble is I  HAVE to use win7-64 which gives exactly the same top module error and failures
to find them if I select a search with newly installed 2017.4 which also reported the vcredist error - but did
allow the install to otherwise complete.
 
Looking at my system I actually have vcredist 2015 installed from elsewhere -  version is: 14.0.23026
(I dont know what installed it though - so I'm reluctant to delete it) - no further info in the vivado logs
except a simple failure to install notice or two. (doesnt say what or why)
(I dont know if there are major changes between the vcredist file versions OR if they can co-inhabit)
 
I've gone through all the suggestions and checks on: https://www.xilinx.com/support/answers/69076.html
So I have  vcredist  installed but perhaps not the right version? (I patched win7 to SP1 last year - or before...)
 
The error message given when trying to install the vivado supplied vcredist is along the lines of "Unable to create path to trusted source" with error code 0x800b010a
 
This is presumably the microsoft certificate system so I searched the error code and tried all the certificate copying suggestions I could find - but this doesnt fix the "top module" issue.
 
The top module issue could be totally unrelated but it is a bit of a coincidence If so. and if so - what else
can I check? That's my only issue - the failure to find the top module name - but of course that gumms the works up.
 
Oh yes - DEP is off - I'm logged in as admin - no firewalls at all (the machine is air gapped - no network/wifi etc)
and I've tried unhiding and taking owership of the trees etc.  I've applied full rights to it all(system/admin/users etc).  No change.
 
PS
Sorry this is a bit long but I've wasted a huge amount of time on this and wanted to get what info
I can recorded in case you can see me doing something stupid (or not doing ... etc)
 
I'm hoping I dont have to run up a totally clean win7-64 installation without knowing more
(Its a well stuffed machine) but I can't think of anything else to try right now.
 
Suggestions to save my sanity are welcome !
(I'm putting the scotch away now..... )
 
 
 

好的 - 昨晚我咬了一口子弹并进行了系统备份。
今天早上我删除了现有的vcredist然后重新启动。
然后我尝试安装随vivado提供的版本 - 它拒绝安装。
然后我发现并重新安装了我以前的版本（它来自手动安装） - 和
它安装没有问题。
很明显，问题是与Vivado一起分发的vcredist_x86.exe的版本。
它显然与某些系统不兼容。
我猜这也是为什么Vivado无法找到顶级模块而失败的“srcscannerfailed”无论是
手动或自动搜索。
似乎需要使用不同版本的vcredist才能让Vivado在某些Windows系统上运行。



以下为原文

 
OK - I bit the bullet last night and did a system backup.
 
This morning I deleted the existing vcredist then rebooted.
I then tried to install the version supplied with vivado - it refused to install.
Then I found and re-installed the version I had on previously (it was from a manual install it turns out) - and
it installed with no problems.
 
It seems clear that the problem is the version of vcredist_x86.exe that is being distributed with Vivado.
It obviously is not compatible with some systems.
 
I'm guessing that is also why Vivado cant find the top level module and fails with "srcscannerfailed" whether
manually or automatically searching.
 
A different version of vcredist seems required to get Vivado to work on some Windows systems.
 
 
 

PS
这是我在安装日志中找到的 - 也许有人知道如何纠正这个问题：
[03C8：0D7C] [2018-01-16T21：47：25] e000：错误0x800b010a：有效负载的验证码验证失败：C： ProgramData  Package Cache  .unverified  vcRuntimeAdditional_x64 [03C8：0D7C] [2018-01-16T21
：47：25] e000：错误0x800b010a：无法验证有效负载的签名：vcRuntimeAdditional_x64 [03C8：0D7C] [2018-01-16T21：47：25] e310：无法验证有效负载：vcRuntimeAdditional_x64在路径：C： ProgramData
包Cache  .unverified  vcRuntimeAdditional_x64，错误：0x800b010a，删除：是[03C8：0D7C] [2018-01-16T21：47：25] e000：错误0x800b010a：无法缓存有效负载：vcRuntimeAdditional_x64 [0778：0E08] [2018-
01-16T21：47：25] e314：无法缓存有效负载：vcRuntimeAdditional_x64来自工作路径：d： Temp  {f144e08f-9cbe-4f09-9a8c-f2b858b7ee7f}  vcRuntimeAdditional_x64，错误：0x800b010a。[0778：0E08] [2018
-01-16T21：47：25] e349：应用程序请求重试有效载荷：vcRuntimeAdditional_x64，遇到错误：0x800b010a。
重试...
以上循环几次然后放弃。



以下为原文

 
PS
 
This is what I found in the installation log - perhaps someone knows how to correct this issue:
 
[03C8:0D7C][2018-01-16T21:47:25]e000: Error 0x800b010a: Failed authenticode verification of payload: C:ProgramDataPackage Cache.unverifiedvcRuntimeAdditional_x64
[03C8:0D7C][2018-01-16T21:47:25]e000: Error 0x800b010a: Failed to verify signature of payload: vcRuntimeAdditional_x64
[03C8:0D7C][2018-01-16T21:47:25]e310: Failed to verify payload: vcRuntimeAdditional_x64 at path: C:ProgramDataPackage Cache.unverifiedvcRuntimeAdditional_x64, error: 0x800b010a, delete: Yes
[03C8:0D7C][2018-01-16T21:47:25]e000: Error 0x800b010a: Failed to cache payload: vcRuntimeAdditional_x64
[0778:0E08][2018-01-16T21:47:25]e314: Failed to cache payload: vcRuntimeAdditional_x64 from working path: d:Temp{f144e08f-9cbe-4f09-9a8c-f2b858b7ee7f}vcRuntimeAdditional_x64, error: 0x800b010a.
[0778:0E08][2018-01-16T21:47:25]e349: Application requested retry of payload: vcRuntimeAdditional_x64, encountered error: 0x800b010a. Retrying...
 
The above loops a few times then gives up.