Bureaucrats, dave_user, Administrators
4,650
edits
Changes
no edit summary
== Introduction ==
This White Paper describes a practical application of the asymmetric multi-processing (AMP) configuration illustrated [[AN-BELK-001:_Asymmetric_Multiprocessing_(AMP)_on_Bora_–_Linux_FreeRTOS|here]]. Specifically, this approach is used to implement a non-intrusive continuous link monitoring mechanism for the Xilinx Zynq multi-gigabit serial transceivers{{efn|More complex configurations such as [[BRX-WP001:_Real-timeness,_system_integrity_and_TrustZone®_technology_on_AMP_configuration|this one]1] can be used as well.}}. The starting point for this work is represented by the Xilinx Application Notes
XAPP743<ref name="XAPP743"> Mike Jenkins, David Mahashin, ''XAPP743 (v1.0.1) Eye Scan with MicroBlaze Processor MCS'', 28th October 2013''</ref>
and
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 of monitoring multi-gigabit transceivers link status when operating on the field{{efn|That is after the product has been deployed.}} [2] in a <u>non-intrusive way</u>. 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:Borax-wp001 01.png|thumb|center|400px|Concept block diagram of the system without monitoring subsystem]]
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 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:
*<span id="REQ3">REQ4</span>: the overall system functionality.
[1] More complex configurations such as [[BRX-WP001:_Real-timeness,_system_integrity_and_TrustZone®_technology_on_AMP_configuration|this one]] can be used as well.
[2] That is after the product has been deployed.
==Link monitoring==
Before illustrating a possible solution, some further considerations about requirements listed in previous section are illustrated.
