This version (27 Feb 2023 17:48) was approved by S Fernandez.The Previously approved version (17 Nov 2022 16:14) is available.Diff

Click here to return to A2B Bus Analyzer Homepage.

Functional Limitations

The following are the functional limitations of the Analyzer hardware.

Number Summary Description Affects (HW ver) Fixed (HW ver)
No support of power over USB-C Power delivery for the Analyzer unit over USB-C port is currently not supported. Power the unit using the supplied 12V adapter 1.0.0
1337 No access to peripherals on intermediate AD242x nodes In a system with all AD242x nodes or mix of AD242x/3x nodes, if Analyzer is used as a last sub-node, peripherals connected to intermediate AD242x sub nodes are not accessible over remote I2C 1.0.0

Known Issues

The following are the know issues with the Analyzer software.

Number Summary Description Affects (SW ver) Fixed (SW ver)
652 No progress shown for Application Update Download on Linux Progress % will not be shown after clicking update application. The update will download and install in the background after a short time. Progress can be seen if the A2B Bus Analyzer is launched from a Terminal command prompt. 1.2.0
934 License Activation may not succeed if using a VPN Under certain rare circumstances the license activation mechanism may fail if the computer is connected to a VPN. In case of problems users should disconnect their VPN. 1.2.0
1071 If the firmware goes into a bad state, then pressing Reset button on the enclosure only resets the A2B Bus Analyzer board and not the firmware. Power-cycle the board to full reset the A2B Bus Analyzer. 1.2.0
Higher TDM modes such as TDM16/32 are not fully tested Audio might be noisy while sinking the audio channels for these TDM modes when A2B Bus Analyzer is acting as an Emulator. 1.2.0
1249 Simultaneous use of File In and File Out options on Monitor or Emulator can cause audio distortion When using A2B Bus Analyzer as a Monitor or as an Emulator (Main/Sub), using both File In (sourcing WAV from PC) and File Out (recording bus audio as WAV) simultaneously in any project feature can cause distortion in sourced and recorded audio due to too much data throughput between the device and the PC. 1.2.0
1559 Bus Monitor not always available after discovering a mixed topology with AD242x and AD243x on the network In a system with a mix of AD242x/3x nodes, if Bus Monitor is used when the Analyzer is acting as a Main node, then Bus Monitor may not always be available after discovering the network 2.2.0
A2B Bus Analyzer doesn't support monitoring the bus or emulating a node using straight through cables Current hardware of the A2B Bus Analyzer doesn't have the front end circuitry to support straight through cables. Additional circuitry has to be built external to A2B Bus Analyzer by the user in order to use it with straight through cables. 1.0.0
A2B Bus Analyzer displays AD243x register bit fields in “Advanced register” tab while emulating AD242x sub-node A2B Bus Analyzer uses a AD243x transceiver and simulates a AD242x sub-node. In the advanced register tab, when AD242x sub-node is simulated, the UI eliminates the AD243x specific registers. But for a register which is common to both AD242x and AD243x, additional bit fields of AD243x show-up even for AD242x. Customers have to refer AD242x technical reference manual to get register description. 2.3.0
When emulating a main node, sub only registers cannot be accessed in the “Advanced register” tab The A2B Bus Analyzer UI keeps a single list of registers which can be accessed when emulating a node. This means that when emulating main only registers that are either common to main and sub nodes or main-only registers are displayed. For this reason in the advanced register tab, while you can read/write registers from the sub nodes, you cannot access registers that do not exist in main like the mailbox registers. In order to use those registers, you can use the SDK, which accepts any valid register address. 2.3.0
1860 A2B Bus Analyzer modifies volume control for SPDI/F digital input A2B Bus Analyzer when used as either monitor or emulator, modifies the audio level for SPDI/F digital interface through volume control. Users need to be careful while testing bit exactness of digital audio. 3.0.0 3.1.0
1998 UASDK C++ emulator register_example returns an error on Linux The C++ emulator_register example provided in the UASDK attempts to write a value of 5 to the TESTMODE register. On Linux this causes a USB timeout and the a2ba_sdk_emulator_register_access function returns A2BA_SDK_FAILED. Rather than writing a value of 5, writing a value of 4 should behave as expected. 3.1.0
1952 Error frames seen on Monitor when both Main node emulator and Bus Monitor features are used simultaneously and different network file (.dat) are applied When both Bus monitor and Main node emulation is enabled together on the same A2BA unit, applying different dat files while keeping the Monitor active with 'discovered' checkbox enabled may result in error events. 3.1.0
2153 USB channel from the UI may contain an unknown offset or be incorrect for streams over 32 The UI sets up the USB channels (both in and out) as the index of the streams in the levels being displayed. This results in unexpected offsets for customers which are dependent on the channels used.
This also can lead to errors where the stream number is greater than 32 but the FW only supports 32 so the channel number is invalid.
As a workaround customers can use the SDK where they can choose the channel numbers.
resources/tools-software/a2b-bus-analyzer/known-issues.txt · Last modified: 27 Feb 2023 17:46 by S Fernandez