MAX1454
Production
The MAX1454 is a highly integrated analog sensor signal conditioner targeted for automotive applications. The device provides amplification, calibration...
Datasheet
MAX1454 on Analog.com
MAX77860
Production
The MAX77860 is a high-performance single input switch mode charger that features USB Type-C CC detection capability in addition to reverse boost capability...
Datasheet
MAX77860 on Analog.com
The MAX1454EVSYS development board connects to a PC via USB, however after installing the 1454R11 software and USB driver, the PC is unable to install the correct driver.
The dev board is identified as a "Maxim MINIQUSB Module" which is different to that listed in the driver documentation where it is "USB <-> Serial". The USB driver is "CDM 2.06.00 WHQL Certified" and this correlates with the FTDI chip on the MAX1454EVSYS board. The provided driver installs with no issues.
I have tried various operating systems: Windows 2000, Windows XP, Windows 7 and Windows 10. In all cases the board is recognised as a MINIQUSB Module and I'm unable to locate an alternative driver for this. I've even downloaded the latest version of the CDM driver that supports Windows 10.
The board is essentially useless without a working driver. The MAX1454 application executes perfectly fine but is unable to detect a MAX1454 EV System board.
Has anyone experienced a similar issue and can assist?
Thank you,
- Alan
JEstayo - Moved from Precision ADCs to Amplifiers. Post date updated from Thursday, February 15, 2024 7:12 PM UTC to Friday, February 16, 2024 1:41 AM UTC to reflect the move.
I have managed to get communications after installing the "MAX77860 Evaluation Kit Software", then removing the GUI application. This uses the MINIQUSB driver and have successfully communicated with the MAX1454 in the MAX1454EVSYS system.
Hope this helps anyone in the same situation as me. I'm a bit disappointed that Analog/Maxim have not responded to my support case as yet - does not fill me with confidence.
Hi Alan,
We apologize for the late response to your query. It is good to know that this has already been resolved and thank you for sharing your solution. I believe this was not immediately acknowledged since this query was under the wrong forum.
-L