[SOLVED] Paneldue firmware compile error

jay_s_uk

Download or git clone the dev branch of RRFLibraries into C:\Eclipse.

64bit

@jay_s_uk
Already been done.
Downloaded RRFLibraries-3.3-dev whatever its called.
Renamed it to RRFLibraries
Put it in Eclipse and even under the firmware tab.

It wont come up in Eclipse when I try to "open project" either, so im going to look into that more.

jay_s_uk

@64bit the project explorer should look like this

64bit

@jay_s_uk

Making progress I guess.

Now Im stuck with no .bin being output.

make --no-print-directory post-build
Generating binary
"/arm-none-eabi-objcopy" -O binary "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3.elf" "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3-nologo.bin" && cat "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3-nologo.bin" "C:/Eclipse/PanelDueFirmware/SplashScreens/SplashScreen-Duet3D-480x272.bin" >"C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3.bin"
c:/windows-build-tools/bin/sh: C:/arm-none-eabi-objcopy: not found

jay_s_uk

@64bit yea, i just got that error. will look into it and report back

jay_s_uk

@64bit what have you got in C:\windows-build-tools?
I had 2 folders and had to tidy it up. works ok for me now.

64bit

@jay_s_uk

I found objcopy.exe in my GNU Embedded tools. So I ran the following from the cmd prompt

C:\Program Files (x86)\GNU Arm Embedded Toolchain\10 2020-q4-major\arm-none-eabi\bin>objcopy.exe -O binary "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3.elf" "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3-nologo.bin"

Output was a no logo bin that I have now flashed to the paneldue. after a reset it opened right up.

A bit of ass pain, but it worked.

64bit

@jay_s_uk

jay_s_uk

@64bit

can you try going to Windows -> Preferences -> C/C++ -> Build -> Build Variables and click "Add..."

set the name to "ArmGccPath", then change to directory and navigate to C:\Program Files (x86)\GNU Arm Embedded Toolchain\10 2020-q4-major\arm-none-eabi\bin

Then apply and close eclipse. reopen it and try and build

64bit

@jay_s_uk said in Paneldue firmware compile error:

C:\Program Files (x86)\GNU Arm Embedded Toolchain\10 2020-q4-major\arm-none-eabi\bin

Must be an issue in the makefile?

"C:\Program Files (x86)\GNU Arm Embedded Toolchain\10 2020-q4-major\arm-none-eabi\bin/arm-none-eabi-objcopy" -O binary "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3.elf" "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3-nologo.bin" && cat "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3-nologo.bin" "C:/Eclipse/PanelDueFirmware/SplashScreens/SplashScreen-Duet3D-480x272.bin" >"C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3.bin"
c:/windows-build-tools/bin/sh: C:\Program Files (x86)\GNU Arm Embedded Toolchain\10 2020-q4-major\arm-none-eabi\bin/arm-none-eabi-objcopy: not found
make[1]: [makefile:94: post-build] Error 127 (ignored)

jay_s_uk

@64bit
It compiles ok for me here

64bit

@jay_s_uk

I dont understand where the forward slash is coming from.

I mean, I can keep just using the command line to run objcopy. I just wish it wasnt screwed up.

What version of the GNU Arm Embedded Toolchain are you using?

64bit

@jay_s_uk

SOLVED

make --no-print-directory post-build
Generating binary
"C:\Program Files (x86)\GNU Arm Embedded Toolchain\10 2020-q4-major\arm-none-eabi\bin/arm-none-eabi-objcopy" -O binary "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3.elf" "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3-nologo.bin" && cat "C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3-nologo.bin" "C:/Eclipse/PanelDueFirmware/SplashScreens/SplashScreen-Duet3D-480x272.bin" >"C:/Eclipse/PanelDueFirmware/Release-v3-4.3/PanelDueFirmware-v3-4.3.bin"

copied and renamed objcopy.exe to arm-none-eabi-objcopy.exe
File compiles properly now into both w/logo and no-logo files.

R006

@jay_s_uk i got the same error and try as @64bit mentioned in the post but its not working for me.
i an waiting your reply @jay_s_uk