可能导致 Windows CE6 映像启动速度缓慢的常见问题有哪些？
我对 Platform Builder 比较陌生，虽然我能够生成 nk.bin 文件，但它们启动速度非常慢，需要 80-100 秒，所以我认为可能有一些复选框需要我设置（或清除）！
我已经在项目设置中删除了 kitl、profiling 等，并将项目设置为“release build”& '船'。
当我查看启动事件日志（在调试中）时，似乎没有任何特定的缓慢点。日志几乎一直滚动，没有大的停顿。
我发现奇怪的一件事是，尽管发布版本中的 nk.bin 文件要小得多（略低于 12Mb），但启动时间与调试版本相比并没有明显变化......
该板是 Vortex86DX_60A，我建筑CE6。
我在这里可能遗漏了任何“常见的构建者错误”，还是这会是更深层次的问题？
I am relatively new to Platform Builder, and whilst I am able to produce nk.bin files, they boot very slowly, 80-100 seconds, so I think there may be some checkbox somewhere that I need to set (or clear)!
I've already removed kitl, profiling, etc in the project settings, and set the project to 'release build' & 'ship'.
When I looked at the startup event log (in debug), there doesn't appear to be any specific point where it is slow. The log pretty much scrolls all the way through with no major pauses.
One thing I found strange was that although the nk.bin file was a lot smaller in release build (just under 12Mb), the boot time didn't noticeably change from the debug build...
The board is a Vortex86DX_60A and I'm building CE6.
Are there any 'common builder mistakes' that I may be missing here, or is this going to be something a little deeper?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
出现这种情况的第一个原因是在发布映像中启用 KITL。设备启动并等待 PC/KITL 连接一分钟或更长时间，然后超时。
其次是忘记将其设置为 RELEASE 模式。 DEBUG 版本的驱动程序（和内核）有很多调试溢出，这会大大减慢速度。
如果您已完成这两项操作，那么听起来您可能遇到了一个或多个驱动程序问题（我知道 Vortex86 在大多数情况下将在 20 秒内启动）。一般来说，当我编写驱动程序时，我喜欢让它们通过 RETAILMSG 报告加载所需的时间（使用 Xxx_Init 顶部和底部的 GetTickCount），这可以快速检查它们正在加载以及花费了多长时间。
The #1 reaon for something like this is leaving KITL enabled in a release image. The device boots and waits for a minute or more for a PC/KITL connection before timing out.
Second is forgetting to set it to RELEASE mode. DEBUG version of drivers (and the kernel) have a lot of debug spew that slows things considerably.
If you've done both of these, then it sounds like you've probably got one or more driver issues (I know a Vortex86 will boot up in under 20s in most conditions). Generally when I write drivers, I like to have them report via RETAILMSG the amount of time they take to load (using GetTickCount at the top and bottom of Xxx_Init), which provides a quick sanity check that they are loading and how long they took.