Bootloader compile ARM-10.2.1 GCC via Cygwin drive chibiOS2.6.6

[GI101]

The GitHub instructions as to configure VESC boot loader via ARM10.2.1 is not fully compatible with chibiOS2.6.6 zip download as bldc-bootloader-master zip. The newer OS3.0.5 has a completely different folder structure. Hence forth I kept the older OS2.6.6 project thinking more compatible with the older BL 407 build.

Was chibiOS3.0.5 ever tested with the VESC BootLoader by anyone in the VESC project?

Replaced Makefile (CHIBIOS) path (../..) with { /cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6 } gives full Eclipse IDE clean "No errors". Also specified the GCC compiler Makefile path:

TRGT = arm-elf-

TRGT = /cygdrive/c/ti/ccs910/ccs/tools/compiler/gcc-arm-none-eabi-10-2020-q4-major/bin/arm-none-eabi- CC = $(TRGT)gcc CPPC = $(TRGT)g++

Why does GCC seem to start a compile of the file names then error out?

13:48:09 Build of configuration Default for project ARMCM4-STM32F429-DISCOVERY make -j4 all cygwin warnings: Compiler Options /cygdrive/c/ti/ccs910/ccs/tools/compiler/gcc-arm-none-eabi-10-2020-q4-major/bin/arm-none-eabi-gcc -c -mcpu=cortex-m4 -O2 -ggdb -fomit-frame-pointer -falign-functions=16 -ffunction-sections -fdata-sections -fno-common -Wall -Wextra -Wstrict-prototypes -Wa,-alms=build/lst/ -DCORTEX_USE_FPU=FALSE -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING -MD -MP -MF .dep/build.d -I. -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/common/ARMCMx/CMSIS/include -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/common/ARMCMx -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx/STM32F4xx -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/kernel/include -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/test -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/include -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/platforms/STM32F4xx -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/platforms/STM32 -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/platforms/STM32/GPIOv2 -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/platforms/STM32/I2Cv1 -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/platforms/STM32/OTGv1 -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/platforms/STM32/RTCv2 -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/platforms/STM32/SPIv1 -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/platforms/STM32/TIMv1 -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/hal/platforms/STM32/USARTv1 -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/boards/ST_STM32F429I_DISCOVERY -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/various/devices_lib/accel -I/cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/various main.c -o main.o

mkdir -p build/obj mkdir -p build/lst Compiling crt0.c Compiling vectors.c Compiling chcore.c arm-none-eabi-gcc.exe: error: /cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx/crt0.c: No such file or directory arm-none-eabi-gcc.exe: fatal error: no input files compilation terminated. arm-none-eabi-gcc.exe: error: /cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx/STM32F4xx/vectors.c: No such file or directory arm-none-eabi-gcc.exe: fatal error: no input files compilation terminated. arm-none-eabi-gcc.exe: error: /cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx/chcore.c: No such file or directory /cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx//rules.mk:183: recipe for target 'build/obj/vectors.o' failed make: [build/obj/vectors.o] Error 1 /cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx//rules.mk:183: recipe for target 'build/obj/crt0.o' failed make: Waiting for unfinished jobs.... make: [build/obj/crt0.o] Error 1 arm-none-eabi-gcc.exe: fatal error: no input files compilation terminated. make: [build/obj/chcore.o] Error 1 /cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx//rules.mk:183: recipe for target 'build/obj/chcore.o' failed Compiling chcore_v7m.c arm-none-eabi-gcc.exe: error: /cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx/chcore_v7m.c: No such file or directory arm-none-eabi-gcc.exe: fatal error: no input files compilation terminated. /cygdrive/c/ti/VESC/Boot_Loader/bldc-bootloader-master/ChibiOS_2.6.6/os/ports/GCC/ARMCMx//rules.mk:183: recipe for target 'build/obj/chcore_v7m.o' failed make: *** [build/obj/chcore_v7m.o] Error 1

07:40:25 Build Failed. 9 errors, 0 warnings. (took 764ms)

[GI101]

BTW: I checked via Cygwin console the drive paths fatal error (no input files) actually do exist in makefile paths shown above.

[GI101]

The problem seems to be the ARM10.0 compiler does not return control back to the IDE or is simply missing tool chain directive for Thumb and FPU. Updated Cygwin for ARM10.0 (arm-none-eabi-gcc10.exe) still the root make file even with added include paths or IDE pre-processor CDT managed build controls produce the same missing file nonsense. Oddly the ST32F429 discovery project imported into IDE has no linker control tab or settings but the directives are in the root make file.

Any ideas why the ARM compile is missing tool chain (Thumb/FPU) directives? The No Input files is an ARM10 compiler message while the Cygwin build via i686-pc-cygwin-gcc-10.exe is missing the Thumb/FPU tool chain directives. If I move arm-none-eabi-gcc10.exe into c:/Cygwin/bin directory the same missing input files message occurs. The make file TRGT: path DOS style or /Cygdrive/c/arm-none-eabi-gcc produce the same two issues.

prototypes -Wa,-alms=build/lst/ -DCORTEX_USE_FPU=FALSE -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING