free pascal pi pico. can't open executable. ( .elf )

[jb007]

Hi,

first checked this side for this error, but nothing found.

The error just apeared. Checked multiple programms, same error.

e.q.:

Compile Project, Mode: Raspberry Pi Pico, OS: embedded, CPU: arm, Target: C:\Users\cobal\OneDrive\projects Laz Pico\pico-fpcexamples-main\pico-fpcexamples-main\i2c_scan\bin\i2c_scan.elf: Exit code 1, Errors: 1, Hints: 2
Hint: Start of reading config file C:\fpcLaz_Pico\fpc\bin\x86_64-win64\fpc.cfg
Hint: End of reading config file C:\fpcLaz_Pico\fpc\bin\x86_64-win64\fpc.cfg
Verbose: Free Pascal Compiler version 3.3.1-9929-g8d63a1ddfd [2022/01/18] for arm
Verbose: Copyright (c) 1993-2022 by Florian Klaempfl and others
Verbose: Target OS: Embedded
Verbose: Compiling i2c_scan.lpr
Verbose: Assembling i2c_scan
Verbose: Linking C:\Users\cobal\OneDrive\projects Laz Pico\pico-fpcexamples-main\pico-fpcexamples-main\i2c_scan\bin\i2c_scan
i2c_scan.lpr(57,0) Error: Can't open executable "C:\Users\cobal\OneDrive\projects Laz Pico\pico-fpcexamples-main\pico-fpcexamples-main\i2c_scan\bin\i2c_scan.elf"
Verbose: Compilation aborted
Verbose: C:\fpcLaz_Pico\fpc\bin\x86_64-win64\ppcrossarm.exe returned an error exitcode

Things worked before...


Checked the directory:

Tnx in advance! Marcel

[TRon]

Does it work when you (cross) compile on a local drive ?

[AlexTP]

Verbose: Free Pascal Compiler version 3.3.1-9929-g8d63a1ddfd [2022/01/18] for arm

It is too old 3.3, it's better to update to last Git version.

[cdbc]

Hi
I've seen the compiler write this: "Can't open executable", before...
It was when I accidently had the app running for test in a console-window, so it was locked for the compiler to write to...
Could that be it?
Regards Benny

[TRon]

There are actually two separate sins:
- compiling on a 3th party (external) filesystem
- using spaces in a project name/path

Something to do with reaping and sowing if I remember correctly 

[jb007]

Tnx for all your replies!

As said before, it worked, don't know what I may have done.
I just hadn't use lac/fpc for a few weeks.


Got it working finaly, here a brief story:

Does it work when you (cross) compile on a local drive ?

Done that, but same error!

Verbose: Free Pascal Compiler version 3.3.1-9929-g8d63a1ddfd [2022/01/18] for arm

It is too old 3.3, it's better to update to last Git version.

Reinstalled, and tried compile from onedrive-dir an local-dir: same error

There are actually two separate sins:
- compiling on a 3th party (external) filesystem
- using spaces in a project name/path

Something to do with reaping and sowing if I remember correctly 

Next I. made a new project dir on local C:\picoProjects
A path WITHOUT spaces: no errors!


I'm very happy I can continue with coding my pico!

Tnx again!



For those interested: made a pcb with a pico attached on it.
For my rc diy truck, to control all the light stuff, like ws2812b-bars and ws2812b-'matrixes'and regular (power) leds.
https://www.youtube.com/playlist?list=PLcCKmeWXkrzRoul43A6f0xf8baJPggiu0

[dbannon]

I'd really like to be wrong here but what I have done with the Pico required me to use a special version of FPC 3.2.2 that had been patched by Michael and available via fpcupdeluxe ??

I'd hope Michael's patches had made it into FPC main but not seen any evidence they had.

But I do also like TRon's answer .....

Davo

[jb007]

Made also a new fresh ( spaceless ) path on OneDrive and things work fine there also!

[dbannon]

Excellent !

JB, just for the record, you are running FPC main here, is that just a direct install of main without any patches applied ?  Or did you install using FPCUPDELUXE (which I suspect puts Michael's patches on as you install) ?

David

[jb007]

Hi,

previous install and current install ( LAZ/fpc) are done by using fpcupdeluxe.

From the very start of LAZ/fpc-pico ( last year ) I'm using a dedicated projects folder ( path ).
There I placed the  'michaels' examples-folder and from that folder I also create new projects.
( things worked fine, till some days ago )

Have a second 'independend' installation of LAZ/fpc for windows applications.

All the time worked with oneDrive, but with with a local oneDrive folder. This folder is also stored solid on my pc.

I don't know anything and I'm not aware of Micheal's patches.

Have to find out what it's all about.

Marcel