cancel
Showing results for 
Search instead for 
Did you mean: 

CubeIDE fail to compile

NVETE.1
Associate II

Hi everyone!

I'm new to CubeIDE. I've just installed version 1.6.1 on Windows 10 and I find myself in a situation...

At my first attempt to make to blink the PC13 Led, the compiler cannot complie those lines and bring the following error:

c:\st\stm32cubeide_1.6.1\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_1.5.0.202011040924\tools\arm-none-eabi\bin\ld.exe: cannot open linker script file C:\Users\NÉXTOR\STM32CubeIDE\workspace_1.6.1\Blink3\STM32F103C8TX_FLASH.ld: No such file or directory

collect2.exe: error: ld returned 1 exit status

I've already checked the following:

Those paths and exists, all if them

The STM32F103C8TX_FLASH.ld file is in the path indicated above and it's visible in the project explorer window.

I tried a couple of times and I tried in a second workspace to no avail.

Well that's it.

I wonder if you could help me with this.

Thanks in advance.

By the way, my name is Nestor and I'm from Argentina.

1 ACCEPTED SOLUTION

Accepted Solutions
Cartu38 OpenDev
Lead II

Could be due to special character usage as part of workspace path. Myself whatever tool I would avoid such. 'É' usage (part of user name 'NÉXTOR') is not recommended according to me.

Have a try with another workspace location and let us known if working

View solution in original post

4 REPLIES 4
BParh.1
Senior III

Could it be due to file permission issue? Please double check that the linker file permission setting allow CubeIDE to access.

Cartu38 OpenDev
Lead II

Could be due to special character usage as part of workspace path. Myself whatever tool I would avoid such. 'É' usage (part of user name 'NÉXTOR') is not recommended according to me.

Have a try with another workspace location and let us known if working

Not sure about permission as linker file is only read not written as part of project build process

Hi Cartu38!

I've followed your indication, switched to a new workspace outside the path "with the special character" and inmediately worked fine! :grinning_face:

I'm back on track.

Thank you very much for your help! :ok_hand: