This shows you the differences between two versions of the page.
Previous revisionNext revision | |||
— | resources:tools-software:a2bv2:quickstartguide:appendix-a [24 Nov 2022 14:06] – [Network Properties] Gireesha Nirvanaiah | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== APPENDIX A: Navigating A2B schematic in SigmaStudio+ ====== | ||
+ | ===== Platforms ===== | ||
+ | The A2B Plugin for SigmaStudio+ gives the following default platforms for the user: | ||
+ | - **A2B** | ||
+ | - **AD242x:** | ||
+ | * EVAL- AD2428WD1BZ: | ||
+ | * EVAL- AD2428WB1BZ: | ||
+ | * EVAL- AD2428WC1BZ: | ||
+ | - **AD243x:** | ||
+ | * EVAL- AD2433WA1BZ: | ||
+ | * EVAL- AD2433WB1BZ: | ||
+ | * EVAL- AD2435WA3LZ: | ||
+ | * EVAL- AD2435WJ3LZ: | ||
+ | * EVAL- AD2430WD1BZ: | ||
+ | * EVAL- AD2430WC1BZ: | ||
+ | * EVAL- AD2430WG1BZ: | ||
+ | * EVAL- AD2438WD1BZ: | ||
+ | * EVAL- AD2437A1NZ: This can be used as both a main and a sub node | ||
+ | * EVAL-AD2437B1NZ: | ||
+ | - **A2BBusAnalyzer** | ||
+ | - **AD242x:** This can be used for Main/Sub Node Emulation or Bus Monitoring of 242x transceiver variants on the A2B Bus Analyzer Hardware | ||
+ | - **AD243x:** This can be used for Main/Sub Node Emulation or Bus Monitoring of 243x transceiver variants on the A2B Bus Analyzer Hardware | ||
+ | These can be seen in the Toolbox in the system view as shown below: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Transceivers and Peripherals ===== | ||
+ | In addition to these, the plugin also provides a range of transceivers and generic peripheral devices as follows: | ||
+ | * AD242x, AD243x Main transceiver | ||
+ | * AD242x, AD243x Subordiante transceiver | ||
+ | * Generic device: A device that takes an xml file as input for programming via I2C. | ||
+ | * Non-Programmable generic device: A device that is used for representing not programmable peripherals in A2B system (e.g. Microphone). | ||
+ | These devices are available as part of the toolbox once inside the platform view/canvas as shown in **Error! Reference source not found..** The platform canvas can be opened by double clicking on the platform in the system view or by clicking the “Canvas” option under the platform in the Project window. | ||
+ | |||
+ | ==== Transceiver settings (General View, Register View and Stream View) ==== | ||
+ | The transceivers and peripheral settings window can be opened by double clicking on the transceiver/ | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | {{ : | ||
+ | ===== Network Properties ===== | ||
+ | The Network Properties tab, as shown in Figure 61, offers configurable options for the target processor software. With these settings one can select the node discovery and initialization method to be used and the clock source for the A2B network. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The four possible discovery methods are | ||
+ | |||
+ | **Simple:** All sub nodes are discovered sequentially from sub 0 to the last available sub node in the system. Once all the sub nodes are discovered, they are initialized for synchronous data exchange. | ||
+ | |||
+ | **Modified: | ||
+ | |||
+ | **Optimized: | ||
+ | |||
+ | **Advanced: | ||
+ | |||
+ | **Discovery Start Delay (ms):** Delay (in milliseconds) to wait after a software reset and before discovery start. | ||
+ | |||
+ | The Line Fault settings allow user to enable fault diagnostic feature of the software. With this any line fault encountered in the system is handled and reported to the user. | ||
+ | |||
+ | **Enable Line Fault Diagnostics: | ||
+ | |||
+ | **Rediscovery upon faults:** If checked, automatic network rediscovery will be performed upon detecting post-discovery faults. | ||
+ | * **No. of Attempts:** Specifies the number of re-discovery attempts to be tried if the fault persists (-1 for infinite retry). | ||
+ | * **Discovery Interval (ms):** Delay between each rediscovery attempt in milliseconds. | ||
+ | |||
+ | **Stack Debug Settings:** This feature allows the user to analyse/ understand the system by using the information logged during stack execution. Information can be either through TRACE or sequence chart or both. | ||
+ | * **Tracing: | ||
+ | * **Sequence Chart:** Sequence Chart captures network transactions in the form of a rich graphical sequence diagram. The sequence chart enables easy understanding of the discovery flow, fault analysis and various other interactions within the system thus enabling quick debugging. |