-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
system cannot find the file specified... #156
Comments
I believe you have encountered this issue: |
Thanks for the response but no, I removed space in path and still have error. Anyway thinking about it, it was working fine, with space in folder name, until I updated to latest version of Minicore.. |
A batch script (delete_merged_output.bat) was introduced in the latest version of MiniCore (v2.0.7), and this is what's causing the issue. The script is there so it's easier to look through the assembly output of your program if you wish to do so. I'm not sure if @SpenceKonde has seen this before or not. After all, it's his script. If there isn't a proper fix for this I'll probably remove the assembly output option for Windows until this is sorted out. |
I removed delete_merged_output.bat from megaTinyCore quite a while ago, after I discovered that the IDE wasn't generating merged output files at all for boards where a bootloader wasn't in use, and there was no need for it. But MiniCore does seem to be generating them (so does ATTinyCore - I haven't dug into why yet). But the problem reproduces for me too. It looks to me like the problem is that you're trying to do:
But the file present isn't called BlinkCopy.ino_atmega328p_16000000L.lst , it's called BlinkCopy.ino.lst |
@SpenceKonde thanks for the clue! turns out the .lst file is incorrectly named when compiling on a Windows computer. https://github.com/MCUdude/MiniCore/blob/master/avr/platform.txt#L78 @ZL1CVD try to replace
if so, I'll push the fix very soon |
Yup, that fixes it! And yes, I have a sketch called BlinkCopy - an exact copy of blink, saved outside of examples just so I can export compiled binary (lol - Most recently it was relevant for fixing the names of my exported .hex and .lst files; I now wrap up every tools submenu option that effects the compiled binary, ex: BlinkCopy.ino.t1614.20c0.u5V.mD0.hex (ATtiny1614 at 20 MHz clocked from internal, with 5V baud rate correction and millis clocked from TCD0) - I'm sure you can guess how the event that prompted that change went down... but for a while kept having stupid situations where the name came out mangled, with {build.somethingorother} in it though I also often use it for looking at how the millis ISR comes out. The separate names are also super useful when you're comparing the output of the same sketch compiled with near-identical options) |
Oh - and you need to update version in platform.txt |
Hi all. "{build.path}/{build.project_name}.lst" with "{build.path}/{build.project_name}{build.mcu}{build.f_cpu}.lst" in file plaform.txt does indeed fix the problem. Huge thanks to all!! |
Something wrong with latest boards.txt (I think). Just upgraded to latest version via boards manager & compiler is not throwing up a file error when I export HEX :
Sketch uses 12822 bytes (39%) of program storage space. Maximum is 32768 bytes.
Global variables use 261 bytes (12%) of dynamic memory, leaving 1787 bytes for local variables. Maximum is 2048 bytes.
C:\Users\Chris\AppData\Local\Arduino15\packages\MiniCore\hardware\avr\2.0.7/scripts/delete_merged_output.bat false C:\Users\Chris\AppData\Local\Temp\arduino_build_922559\CIV-SMeter.ino.with_bootloader.hex
cmd /C copy C:\Users\Chris\AppData\Local\Temp\arduino_build_922559\CIV-SMeter.ino_atmega328pb_16000000L.lst E:\PRODUCTS\CAT Icom\CIV-SMeter
The system cannot find the file specified.
Error compiling.
I'm compiling 328PB with LTO enabled, no EEPROM retained, no bootloader and exporting HEX via Sketch >Export Compiled Binary.
Confirm the HEX does exist in the temp folder, its just not being found & copied across to dev folder in Windows 7. worked fine in prior versions..
The text was updated successfully, but these errors were encountered: