Build 17763的正常运行时间问题 [英] Uptime issues with Build 17763
问题描述
我有一个在Raspberry PI 3上使用build 17763的产品。 虽然应用程序调试得很好，并且config.txt文件已正确配置...包括将GPU保持在250 Mhz ...经过几个月的正常运行时间测试后，我们无法获得
设备停留完全可操作超过一周而没有问题。 系统的核心仍然在运行，但我们要么每隔几天就会看到一个应用程序重启（比如框架故障），或者当通过专用的官方RP触摸屏使用
时标准视频驱动程序失败。端口 如果发生锁定，我们的产品上会有一个基于硬件的监视器，但是这个监视器永远不会触发，因为尽管存在其他问题，应用程序仍在运行。 另外
必须禁用板载声卡，以确保它不会使触摸屏的数字转换器驱动程序崩溃。 微软有没有人在长期测试中看到这些问题，因为几个月后，我的公司在
我们的应用程序代码中找不到设计问题？ 我们也没有看到产品中设计的电源或硬件问题，我们在测试期间监控电源输出......如果我们无法解决这个问题，我们可能需要切换硬件并查看是否不同的
司机有所作为...
I have a product that uses build 17763 on Raspberry PI 3. Although the application is well debugged, and the config.txt file is properly configured...including keeping the GPU at 250 Mhz...after several months of uptime testing, we just can't get the device to stay fully operable for longer than a week without issues. The core of the system stays running, but we either see an application restart every couple of days randomly (like a framework failure) or a failure of the standard video driver when being used with the official RP touch screen through the dedicated port. We have a hardware based watchdog on our product should a lockup occur, but this watchdog never fires because the application is still running despite the other issues. Also the onboard sound card had to be disabled to make sure it does not crash the digitizer driver for the touch screen. Has anyone at Microsoft seen these issues in longer term testing because after several months, my company can't find design issues in our application code? We also don't see issues with the power supply or hardware as it was designed into the product and we monitor the power supply output during testing...if we can't work this out we might have to switch up hardware and see if different drivers make a difference...
谢谢，
Dan DeMerchant
Dan DeMerchant
推荐答案
您好，danoplus，
Hello danoplus,
>> > 我有一个产品在Raspberry PI 3上使用build 17763。
>>>I have a product that uses build 17763 on Raspberry PI 3.
您使用的是哪个版本17763.1或17763.107？
Which version do you use 17763.1 or 17763.107?
>>> 系统的核心仍在运行，但我们要么每隔几天看一次应用程序重启（比如
）框架失败）
>>>The core of the system stays running, but we either see an application restart every couple of days randomly (like a framework failure)
您的意思是您的应用程序自行重启但系统没有重启？如果系统始终运行，您可以通过设备门户获取应用程序的实时进程转储。
Do you mean your app restart by itself but the system doesn't restart? If the system always running you can get the live process dump of the app via device portal.
通常，应用程序不会自动重新启动，除非您将其设计为，但在Windows上IoT Core后台应用程序将自动重启。所以你在谈论背景应用吗？
In general, the app won't restart automatically except you design it to be, but on Windows IoT Core the background application will auto restart. So are you talking about background application?
>>> 微软有没有人在长期测试中看到这些问题，因为之后几个月，我的公司不能在我们的应用程序代码中找到设计问题吗？
>>>Has anyone at Microsoft seen these issues in longer term testing because after several months, my company can't find design issues in our application code?
在长时间运行后，我从未看到app重启的问题。也许我的运行时间不够长，或者我使用的应用程序无法重现此问题。我从来没有听说过这个问题。
I never see this issue that app restart after long time running. Maybe I didn't run long enough or apps I used can't reproduce this issue. And I never heard of this issue.
如果可能，您可以在Windows 10桌面等其他设备上运行您的应用，看看它是否可以重现此问题。
If possible, you can run your app on other device like Windows 10 desktop to see if it can reproduce this issue.
至于触摸屏冻结问题，在Raspberry Pi 3上使用3.5mm音频/视频插孔时，这是一个已知问题。
相关主题。
As for touch screen freeze issue, it is an known issue when using the 3.5mm Audio/Video Jack on Raspberry Pi 3. Related thread.
最后，您使用默认图像还是构建自定义图像？
At last, do you use default image or build your custom image?
祝你好运，
Rita
这篇关于Build 17763的正常运行时间问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
