Q: How do I get a copy of the A2B Analyzer Software Application?
A: When you purchase the A2B Analyzer System, you will receive a link to download the Windows and Linux installers of the A2B Analyzer Software from Mentor Graphics Support Center. The tool also comes with comprehensive documentation. Once registered on the Support Center site, you will also receive notification of any new updates to the Analyzer software and firmware.
Q: What output file formats are supported by the Analyzer Software?
A: The Analyzer Software (Network Builder utility) supports a human-readable session format, C file header, and a binary format based on Google Protocol Buffers.
Q: Is source code provided for the A2B Analyzer Application?
Q. Is there a limitation on number of streams possible to be configured in Network Builder utility?
A: There is no inherent limit.
Q. Why does the A2B Analyzer needs to know the network configuration while in slave mode?
A: The A2B Analyzer is more than just a A2B device as it lets you record and collect the data even from the slave nodes. We need the TDM configuration from the network configuration file when we're configured as a slave to know how to set up the Blackfin's synchronous serial peripheral ports (SPORTs) and CODEC. Providing the network configuration to slave nodes enable you to routes audio correctly inside the A2B Analyzer and also collect the data into the HMI from the PC.
Q: Are there any other learning resources available?
A: A detailed video walkthrough of the tool is available (see link at top of page). In addition, a 1-day training material is also available.
Q. The OEM/Tier1 aren’t able to provide a suitable bus description data file (Mentor doesn’t support the export options from ADI). A configuration “by hand” is not doable, since there are so many parameters the Mentor interface asks for, a few the vendors can’t even provide. How can slave suppliers get the BDD data?
A. The Network Builder tool differs from the approach ADI takes in configuring A2B nodes/networks. To successfully create a network configuration file for an A2B network you’d only need to know the TDM settings (I2SGCFG and I2SCFG registers) to hear audio from your slave. In case you are using GPIO on any pin on the AD24xx, only in that case you would additionally need to touch the GPIO registers. Normally, you wouldn’t have to modify any other registers apart from this. The TDM information can be easily found even in ADI’s XML export format.
Also, just for your information ADI’s tool only writes register values to slave nodes that differ from the power on default values. So, if you see a register not specified in ADI’s format it’s fairly safe to assume that the register would be configured to it power on default value.
Q: Can the Node Simulator utility be used to simulate a slave node on the A2B network?
A: Yes, the Analyzer can simulate both a master or a slave node, and this can be configured using the Node Simulator utility. Make sure to use v220.127.116.11 or newer.
Q: No audio playing after running discovery and starting audio/tones?
A: This is likely because the CODEC on the slave has not been initialized. If you are using a WBZ/WGZ ADI evaluation board you need to set the "Peripheral Cfg" utility. This is also applicable to slaves that need to setup DSPs/peripherals in the slave nodes.
Q: What information should be provided by the user to debug HMI problems?
A: The Analyzer Application can dump all its settings to aid in reproducing problems. Navigate to the About dialog box. The About dialog box contains a System Info button that will copy all the necessary system info to the clipboard. You can then copy the information directly into an email, or a file.
Some of the information copied is by the System Info button is:
- General system/application info: CPU/Arch/SW versions/etc
- Any lock files for detecting lock problems
- State file contents
- Preferences file contents
- Register dump of the current network (if possible)
- Portions of the log (from the Logging tab)
- Last Saved and Current Session
- The last discovery's UML Sequence