Wiki

Analog Devices Wiki

English
English
简体中文
简体中文
日本語
日本語
Руccкий
Руccкий

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
resources:tools-software:a2bv2:quickstartguide:appendix-a [08 Dec 2022 13:50] – [Network Properties] Gireesha Nirvanaiahresources:tools-software:a2bv2:quickstartguide:appendix-a [20 Dec 2023 12:19] (current) – [Network Properties] Gireesha Nirvanaiah
Line 18: Line 18:
       * EVAL- AD2430WC1BZ: This is a sub node only platform       * EVAL- AD2430WC1BZ: This is a sub node only platform
       * EVAL- AD2430WG1BZ: This is a sub node only platform       * EVAL- AD2430WG1BZ: This is a sub node only platform
-      * EVAL- AD2438WD1BZ: This can be used as both a main and a sub node+      * EVAL- AD2438WD1BZ: This can be used as main node
       * EVAL- AD2437A1NZ: This can be used as both a main and a sub node       * EVAL- AD2437A1NZ: This can be used as both a main and a sub node
-      * EVAL-AD2437B1NZ: This is a sub node only platform.+      * EVAL- AD2437B1NZ: This is a sub node only platform. 
 +      * EVAL- AD2437A1MZ: This can be used as both a main and a sub node. 
 +      * EVAL- AD2437B1MZ: This is a sub node only platform.
   - **A2BBusAnalyzer**   - **A2BBusAnalyzer**
     - **AD242x:** This can be used for Main/Sub Node Emulation or Bus Monitoring of 242x transceiver variants on the A2B Bus Analyzer Hardware     - **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     - **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: 
- 
-{{:resources:tools-software:a2bv2:quickstartguide:a2b_platforms_in_toolbox.png?250|}} 
  
 +{{ :resources:tools-software:a2bv2:a2bssplususerguide:tree_toolbox_.png?600 |}}
 **Figure 56:** A2B platforms in toolbox **Figure 56:** A2B platforms in toolbox
 ===== Transceivers and Peripherals ===== ===== Transceivers and Peripherals =====
Line 35: Line 35:
   * Generic device: A device that takes an xml file as input for programming via I2C.   * 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).   * 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.+These devices are available as part of the toolbox once inside the platform view/canvas as shown in below, 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) ====+==== Transceiver settings (General View, Register View, Stream View and Crossbar View) ====
 The transceivers and peripheral settings window can be opened by double clicking on the transceiver/peripheral in the platform view. Additionally, it can also be opened by clicking on the “Settings” option under the transceiver/peripheral in the project window. The transceivers and peripheral settings window can be opened by double clicking on the transceiver/peripheral in the platform view. Additionally, it can also be opened by clicking on the “Settings” option under the transceiver/peripheral in the project window.
  
Line 55: Line 55:
  
 **Figure 60:** Node Level Stream View **Figure 60:** Node Level Stream View
 +
 +{{:resources:tools-software:a2bv2:a2bssplususerguide:crosbar_view.png?500|}}
 +
 +**Figure:** Crossbar View Tab 
 ===== Network Properties ===== ===== Network Properties =====
 The Network Properties tab, as shown in [[:resources:tools-software:a2bv2:quickstartguide:appendix-a#network_properties|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 Network Properties tab, as shown in [[:resources:tools-software:a2bv2:quickstartguide:appendix-a#network_properties|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.
  
-{{:resources:tools-software:a2bv2:quickstartguide:network_properties_tab.png?300|}}+{{:resources:tools-software:a2bv2:a2bssplususerguide:network_settings_tab.png?600|}}
  
 **Figure 61:** Network Properties Tab **Figure 61:** Network Properties Tab
Line 68: Line 72:
 **Modified:** All sub nodes are discovered and immediately initialized (for synchronous data exchange) sequentially from sub 0 to the last available sub node in the system. **Modified:** All sub nodes are discovered and immediately initialized (for synchronous data exchange) sequentially from sub 0 to the last available sub node in the system.
  
-**Optimized:** Even before a node is initialized the host tries to discover the next node. The time for the next node to be discovered is used to initialize the current node. Synchronous data can start only after all nodes are discovered and initialized (not supported for AD2430 AND AD2438).+**Optimized:** Even before a node is initialized the host tries to discover the next node. The time for the next node to be discovered is used to initialize the current node. Synchronous data can start only after all nodes are discovered and initialized.
  
 **Advanced:** Even before a node is initialized the host tries to discover the next node. The time for the next node to be discovered is used to initialize the current node. Synchronous data exchange can start as soon as a main and sub node 0 is initialized (not supported for AD243x main). **Advanced:** Even before a node is initialized the host tries to discover the next node. The time for the next node to be discovered is used to initialize the current node. Synchronous data exchange can start as soon as a main and sub node 0 is initialized (not supported for AD243x main).
Line 75: Line 79:
  
 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. 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.
 +
 +**Override Bus Self Discovery:** If checked, Bus self-discovery status is ignored, discovery process starts with the soft-reset of A2B network. If unchecked, software looks for a self-discovered network, configures the network as per the schematic. 
  
 **Enable Line Fault Diagnostics:** Enables line fault diagnostic feature of software. When set, SigmaStudio+ will continuously monitor the network for faults at 1 second interval. Detected faults will be handled and notified. **Enable Line Fault Diagnostics:** Enables line fault diagnostic feature of software. When set, SigmaStudio+ will continuously monitor the network for faults at 1 second interval. Detected faults will be handled and notified.
  
-**Rediscovery upon faults:** If checked, automatic network rediscovery will be performed upon detecting post-discovery faults.+**Rediscovery upon faults:** If checked, automatic network rediscovery or partial discovery 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).   * **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.   * **Discovery Interval (ms):** Delay between each rediscovery attempt in milliseconds.
Line 85: Line 91:
   * **Tracing:** Logs key information and network events during the stack execution to a text file. User can configure the required ‘Level’ and ‘Domain’ for tracing.   * **Tracing:** Logs key information and network events during the stack execution to a text file. User can configure the required ‘Level’ and ‘Domain’ for 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.   * **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.
 +
 +The Refresh  {{:resources:tools-software:a2bv2:a2bssplususerguide:refresh.png?20|}}  button checks and updates the discovery status of connected A2B Nodes upon a click.
resources/tools-software/a2bv2/quickstartguide/appendix-a.1670503842.txt.gz · Last modified: 08 Dec 2022 13:50 by Gireesha Nirvanaiah

Page Tools