We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hello.
I'm new to ARM programming. I'm using Keil uVision v5.17.0.0 on Windows 8.1, I have device named STM32 F7 Discovery with STM32F746NGH6 MCU (216 MHz/462 DMIPS). I'v opened demo project File_Demo, built it without errors. When I press "Download (F8)", I get this:
--------------------------- ULINK - Cortex-M Error --------------------------- No ULINK Device found --------------------------- OK ---------------------------
and then:
--------------------------- µVision --------------------------- Error: Flash Download failed - Target DLL has been cancelled
--------------------------- OK ---------------------------
Just some facts:
1) UL_Configure. This did not help:
c:\Keil_v5\ARM\ULINK\Utilities>UL2_Configure B0 ULINK2 Configure Utility V1.0
Error: ULINK not found!
2) Project options for target -> Debug -> tryed all available debuggers - the same result, no one worked. Default setting was ULINK2/ME Cortex Debugger
3) www.keil.com/.../ulink2_trblsh_hwcheck.htm this hardware checklist not passed in my case, but not in the way described in above article - it is okay with leds, but I dont see my device in HID section of Windows Device Manager, it is listed in USB Controllers section as "USB Composite device". There is nothing about this issue in the article.
4) When I connect device to USB port of my PC, it is recognized as USB external flash or hard drive, named "DIS_F746NG", with some files and permission to read/write available and 1016k of 1032k free.
5) UninstallULINK.exe, then InstallULINK.exe in c:\Keil_v5\ARM\ULINK\ did not help.
And I almost forgot about one thing. The very first time I'v tried to load a project to device, the error was different - something about ST-LINK (I dont remember exactly). After some googling and performing random actions (I'm a beginner, so I dont exactly understand what I am doing, sorry) the error changed to described above. I have updated ST-LINK on device to latest version, I exactly remember that it was some reaction (blinking leds) from the device's side. But now I am unable to do it, when I press "Device Connect" in ST-Link Upgrade program, it says:
--------------------------- ST-LinkUpgrade --------------------------- Communication error with ST-Link.
Try to start it. --------------------------- OK ---------------------------
Please help, I am totally confused with all that.
Start with the fact you don't actually have an ULINK for it to find.
You have an ST-LINK.
Try the connect under reset option, and make sure you have selected SWD mode
On another computer, with my device and USB cable, the program "STM32 ST-LINK Utility" can see device, connect to it, show device memory, etc. I didn't installed Keil uVision on this (working OK with "...Utility") computer, but I am almost certain about some USB problem on my computer (where "...Utility" does not work. I cannot "connect under reset" and/or choose SWD mode because these settings are inactive, because of "No ST-LINK detected error"! I also found trace.log file in ST-LINK Utility's folder, it contains errors like that:
cErrLog::SetLogTraceOn STLinkUSBDriver.dll loaded USB communication error (65657) after target cmd F1 80 00 00 00 00 00 00 00 00 ST-Link get version failure
The next step will be reinstalling Windows, I suppose... ((
now trace.log looks like this:
W at 0xe0042004: 0x00000000 cErrLog::SetLogTraceOn STLinkUSBDriver.dll loaded No ST-LINK device detected on the USB
Reinstalling Windows won't address hardware issues, not had cause here to reinstall windows in years.
Try different USB ports/cables.
Try installing ST's most current drivers, and insuring that the DLLs that Keil is using are the most current.
Check the driver versions in Device Manager
Review Intel vs AMD, Windows versions, or other difference between systems that would contribute to one working, and the other not.
I reinstalled Windows, and now it works in ST-Link Utility. It will most likely work in Keil, too. I will install Keil and post a message about results.
I have found the issue. It was YandexDisk application, that created virtual drive in the system. After installing it the error began to appear again. Very bad news, because I use it in my work for synchronization data with cloud. I suspected this application before reinstalling Windows, because there were some advices in the web about Daemon Tools, that does actually the same thing. But uninstall of YandexDisk does not help. I will try now to compare System Restore Points before and after YD, maybe the the true reason will become clear.