2019-02-03 03:58 PM
I have checked and re-checked this. Also used another USB to I2C converter and can read the registers just fine. Put an I2C analyzer on the setup and I see no activity when the GUI program starts.
Today on Github I found a HwCheckUtility.exe file. It launches, finds the com port and then indicates it found the I2C device at 0x28 address. I also see the scan on the logic analyzer.
I am now at a loss as to what do next.
GUI version is 1.06S. Thanks
Solved! Go to Solution.
2019-02-08 07:57 PM
2019-02-06 11:06 PM
Hello,
There is a known issue with the GUI on some computer configuration with several COM ports, where the port on which is connected the Nucleo board is not detected automatically.
Please use the updated version attached. It should resolve the port detection.
Check also that you have VC++ 2015 runtime properly installed.
Prerequisites for STUSBxx GUI:
• 1) On Windows 7, install: STM32 Virtual COM Port Driver (STSW-STM32102)
http://www.st.com/en/development-tools/stsw-stm32102.html
On Windows 10, no need to install additional drivers, because the USB CDC driver is already installed by default.
• 2) Install: Microsoft Visual C++ 2015 Redistributable Update 3
https://www.microsoft.com/en-us/download/details.aspx?id=53587
2019-02-07 03:23 PM
Gregory
Thank you so much. Once I test it, I will report back.
2019-02-08 07:57 PM
2019-02-13 04:55 PM
Gregory
Thank you for the new GUI. I used the latest one and it is now talking to the development board. So it looks like my problem is solved.
NOTE: On my Lenovo laptop (WIN 10), I had to install the 32 bit Microsoft Visual C++ 2015 Redistributable Update 3. Even though this is a 64 bit laptop, it wanted the 32 bit dll. No problem, it works which is all I want.
2019-03-12 06:37 PM
How did you know that you needed 32 bit Microsoft Visual C++ 2015 installed? The documentation talks about needing 2012 and including some of the dll's, but this is ST's documentation problem (and now mine) if you actually needed 2015 for it to work.
I already had C++ 2012 and 2017 for x86 and x64, so now I'm hoping 2015 is the difference. Had to uninstall 2017 to install 2015 and then reinstalled the 2017's.
Before uninstalling 2017 and installing 2015, the application could NEVER see the Nucleo. So I think JUST 2012 runtimes may not be enough. Annoying because I lost half a day to this problem before finding this post.
Now my Nucleo can be seen, but still not successful in talking to my STUSB4500. But that's likely an I2C wiring issue since you've confirmed 1.07 GUI version worked for you in the end.
Thanks
2019-03-13 01:51 AM
Hi,
Actually the GUI Application needs both 2012 and 2015 version of Microsoft Visual C++ Redistributable 32bit (x86).
Sorry for the confusion, the documentation on ST.com is not up-to-date. I will report it.
This utility is simple and doesn't need VC++ Redistributable.
You can get it here:
The Visual C++ 2017 Redistributable is a binary-compatible in-place upgrade of the Visual C++ 2015 Redistributable and shares the same registry keys.
So 2017 Redist replaces the 2015.
I haven't tried VC++ 2017, but if you already have VC++ 2017, you shouldn't need to install VC++ 2015.
Thus having both VC++ 2012 and VC++ 2017 should be enough to have the STUSB4500 GUI to work properly.
When the Nucleo board is ready, the LED2 must be blinking. If it is not blinking, there is an hardware issue, and the GUI application will not be able to connect to it.
Download Links:
https://www.microsoft.com/en-us/download/details.aspx?id=30679
https://www.microsoft.com/en-us/download/details.aspx?id=53587
https://aka.ms/vs/15/release/vc_redist.x86.exe
2019-03-13 04:13 PM
All I remember is that I installed the 32 bit version when given the option, what year it was, I cant say. right now I dont have access to that computer.
2019-03-13 05:04 PM
Thanks for this. With 1.07, board not found but HwCheckUtility 1.0.0 found my ISC005V1. With 1.08, I can now see the board.