Hi,
I compiled the firmware before to have AS5047D hardware SPI. I can not remember having any problems with it. Now I tried it again with an Ubuntu based Linux (Pop OS) VM. I downloaded the toolchain from https://developer.arm.com/tools-and-software/open-source-software/develo... unpacked it and added the /bin to the PATH. I edited the conf_general.h and the compile went through without errors, but after uploading the .bin file to the VESC, it is no longer accessible through USB. I already ordered a ST-Link, but I will need a working firmware. What do I need to do to get a working enviroment again? Thanks in advance!
Since there are multiple threads with this problem now: I was using gcc-arm-none-eabi-9-2019-q4-major-x86-64-linux.tar.bz before and it was working. I am installing it now and wait for my ST-Link to arrive.
Got my ST-Link and found my Ubuntu-VM in my backup. I used the VM to compile the firmware, uploaded it with the ST-Link Utility and the VESC is up and running again.
Hello, I have the problem that vesc tool does not let me load the new fraimware, I already ordered the st-link, but I have neither the firmware nor the VM to compile it, for two tell me where to download the firmware and the VM?