Windows tool chain problem

Support
1

Hi,

I recently get myself an Odrive. I’ve managed to get it up and running quite seamless with hoverboard motor, it works impressive.
But now I would like to do some changes in code, to make Odrive better suit my needs.
I’ve gone through a lot of problems in setting up toolchain on Win7, but finally I’ve got stuck.
I get following problem while trying to compile:

> Executing task in folder Firmware: make <

 [                    ETA~=??? Remaining=80 Active=4                     ]   0%U
nable to retrieve WOW64 info
tup error: failed to inject dll: No such file or directory
 *** Command ID=335 failed: arm-none-eabi-gcc -std=c99 -c Board/v3/Drivers/STM32
F4xx_HAL_Driver/Src\stm32f4xx_hal_cortex.c -DHW_VERSION_MAJOR=3 -DHW_VERSION_MIN

Any help would be appreciated.

2

Please do: make -v and arm-none-eabi-gcc --version

Also, are you on 32 or 64 bit Windows 7? Doesn’t look like Tup is guaranteed to work with 32 bit systems. https://github.com/gittup/gittup/issues/11

3

Thanks for quick answer, here are versions:

GNU Make 3.81

arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1
20170904 (release) [ARM/embedded-7-branch revision 255204]

The system is 64 bit.

4

I had the same exact problem,
Unable to retrieve WOW64 info
I tracked my issue down to McAFee removing tup32det.exe
I backed down from the latest version of tup to 7.8 and McAFee didn’t try and delete.
Now I build successfully

2 Likes
5

Just in case it helps anyone else, I was also having this same issue (antivirus removing tup32det.exe upon running ‘make’), but I had to revert back to v0.7.6 to fix it (v0.7.8 was still giving me the same issue).

6

It seems that I have the same issue.

Can you confirm that the only Tup files you have (with version 0.7.6) are:

  • tup.1
  • tup.exe
  • tup32detec.exe
  • tup-dllinject.dll
  • tup-dllinject32.dll

My build output:
C:\Users\julien\source\repos\ODrive\Firmware (master -> origin)
λ make
100%
8) [1.699s] arm-none-eabi-gcc -std=c99 -c Board/v3/Drivers/STM32F4xx_HAL_Driver/Src\stm32f4xx_ll_usb.c -DHW_VERSION_MAJOR=3 -DHW_VERSION_MINOR=6 -DHW_VERSION_VOLTAGE=24 -DUSB_PROTOCOL_NATIVE -DUART_PROTOCOL_ASCII -D__weak=“attribute((weak))” -D__packed=“attribute((packed))” -DUSE_HAL_DRIVER -DSTM32F405xx -mthumb -mcpu=cortex-m4 -mfpu=fpv4-sp-d16 -mfloat-abi=hard -Wall -Wdouble-promotion -Wfloat-conversion -fdata-sections -ffunction-sections -O2 -ffast-math -fno-finite-math-only -IBoard/v3/Middlewares/Third_Party/FreeRTOS/Source/portable/GCC/ARM_CM4F -IBoard/v3/Middlewares/Third_Party/FreeRTOS/Source/include -IBoard/v3/Middlewares/Third_Party/FreeRTOS/Source/CMSIS_RTOS -IBoard/v3/Middlewares/ST/STM32_USB_Device_Library/Core/Inc -IBoard/v3/Middlewares/ST/STM32_USB_Device_Library/Class/CDC/Inc -IBoard/v3/Drivers/STM32F4xx_HAL_Driver/Inc -IBoard/v3/Drivers/STM32F4xx_HAL_Driver/Inc/Legacy -IBoard/v3/Drivers/CMSIS/Device/ST/STM32F4xx/Include -IBoard/v3/Drivers/CMSIS/Include -IBoard/v3/Inc -I. -IDrivers/DRV8301 -o build/obj\Board_v3_Drivers_STM32F4xx_HAL_Driver_Src_stm32f4xx_ll_usb.c.o
Board/v3/Drivers/STM32F4xx_HAL_Driver/Src\stm32f4xx_ll_usb.c: In function ‘USB_WritePacket’:
Board/v3/Drivers/STM32F4xx_HAL_Driver/Src\stm32f4xx_ll_usb.c:886:7: warning: ‘packed’ attribute ignored for type ‘uint32_t *’ {aka ‘long unsigned int *’} [-Wattributes]
886 | USBx_DFIFO(ch_ep_num) = *((__packed uint32_t *)src);
| ^~~~~~~~~~
Board/v3/Drivers/STM32F4xx_HAL_Driver/Src\stm32f4xx_ll_usb.c: In function ‘USB_ReadPacket’:
Board/v3/Drivers/STM32F4xx_HAL_Driver/Src\stm32f4xx_ll_usb.c:912:5: warning: ‘packed’ attribute ignored for type ‘uint32_t *’ {aka ‘long unsigned int *’} [-Wattributes]
912 | *(__packed uint32_t *)dest = USBx_DFIFO(0U);
| ^
[ ETA~=4s Remaining=33 Active=8 ] 60%tup error: failed to inject dll: No such file or directory
*** Command ID=501 failed: python …/tools/odrive/version.py --output build\version.h
[ ETA~=3s Remaining=26 Active=0 ] 69%
*** tup: 1 job failed.
make: *** [all] Erreur 1

versions:
tup v0.7.6
arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 9-2019-q4-major) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]
GNU gdb (GNU Tools for Arm Embedded Processors 9-2019-q4-major) 8.3.0.20190709-git
xPack OpenOCD, 64-bit Open On-Chip Debugger 0.10.0+dev (2019-07-17-11:28)
Python 3.7.4

Do you have by any chance a hint on what is going wrong?

7

I don’t think GCC 9 works with the master branch.

8

I have the same trouble,and my solution is place my “tup-latest” folder in other Disk(except C:/)