Over and over. I tried running the command manually and it just exits and does pretty much nothing.
I disabled the first 8 lines of the rusefi.mk and obviously, got the same error as the people that were not running git submodule update --init
BTW, before that I got:
C:\Users\User\Downloads\oldrusefi\efi\firmware>git submodule update --init
fatal: not a git repository (or any parent up to mount point /cygdrive)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Over and over. I tried running the command manually and it just exits and does pretty much nothing.
I disabled the first 8 lines of the rusefi.mk and obviously, got the same error as the people that were not running git submodule update --init
BTW, before that I got:
C:\Users\User\Downloads\oldrusefi\efi\firmware>git submodule update --init
fatal: not a git repository (or any parent up to mount point /cygdrive)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
If you want to compile without having a git folder, you have to manually download the chibios and chibios contrib and put in the folders.
Have been fighting the firmware myself for a while.
Over and over. I tried running the command manually and it just exits and does pretty much nothing.
I disabled the first 8 lines of the rusefi.mk and obviously, got the same error as the people that were not running git submodule update --init
BTW, before that I got:
C:\Users\User\Downloads\oldrusefi\efi\firmware>git submodule update --init
fatal: not a git repository (or any parent up to mount point /cygdrive)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
If you want to compile without having a git folder, you have to manually download the chibios and chibios contrib and put in the folders.
Have been fighting the firmware myself for a while.
I mean I'd compile it with a git folder... but how do I create it?
I'll give what you said a shot, thanks!
**EDIT** IT WORKED! THANK YOU!
**EDIT 2 **
The fix allowed me to start compiling, but I keep failing to compile since I apparently don't have "stm32_gpio.h", which is supposed to be included in the GCC toolchain I think?
Over and over. I tried running the command manually and it just exits and does pretty much nothing.
I disabled the first 8 lines of the rusefi.mk and obviously, got the same error as the people that were not running git submodule update --init
BTW, before that I got:
C:\Users\User\Downloads\oldrusefi\efi\firmware>git submodule update --init
fatal: not a git repository (or any parent up to mount point /cygdrive)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
If you want to compile without having a git folder, you have to manually download the chibios and chibios contrib and put in the folders.
Have been fighting the firmware myself for a while.
I mean I'd compile it with a git folder... but how do I create it?
I'll give what you said a shot, thanks!
**EDIT** IT WORKED! THANK YOU!
**EDIT 2 **
The fix allowed me to start compiling, but I keep failing to compile since I apparently don't have "stm32_gpio.h", which is supposed to be included in the GCC toolchain I think?
Over and over. I tried running the command manually and it just exits and does pretty much nothing.
I disabled the first 8 lines of the rusefi.mk and obviously, got the same error as the people that were not running git submodule update --init
BTW, before that I got:
C:\Users\User\Downloads\oldrusefi\efi\firmware>git submodule update --init
fatal: not a git repository (or any parent up to mount point /cygdrive)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
If you want to compile without having a git folder, you have to manually download the chibios and chibios contrib and put in the folders.
Have been fighting the firmware myself for a while.
I mean I'd compile it with a git folder... but how do I create it?
I'll give what you said a shot, thanks!
**EDIT** IT WORKED! THANK YOU!
**EDIT 2 **
The fix allowed me to start compiling, but I keep failing to compile since I apparently don't have "stm32_gpio.h", which is supposed to be included in the GCC toolchain I think?
Download Git for Windows.
I have still never gotten it to compile with command line. It always end in some error.
**EDIT 2 **
The fix allowed me to start compiling, but I keep failing to compile since I apparently don't have "stm32_gpio.h", which is supposed to be included in the GCC toolchain I think?
No, stm32_gpio.h is not part of compiler - I suspect your older? updated? folder has mismatched version of ChibiOS maybe?
git submodule update --recursive --remote
could be helpful to update submodule since there was ChibiOS migration recently
**EDIT 2 **
The fix allowed me to start compiling, but I keep failing to compile since I apparently don't have "stm32_gpio.h", which is supposed to be included in the GCC toolchain I think?
No, stm32_gpio.h is not part of compiler - I suspect your older? updated? folder has mismatched version of ChibiOS maybe?
git submodule update --recursive --remote
could be helpful to update submodule since there was ChibiOS migration recently
The link to ChibiOS on your Github takes me to the ChibiOS fork... on your Github, I downloaded that and put it in ChibiOS (and downloaded Contrib and put it there too) and apaprently I'm missing stm32_gpio.
The link to ChibiOS on your Github takes me to the ChibiOS fork... on your Github, I downloaded that and put it in ChibiOS (and downloaded Contrib and put it there too) and apaprently I'm missing stm32_gpio.
This does not sound like the way you are supposed to be using github. I would recommend against manually resolving submodules put get
git submodule update --init
or maybe
git submodule update --recursive --remote
Also, why do you need to compile - why would pre-compiled binaries not work for you?
The link to ChibiOS on your Github takes me to the ChibiOS fork... on your Github, I downloaded that and put it in ChibiOS (and downloaded Contrib and put it there too) and apaprently I'm missing stm32_gpio.
This does not sound like the way you are supposed to be using github. I would recommend against manually resolving submodules put get
git submodule update --init
or maybe
git submodule update --recursive --remote
Also, why do you need to compile - why would pre-compiled binaries not work for you?
As I posted before, git submodule update --init just does evidently nothing and returns to cmd without apparently doing anything
the other command hasn't been mentioned and I'll try it out now:
errorrusefi.PNG (12 KiB) Viewed 67062 times
I want to compile so I can start fiddling around with it. I have a Github repo of my own ( https://github.com/ElDominio ) and I like to learn about this, and seeing as rusEFI uses an OS I'd like to learn about how they work, especially in an ECU
The link to ChibiOS on your Github takes me to the ChibiOS fork... on your Github, I downloaded that and put it in ChibiOS (and downloaded Contrib and put it there too) and apaprently I'm missing stm32_gpio.
This does not sound like the way you are supposed to be using github. I would recommend against manually resolving submodules put get
git submodule update --init
or maybe
git submodule update --recursive --remote
Also, why do you need to compile - why would pre-compiled binaries not work for you?
As I posted before, git submodule update --init just does evidently nothing and returns to cmd without apparently doing anything
the other command hasn't been mentioned and I'll try it out now:
errorrusefi.PNG
I want to compile so I can start fiddling around with it. I have a Github repo of my own ( https://github.com/ElDominio ) and I like to learn about this, and seeing as rusEFI uses an OS I'd like to learn about how they work, especially in an ECU
I do not see the ".git" folder. I suspect you did not clone, but instead downloaded from the web page. Try obtaining the folder with git instead of the web page download.
I believe the commands will be something like this.
this makes me think your chibios is wrong. since chibios is supposed to be downloaded automatically I wonder what else is wrong. So, Where did you get these source codes how exactly? How did you get chibios submodule exactly?
I'm familiar with IAR and STM32CubeIDE, not gnu toolchain.
Now I want to modify some GPIO and Timer setting of your firmware and compile it.
Below is the first headache of make:
I think the best compiler tool is available in linux, Just install a linux on a virtual machine like virtualbox and compile it.
As i had experience, The cygwin sometimes goes unstable especially with lib(s). https://www.youtube.com/watch?v=H3ZQDkpKwQo
You must have installed gcc-arm-none-eabi(v9) in path and maybe some other utility packets(git, make etc)
In Terminal:
$ mkdir retest
$ cd retest
$ git clone https://github.com/rusefi/rusefi.git
$ cd rusefi/
$ git submodule update --init
$ cd firmware/
$ git log --oneline | head
$ make
Then you have "rusefi.bin" in "Build" directory
as far as I remember, git clone takes up too much space and network traffic, downloading unnecessary hardware-related files, datasheets, etc. I don't remember if I managed to find a solution to download it partially ;-(