Closed StefanoTesla closed 2 years ago
Remove C:\Users\Tesla\.platformio\packages\toolchain-xtensa32
an retry.
Building in release mode Compiling .pio\build\esp32doit-devkit-v1\src\dome.cpp.o "xtensa-esp32-elf-g++" non \x8a riconosciuto come comando interno o esterno, un programma eseguibile o un file batch.
You have an antivirus installed that interferes with the download, installation and invocation of the toolchain? This is not normal.
Any antivirus
Il gio 6 gen 2022, 22:29 Maximilian Gerhardt @.***> ha scritto:
You have an antivirus installed that interferes with the download, installation and invocation of the toolchain? This is not normal.
— Reply to this email directly, view it on GitHub https://github.com/platformio/platformio-core/issues/4149#issuecomment-1006947976, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWB3IGQU7QSU5JUB5J6BZC3UUYCSJANCNFSM5LL4TW3A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
Finally I found the problem, i delete all content Inside package folder and all .cache folder
And build is ok
Hi,
I am sorry to reopen the issue, but I am having the same problem as @StefanoTesla. I can't find a way to bypass that error. Deleting all content inside package and .cache folder doesn't help. No antivirus, platformio downloads everything but gets stuck on that error. Could anyone give me a hint on what may be going on ?
I'm running the latest version of platformio, my ini config :
[env:ch552]
platform = intel_mcs51
board = ch552
build_flags =
--model-medium
--LC:/Users/mainwire/.platformio/packages/toolchain-sdcc/lib/medium
-IC:
-IC:/Users/mainwire/Documents/PlatformIO/Projects/ch552_controller/src/Driver/inc
-Isrc/PLAT/inc
extra_scripts = link_medium.py
link_medium.py file :
Import("env")
env.Append(LINKFLAGS=["--model-medium"])
**Building in release mode Compiling .pio\build\esp32doit-devkit-v1\src\dome.cpp.o "xtensa-esp32-elf-g++" non \x8a riconosciuto come comando interno o esterno, un programma eseguibile o un file batch.**
You didn't post your ch552
board definition and used absolute pahs from your project, so this is a bit hard to reproduce. When I use a known board with
[env:CH559]
platform = intel_mcs51
board = CH559
build_flags =
--model-medium
--LC:/Users/Max/.platformio/packages/toolchain-sdcc/lib/medium
-IC:
-Isrc/Driver/inc
-Isrc/PLAT/inc
extra_scripts = link_medium.py
and your above script conent, it compiles fine, but complains
at 1: warning 117: unknown compiler option '--LC:/Users/Max/.platformio/packages/toolchain-sdcc/lib/medium' ignored
Since that should be -L
and not --L
. When I correct that, it builds even without warnings. See build logs.
Ah, if you actually use
build_flags =
--model-medium
--LC:/Users/mainwire/.platformio/packages/toolchain-sdcc/lib/medium
-IC:
-IC:/Users/mainwire/Documents/PlatformIO/Projects/ch552_controller/src/Driver/inc
-Isrc/PLAT/inc
extra_scripts = link_medium.py
then that's wrong because there are two spaces in front of extra_scripts
which should not be there. Then that extra_scripts = link_medium.py
is added as a compiler argument, which the compiler thinks is a file to be build. And of course that's not there. Double check your spaces.
You didn't post your
ch552
board definition and used absolute pahs from your project, so this is a bit hard to reproduce. When I use a known board with[env:CH559] platform = intel_mcs51 board = CH559 build_flags = --model-medium --LC:/Users/Max/.platformio/packages/toolchain-sdcc/lib/medium -IC: -Isrc/Driver/inc -Isrc/PLAT/inc extra_scripts = link_medium.py
and your above script conent, it compiles fine, but complains
at 1: warning 117: unknown compiler option '--LC:/Users/Max/.platformio/packages/toolchain-sdcc/lib/medium' ignored
Since that should be
-L
and not--L
. When I correct that, it builds even without warnings. See build logs.
Thank you for answering,
I updated my ini file :
[env:CH559]
platform = intel_mcs51
board = CH559
build_flags =
--model-medium
--LC:%%userprofile%%/.platformio/packages/toolchain-sdcc/lib/medium
-IC:
-Isrc/Driver/inc
-Isrc/PLAT/inc
extra_scripts = C:\Users\mainwire\.platformio\link_medium.py
Here is my board definition : https://pastebin.com/J8HgWyvh The space appeared when I wrote the message, I don't have it in my config file.
I tried to delete .cache and packages again, so far no changes build logs : https://pastebin.com/XhMAL3CB
There is also something odd, vscode isn't accepting the config :
Unable to resolve configuration with compilerPath: "C:/Users/mainwire/.platformio/packages/toolchain-sdcc/bin/sdcc.exe"
And what is the exact error message you're getting? It can't be the same one with xtensa.
This one :
"CC" non \x8a riconosciuto come comando interno o esterno, un programma eseguibile o un file batch.
What do you mean by "can't be the same one with xtensa" ?
In https://github.com/platformio/platformio-core/issues/4149#issuecomment-1935637991 you quoted your error message as xtensa-esp32-elf-g++
.
The error is weird. Can you open a core CLI and post the output of
pio run -t clean
pio run -v -j1
?
I actually tried to use xtensa, but my platformio seems to be ignoring the toolchain :
When using this line : --LC:%%userprofile%%/.platformio/packages/toolchain-xtensa/lib/medium
and saving, no error, but platformio just tries to compile it with sdcc :
CONFIGURATION: https://docs.platformio.org/page/boards/intel_mcs51/CH559.html
PLATFORM: Intel MCS-51 (8051) (2.1.0) > CH559
HARDWARE: CH559 12MHz, 6.25KB RAM, 64KB Flash
PACKAGES:
- toolchain-sdcc @ 1.40200.0 (4.2.0)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
..This is a MCS51 based chip. You absolutely cannot use an XTensa toolchain with this.
In #4149 (comment) you quoted your error message as
xtensa-esp32-elf-g++
.The error is weird. Can you open a core CLI and post the output of
pio run -t clean pio run -v -j1
?
Same result : https://pastebin.com/8xBQBXGc
That is not supposed to happen. CC
should be replaced by sdcc
per builder code. I can also not reproduce your bug on my machine. You should open a bug report in https://github.com/platformio/platform-intel_mcs51/issues
Very well, thank you for taking your time on this ! Do you believe it could be a simple mistake caused by my configs ? Or is it definitely a bug ?
If you don't happen to have executed some export CC="CC"
that would try to override PlatformIO's CC
variable, this should not happen. Also, the bug should happen in the standard config too then, right? E.g., imported https://github.com/platformio/platform-intel_mcs51/tree/develop/examples/native-blink.
Thank you for that link, I will try it one last time
Hi, I am reporting back here because there is something weird I can't explain ; the compilation is working completely fine with an empty/full C file in the project, but is NOT working with an empty/full CPP file. Am I completely missing how the CH559 works ? Or is it a bug ?
Hi @maxgerhardt, I am sorry to ping you, but I am currently unable to find a solution to my problem. It would seem that the CH552G can only be programmed in C. Is there any way to get it to work with C++ files ? Or should I rewrite my entire code in C ?
Hello everyone, I'm building my git hub project in a new fresh formatted pc, I don't understand why I get this error:
All the missing file exist...
No antivirus running