Analyzer SDK - FAQ

Document created by Anil on Apr 4, 2018Last modified by Anil on Apr 4, 2018
Version 2Show Document
  • View in full screen mode

Q: What functionality does the A2B Analyzer SDK provide?

A: With the A2B Analyzer SDK you will be able to create a Master or Slave node simulation on A2B by using the A2B Analyzer. For each simulated Master or Slave node you will need a dedicated A2B Analyzer.


Q: When using the A2B Analyzer as a master, how is a configuration provided to the slave.

A: Typically if slave nodes require configuration by the master then their peripherals are accessible via its local AD2410 transceiver’s I2C pins. In this case, the master will program them during the discovery process. With the A2B Analyzer this is accomplished by the Host using the A2B Analyzer SDK.


Q: Can the A2B Analyzer be used to simulate a slave node on the network?

A:  Yes, the A2B Analyzer can absolutely be configured as a slave device using the anlzr_devapiSetModeReq() API call. The one additional step required in configuring the A2B Analyzer as a slave is, you'll need to add an API call to let the SDK and A2B Analyzer know the AD2410 configuration using the anlzr_strmapiConfigA2bTdmReq() API call. The A2B slaves are configured by the master, and the slave cannot access this configuration data. After supplying this configuration, the A2B Analyzer can then be configured, for example, to route audio from a slot on the A2B network to an A2B Analyzer output, or to save that audio input to a file on the host. This is essentially what is performed in the example application provided with the A2B Analyzer SDK in a master configuration.
The Analyzer can also be configured to simulate a slave node by using the A2B Analyzer Software application.


Q: How is TDM-channel mapping between the A2B bus and the computer handled, and what capabilities are available?

A: There are two modes to consider, Master and Slave.

In master mode, the A2B Analyzer uses a fixed dual line 8 slot 32 bit TDM configuration supporting 16 inputs and 16 outputs. For any particular configuration, unused TDM slots are filled with zeros and never shifted out on the A2B bus.  The A2B Analyzer automatically reformats the USB audio data as necessary to fit this configuration.

In slave mode, the A2B Analyzer supports all TDM configurations possible on the AD2410. The A2B Analyzer automatically reformats the audio data as required when sending or receiving from analog, S/PDIF, or USB streams.


Q: How is GPIO configured and controlled using the A2B Analyzer SDK?

A: There are a number of API calls available to configure and control both A2B GPIO and A2B Analyzer GPIO. Please refer to the documentation for the following API calls for more detail:

  • anlzr_gpioapiGetA2bReq()
  • anlzr_gpioapiGetExtReq()
  • anlzr_gpioapiSetA2bOutputsReq()
  • anlzr_gpioapiSetExtOutputsReq()
  • anlzr_gpioapiSetA2bDirReq()
  • anlzr_gpioapiSetExtDirReq()

Q: How are the two tri-color LEDs on the A2B Analyzer controlled?

A: API calls similar to those available for GPIO are used, for example anlzr_gpioapiSetLedReq(). Additionally there are defined constants that can be used to refer to the specific LED (upper or lower) and the desired output color for the LED. Both LEDs are available for use by applications written with the A2B Analyzer SDK.


Q: Is source code provided for the A2B Analyzer SDK?

A: No.


Q. How can the SDK be used to read Slot activity to measure channel level?

A: Use the API

(a) anlzr_strmapiGetA2bSrcMonitorReq (struct anlzr_Device *  dev,  anlzr_U16  tId  ) and

(b) anlzr_strmapiGetA2bSrcMonitorDecode (struct anlzr_Response *  resp,  struct anlzr_StrmApiA2bSrcMonitorResp *  info  )

After response is received, the RX/TX activity level information can be got from the anlzr_StrmApiA2bSrcMonitorResp structure.

You can also refer to the A2B Analyzer SDK documentation for more details. It will be located under A2B Analyzer SDK -> Modules -> Analyzer Streaming Services -> Functions.