• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 46 subscribers
  • Views 263 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ADS9219EVM: GUI Device_Mismatch Error

Austin Pohlman
Prodigy 50 points
Part Number: ADS9219EVM
Other Parts Discussed in Thread: TSWDC155EVM, ADS9219, ADS9218, ADS9227EVM

Tool/software:

Hello,

I recently purchased the ADS9219EVM and the TSWDC155EVM, and I downloaded version 2.0 (latest) of the ADS92XXEVM-GUI software from https://www.ti.com/tool/ADS9219EVM#order-start-development.

While following the ADS9219EVM user guide steps to get started, prior configuration steps completed OK, but the "Initialize ADS92xx" button in the GUI config tab (user guide section 3.2.3) reported back a "Device_Mismatch" status with a log message (see image below). 

Digging into the python files, this message appears to originate from GUI_bridge.py and is related to a Version ID read command that checks one of the ADC registers. Haven't been able to find any info on this on the forums, and there is no ADS92XXEVM-GUI manual, only what's available in the ADS9219EVM user guide.

Interestingly, a colleague was able to successfully use what looks like an earlier version of the GUI received from the link on this post https://e2e.ti.com/support/data-converters-group/data-converters/f/data-converters-forum/1214830/ads9218evm-pdk-download-location-for-the-ads92xxevm-software-referenced-in-user-guide. However, that GUI only appears to operate correctly at a 4MHz sampling rate and is missing functionality that v2.0 has like reading out the internal temp sensor, so I would like to resolve this issue rather than attempt to work around it.

My setup is:

  • Windows 10 laptop, followed user guide to install USB drivers
  • USB 3.0 port directly connected & powering TSWDC155EVM via the provided USB cable
  • 5.5V external supply connected to power ADS9219EVM. Quiescent draw ~70mA when not configured
  • Power sequencing for the ADS9219EVM doesn't seem to matter -- same results when powering on prior to TSWDC155EVM or after, in all cases powered on ADS9219EVM prior to attempting initialization
  • Default GUI settings for data rate, data lanes, etc...
  • Worth noting that the physical IC on the ADS9219EVM is only marked "92xx" rather than the full part number which is what I'd expect.
  • ESD-safe practices followed (mat & ground strap)

 

  • 0
    TI__Expert 4010 points

    Hello Austin,

    Thank you for bringing this up. This message on this GUI appears due to the device not being fully released to market yet, but the GUI/device should still be functional, this message can be ignored.

    This GUI works with multiple EVMs and devices, some of those devices have been fully released and others not yet, like the ADS9219. Since this EVM has been released prior to the full release of the ADS9219, the marking on the device is also marked as “ADS92xx”. It is still functional as an ADS9219 though.  If the device on this EVM is replaced with a fully released device, e.g. ADS9218, the message should not pop up.

    In the other post shared for the ADS9218EVM the software had not been fully released yet and this additional step was needed.  I will also note the ADS9218EVM is now obsolete. Since then we have updated the both the GUI and both the ADS9219EVM and ADS9227EVM so that they are all compatible with all the ADS92xx devices.  

     

    I appreciate you sharing your step through as well as your set up, this is all very helpful and should lead to a functional set up.

     

    Could you expand a bit more on how the GUI is only operating correctly at 4MHz? Can you read back from the device at all outside of the 4MHz sampling rate? is this with the FPGA clock or with an external clock? 

    The temperature read back option in the GUI does not seem correct. It seem like it is correct in the register map view, and with what is actually coming out it in the GUI seems like it still needs to be calculated further (formula below). This GUI will be updated soon and that will be one of the features to be fixed in the coming update.

    Best regards, 

    Yolanda