求一些嵌入式电信板的参考资料
我参与了电信行业的嵌入式软件开发。我以前对此类嵌入式硬件设备的经验为零。
我有一个网络处理器板，它的特点是切换管道引擎。 除了该板之外，还有一个名为“piggy”的配件板（似乎用于以太网连接）和另一个串行线连接。
我完全迷失了这些板和串行线连接。它们的用途是什么？我尝试使用google找到一些有用的介绍或材料但失败了。谁能指出这个小猪板是做什么用的？有什么好的参考资料或书籍可以解释这一点吗？
多谢！！
I am involved with an embedded software development for telecom industry. I have zero experience before with such embedded hardware devices.
I got a network processor board, which is featured in switching pipeline engines.
Besides the board, there is also an accessory board called "piggy"(seems for ethernet connetion), and another serial line connection.
I am completely lost about these boards and serial line connections. what they are used for? I tried to use google to find some useful introduction or materials but failed. Can anyone point out what this piggy board is used for? Any good references or books that explain about this?
Thanks a lot!!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
要开发嵌入式系统，您需要一台开发主机（托管开发工具的 PC 或工作站，包括交叉编译器、平台库、调试器等）以及与目标的调试连接（通常是在线仿真器或JTAG 调试器，但在某些情况下，可以通过目标上运行的软件支持通过串行、USB 或以太网进行调试 - 尽管这不太可靠，因为您正在调试的代码可能会损坏或破坏在同一目标上运行的调试存根。
当您将这些整合在一起并可以在目标上构建、加载和运行代码时，您就可以提出更具体的问题。为该平台编写代码将取决于许多因素，例如处理器类型、编程语言、目标操作系统（如果有）、实时性能要求、监管标准、产品类型标准等。
关于如何访问您的特定硬件，那么没有人可以告诉你，如果没有文档和硬件原理图，你就无法自己用它做任何事情。在大多数情况下，一些电子知识将是一个明显的优势。
To develop for your embedded system you will need a development host (a PC or workstation that hosts the development tools including cross-compiler, platform libraries, debugger etc.), and a debug connection to the target (typically an in-circuit emulator or JTAG debugger, but in some cases debug over serial, USB or Ethernet may be supported via software running on the target - though that is less reliable since the code you are debugging may corrupt or break the debug stub running on the same target).
When you have got that together and can build, load and run code on the target, you may then be in a position to ask a more specific question. Writing code for this platform will depend on many things such as processor type, programming language, target operating system (if any), real-time performance requirements, regulatory standards, product type standards etc.
With respect to how to access your specific hardware, then no one can tell you that without access to the documentation and hardware schematics, and you cannot do anything with it yourself without that. Some knowledge of electronics will be a distinct advantage in most cases.