选择 RTOS、CPU 和 IDE 来帮助将 .NET 应用程序一分为二：嵌入式（固件）应用程序和 Windows（.NET）应用程序
选择 RTOS、CPU 和 IDE 来帮助将 .NET 应用程序一分为二：嵌入式（固件）应用程序和 Windows（.NET）应用程序
choosing RTOS, CPU and IDE to help with splitting .NET app in two: embedded(firmware) app and windows(.NET) app
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
RTOS、TCP/IP、文件系统和 USB 不需要紧密集成（即您不一定需要一个已经包含所有这些组件的 RTOS），这是完全可能的，而且事实上独立获取所有这些组件并集成并不太困难他们自己。这将为您提供最广泛的解决方案选择。例如，我已成功将 Keil 的 RTX 内核（通过其 ARM 工具链免费）与 ELM FatFs< 集成/a> 和 STMicroElectronics 的 STM32 USB 库。也就是说，Keil 还提供了一个扩展（非免费）库，其中包括更易于集成的 TCP/IP、USB 和文件系统。
然而，有许多可能的集成解决方案，作为一站式商店，Segger 提供可以轻松集成的独立 RTOS、TCP/IP、USB 和文件系统库。成本是一个问题 eCos 操作系统是一个开源操作系统，包含所有这些内容以及一个由贡献的代码和库组成的大型生态系统。
为了与 PC 上的 .NET 紧密耦合，您可能会在嵌入式系统上使用 .NETmicro 效果更好，但这不具有实时能力，并且需要大约 300Kb 的内存来启动，而对于具有 USB、TCP/IP 的 RTOS 可能需要 30Kb和文件系统。
您在标题中提到了 CPU 选择，但在问题中没有提到。您需要考虑性能要求和 I/O 能力。显然，如果它支持片上以太网和 USB，那将是一个好的开始。许多微控制器都具有这些外设，但单一架构供应商的最广泛选择可以在基于 ARM 的设备中找到。我建议您查看 STM32 或 Freescale Kinetis 设备，它们是 ARM Cortex M3/4 设备，具有多种片上外设组合和开发板可供选择。
RTOS, TCP/IP, Filesystem, and USB need not be tightly integrated (i.e. you do not necessarily need an RTOS that includes all those already), it is entirely possible, and in fact not too difficult to obtain all those components independently and integrate them yourself. That would give you the widest choice of solution. For example, I have successfully integrated Keil's RTX kernel (free with their ARM toochain) with ELM FatFs, and STMicroelectronics' STM32 USB library. That said, Keil also provide an extended (non free) library that includes TCP/IP, USB, and filesystem that would be easier to integrate.
However there are many possible integrated solutions, as a one-stop shop, Segger provide separate RTOS, TCP/IP, USB and file-system libraries that can be easily integrated. f cost is an issue eCos os an open source OS with all those things includes and a large ecosystem of contributed code and libraries.
For tight coupling with .NET on the PC you might do better using .NETmicro on the embedded system, but that is not real-time capable and requires about 300Kb jut to boot as opposed to perhaps 30Kb for an RTOS with USB, TCP/IP and a filesystem.
You mention CPU choice in the title, but not in the question. You need to consider performance requirements and I/O capability. Obviously if it supports Ethernet and USB on-chip that would be a good start. Many microcontrollers have these peripherals, but the widest choice of vendors for a single architecture can be found in ARM based devices. I suggest that you look at STM32 or Freescale Kinetis devices, being ARM Cortex M3/4 devices with a wide selection of on-chip peripheral combinations and development boards.
方程式中有太多变量...我想您应该首先选择CPU（根据您的技术要求和观点），然后咨询制造商/社区，了解该核心可用的生态系统（编译器、工具、RTOS、调试器、IDE、模拟器、演示板、入门套件等）
Too many variables in equation... I suppose you should choose CPU first (according to your technical requirements and perspective) and then consult with manufacturer/community on which ecosystem is available for this core (compiler, tools, RTOS, debugger, IDE, simulator, demo-boards, starter-kits, etc)