Difference between revisions of "BXELK-TN-002: Non-intrusive continuous multi-gigabit transceivers link monitoring"
(→Introduction) |
(→Introduction) |
||
| Line 25: | Line 25: | ||
with Vivado IP Integrator and AXI4'', 19th November 2014''</ref>, thus reading of these documents is highly recommended. | with Vivado IP Integrator and AXI4'', 19th November 2014''</ref>, thus reading of these documents is highly recommended. | ||
| − | The issue that this White Paper addresses is the need to monitor multi-gigabit transceivers link status <u> | + | The issue that this White Paper addresses is the need to monitor multi-gigabit transceivers link status in a <u>non-intrusive way</u> and <u>on the field</u>{{efn|That is after product has been sold and it is operating.}}. Just imagine a product that is based on the architecture similar to the one depicted in the following figure. It is assumed that this architecture is quite representative of many real use cases. |
[[File:TBD.png|thumb|center|200px|Concept block diagram of the system]] | [[File:TBD.png|thumb|center|200px|Concept block diagram of the system]] | ||
| − | In Programmable Logic (PL) | + | A generic communication IP is implemented In Programmable Logic (PL) . This IP makes use of multi-gigabit transceivers to communicate with the peer at the other end of the physical link. On Processor Subsystem (PS) side, Linux operating system is used. On top of the kernel, several applications run, implementing high-level product's functionalities, including the management of data sent and received data through the link shown in the figure. It is also assumed that the reliability of this link is a crucial factor for the successful product functioning. Thus a specific monitoring of its health has to be implemented in order to detect any deviation from normal working conditions that may affect link robustness such as: |
*medium/long-term drift of the physical link characteristics | *medium/long-term drift of the physical link characteristics | ||
*significant part to part variations of such characteristics. | *significant part to part variations of such characteristics. | ||
| Line 33: | Line 33: | ||
*<span id="REQ1">REQ1</span>: the software applications running in the Linux realm | *<span id="REQ1">REQ1</span>: the software applications running in the Linux realm | ||
*<span id="REQ2">REQ2</span>: the user functions implemented in PL | *<span id="REQ2">REQ2</span>: the user functions implemented in PL | ||
| − | *<span id="REQ3">REQ3</span>: the overall system functionality. | + | *<span id="REQ3">REQ3</span>: the overall system functionality. |
==Proposed solution== | ==Proposed solution== | ||
Revision as of 13:02, 22 September 2015
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
History[edit | edit source]
| Version | Date | BELK version | Notes |
|---|---|---|---|
| 0.9.0 | September 2015 | 3.0.0 | Internal draft |
Introduction[edit | edit source]
This White Papers describes a practical application of the asymmetric multi-processing (AMP) configuration illustrated here. Specifically, this technique is used to implement a non-intrusive continuous link monitoring mechanism for the Xilinx Zynq multi-gigabit serial transceivers[a].
The starting point for this work is represented by the Xilinx Application Notes XAPP743[1] and XAPP1198[2], thus reading of these documents is highly recommended.
The issue that this White Paper addresses is the need to monitor multi-gigabit transceivers link status in a non-intrusive way and on the field[b]. Just imagine a product that is based on the architecture similar to the one depicted in the following figure. It is assumed that this architecture is quite representative of many real use cases.
A generic communication IP is implemented In Programmable Logic (PL) . This IP makes use of multi-gigabit transceivers to communicate with the peer at the other end of the physical link. On Processor Subsystem (PS) side, Linux operating system is used. On top of the kernel, several applications run, implementing high-level product's functionalities, including the management of data sent and received data through the link shown in the figure. It is also assumed that the reliability of this link is a crucial factor for the successful product functioning. Thus a specific monitoring of its health has to be implemented in order to detect any deviation from normal working conditions that may affect link robustness such as:
- medium/long-term drift of the physical link characteristics
- significant part to part variations of such characteristics.
Additional requirements have to be met, that is monitoring function has to be substantially non-intrusive with respect to:
- REQ1: the software applications running in the Linux realm
- REQ2: the user functions implemented in PL
- REQ3: the overall system functionality.
Proposed solution[edit | edit source]
In contrast to XAPP743[1] and XAPP1198[2] whe
Conclusions[edit | edit source]
Cite error: <ref> tags exist for a group named "lower-alpha", but no corresponding <references group="lower-alpha"/> tag was found, or a closing </ref> is missing
