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.
Is there a known solution for the L6002U compile error when using different disk drives?
For example, if anything in the options for target (such as output or listings folders) is set to a valid location on my drive H: I get the L6002U error. But if I set them to the I: drive, there is no L6002U error. As far as I can tell, the drives access permissions are the same.
A search of this forum gives other people with L6002U errors, all of which are unsolved.
The failed drive: Network drive, NTFS file system, Windows 7, Trend Micro anti-virus
Keil does not create H:\Desktop\foo\output\stm32f4xx_it.o
If I copy that file to the drive to the proper folder, then Keil immediately deletes the file when the rebuild button is pressed and says it cannot find that file
The drives that work: Network drive, NTFS file system, Windows 7, Trend Micro anti-virus
Keil creates <any other drive>.\output\stm32f4xx_it.o and then immediately uses that file.
Same or different network server? Time correctly synchronized if different?
Windows says they are on the same file server, but I haven't spoken to the networking people about Keil's issue. The time stamps on files on both drives are identical.
The joys of Windows IT
It's hard to know who to blame here, I've seen people have problems with Microsoft CHM help files across windows shares, so this could just as likely be something retarded Microsoft is doing, rather than Keil. If the OS throws an "access denied" or "invalid parameter" type error, it's pretty hard for an application to get a specific reason.
The best way to get Keil, or anyone, to fix these kind of issues is to be able to demonstrate them repeatably, and with clear conditions.
I would be tempted to disable the Anti-Virus stuff because that's prone to foul things up in a myriad of ways, all up and down the file system and filter stacks. Try also with different map/share combinations, and the access rights ascribed to each.