Thanks for the report, could you also attach the log from the Arduino IDE with the File > Preferences > Verbose Output During "Compile" Enabled?

Can you also try adding a local board.txt to your project (vMicro > Add Code > Add Local Board.txt) and pasting in the attached overrides, and see if this then compiles in Visual Micro?

Quote:


Yes please, and it is just capturing the output, with the additional logging enabled from File > Preferences > Show Verbose Output during "Compile" checked.

The -g0 flag we have changed it to will affect debugging, but once we have reviewed the Arduino IDE log from the same machine hopefully we will be able to understand the true root cause of the issue (currently we cannot replicate the issue on our machines).

It's not letting me upload the file...


"With the file ArduinoIDEOutputForUnoR4WiFi.txt (0 KB) you exceed the maximum allowed upload directory volume."

I emailed you the file instead...

Thanks for uploading the log, and we have fixed the issue preventing the .txt file from uploading.

Would you be able to rename the attached file from .txt to .bat and run it on your machine?

If you can attach the output as a text file or attach an image of the console output it would be greatly appreciated.

It will provide further output about the locale and windows version which will help us to identify exactly where the failure is coming from so we can ensure we can validate any fixes against the issue.

Thanks for the log and I believe the windows version shown here represents Win11, just not clearly with "11" as we would expect.

I have updated another machine to this Windows build and the same codepage etc, but still cannot repro to investigate further.

When you have chance would you mind trying:
1) Disable any AntiVirus Real Time Scanning on your machine
2) Open the failing project and run Build > Clean Solution
3) Ensure the -g0 overrides are commented out in the board.txt (just put # at the start of the line)
4) Build the project again
5) Re-enable your AV protection

Let us know if this yields a different result when you have had chance.

Agree this is very frustrating, and if I could replicate the issue it would make it easier to isolate the root cause, however it seems very environmental (and a lot of moving parts).

Do the same commands that fail in the build output give the same result when run via CMD? (Example commands from your previous log attached)

Thanks for trying, and apologies for not noticing the quoting issue and potential for the output folder to exist.

The attached file can be renamed as *.bat, or run the two commands within separately in the same CMD session, this should hopefully give the same error that we see in vMicro....

I am now getting a cosistent error, after playing around with the VSMicro debugger options. Tried them all and reset back to off. Now nothing builds (including with the overrides you provided earlier). I think I have something really honked up now...

New output file attached...

I still get the same error documented in Output-MicroBuild.txt sent in my previous message.

Is the arm-none-eabi-gcc the correct compiler for the board?

Overrides didn't work.
New project has same problem.
This new problem started when I messed around with the VMicro+Debugger+Debug: Off/Serial/Arduino/Hardware and back to Off. Like there is some garbage left somewhere that is not being cleaned up (?).