I downloaded the Virtual Bench 3.0 tool and and installed it as per instructions and on first run, I let it perform an update. This increased the number of devices listed in the config.xml file and database directory.
In the updated config.xml file and the database, there is an entry in the new config.xml file for the MPQ4210 and there is a MPQ4210 directory in the database. Despite there being many devices in the config.xml file and the database directory, the VB 3.0 tool only displays a subset of these devices when trying to add a device. Importantly for me. the MPQ4210 does not appear in the list.
On using the PMBus Tool, if I set the I2C address to be 66, I can read the contents of the MPQ4210 on the EVQ4210-U-00b board.
The Virtual Bench 4.0 tool does not work.
The MPQ4210 GUI tool does not work.
The config.xml file has line entries like the following:
FileDataInfo Path=“Database/MPQ4210/DefaultDatasheet.Spec” MD5=“C5EEC756BDE97C278968FF0B76239B97” Size=“10639”
The file size of the MPQ4210 DefaultDatasheet.Spec does not match the size stated in the config.xml but changing it to be 10,415 bytes does not get the MPQ4210 to appear so in addition to that, I assume the MD5 number has to match as well. In fact, experimentally changing the file size of devices that do appear in the add device list does not affect the display in the list, so it appears the file size is not checked by the tool. Maybe it is just the MD5 value that is checked.
Clearly because the file size for the MPQ4210 entry is incorrect, it is highly likely someone hasn’t updated the config.xml file to reflect the latest MPQ4210 DefaultDatasheet.Spec file.
Given these clues, do you think you could provide me an updated set of files which does allow the MPQ4210 device to be selected.
In the meantime, I will try to evaluate the board using the PMBus Tool.