Thanks,I thought you are still using gcc 4.7russian wrote: ↑Sun Feb 10, 2019 4:08 amthe part about 2013 looks to be the problem. Please use current gnu arm 8 or recent gnu arm 7.3yyj876790646 wrote: ↑Sun Feb 10, 2019 2:59 amMy gcc version is cc version 4.7.3 20130312 (release) [ARM/embedded-4_7-branch revision 196615] (GNU Tools for ARM Embedded Processors)
At the moment I am using 7.3.1 20180622
[info] How to compile the firmware
-
- Posts: 11
- Joined: Tue Jan 01, 2019 1:55 am
Re: How to compile the firmware
- NormanAlphaspeed
- Posts: 68
- Joined: Fri Jan 13, 2017 7:15 am
- Location: Puerto Rico
- Contact:
Re: How to compile the firmware
the git submodule update --init does nothing for me, I only get
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:
Over and over. I tried running the command manually and it just exits and does pretty much nothing.C:\Users\User\Downloads\rusefi-master\firmware>make
Invoking "git submodule update --init"
Invoked "git submodule update --init"
rusefi.mk:7: *** Please run 'make' again. Stop.
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).
AlphaX Auto Electronics
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
Re: How to compile the firmware
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.NormanAlphaspeed wrote: ↑Tue Feb 12, 2019 10:00 amthe git submodule update --init does nothing for me, I only getOver and over. I tried running the command manually and it just exits and does pretty much nothing.C:\Users\User\Downloads\rusefi-master\firmware>make
Invoking "git submodule update --init"
Invoked "git submodule update --init"
rusefi.mk:7: *** Please run 'make' again. Stop.
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).
Have been fighting the firmware myself for a while.
- NormanAlphaspeed
- Posts: 68
- Joined: Fri Jan 13, 2017 7:15 am
- Location: Puerto Rico
- Contact:
Re: How to compile the firmware
I mean I'd compile it with a git folder... but how do I create it?960 wrote: ↑Tue Feb 12, 2019 1:50 pmIf you want to compile without having a git folder, you have to manually download the chibios and chibios contrib and put in the folders.NormanAlphaspeed wrote: ↑Tue Feb 12, 2019 10:00 amthe git submodule update --init does nothing for me, I only getOver and over. I tried running the command manually and it just exits and does pretty much nothing.C:\Users\User\Downloads\rusefi-master\firmware>make
Invoking "git submodule update --init"
Invoked "git submodule update --init"
rusefi.mk:7: *** Please run 'make' again. Stop.
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).
Have been fighting the firmware myself for a while.
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?
AlphaX Auto Electronics
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
Re: How to compile the firmware
Download Git for Windows.NormanAlphaspeed wrote: ↑Tue Feb 12, 2019 3:45 pmI mean I'd compile it with a git folder... but how do I create it?960 wrote: ↑Tue Feb 12, 2019 1:50 pmIf you want to compile without having a git folder, you have to manually download the chibios and chibios contrib and put in the folders.NormanAlphaspeed wrote: ↑Tue Feb 12, 2019 10:00 amthe git submodule update --init does nothing for me, I only getOver and over. I tried running the command manually and it just exits and does pretty much nothing.C:\Users\User\Downloads\rusefi-master\firmware>make
Invoking "git submodule update --init"
Invoked "git submodule update --init"
rusefi.mk:7: *** Please run 'make' again. Stop.
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).
Have been fighting the firmware myself for a while.
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?
Re: How to compile the firmware
I have still never gotten it to compile with command line. It always end in some error.960 wrote: ↑Tue Feb 12, 2019 8:38 pmDownload Git for Windows.NormanAlphaspeed wrote: ↑Tue Feb 12, 2019 3:45 pmI mean I'd compile it with a git folder... but how do I create it?960 wrote: ↑Tue Feb 12, 2019 1:50 pmIf you want to compile without having a git folder, you have to manually download the chibios and chibios contrib and put in the folders.NormanAlphaspeed wrote: ↑Tue Feb 12, 2019 10:00 amthe git submodule update --init does nothing for me, I only getOver and over. I tried running the command manually and it just exits and does pretty much nothing.C:\Users\User\Downloads\rusefi-master\firmware>make
Invoking "git submodule update --init"
Invoked "git submodule update --init"
rusefi.mk:7: *** Please run 'make' again. Stop.
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).
Have been fighting the firmware myself for a while.
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?
But ChibiStudio works for me.
- AndreyB
- Site Admin
- Posts: 14381
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: How to compile the firmware
No, stm32_gpio.h is not part of compiler - I suspect your older? updated? folder has mismatched version of ChibiOS maybe?NormanAlphaspeed wrote: ↑Tue Feb 12, 2019 3:45 pm**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?
could be helpful to update submodule since there was ChibiOS migration recentlygit submodule update --recursive --remote
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- NormanAlphaspeed
- Posts: 68
- Joined: Fri Jan 13, 2017 7:15 am
- Location: Puerto Rico
- Contact:
Re: How to compile the firmware
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.russian wrote: ↑Tue Feb 12, 2019 11:25 pmNo, stm32_gpio.h is not part of compiler - I suspect your older? updated? folder has mismatched version of ChibiOS maybe?NormanAlphaspeed wrote: ↑Tue Feb 12, 2019 3:45 pm**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?
could be helpful to update submodule since there was ChibiOS migration recentlygit submodule update --recursive --remote
AlphaX Auto Electronics
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
- AndreyB
- Site Admin
- Posts: 14381
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: How to compile the firmware
This does not sound like the way you are supposed to be using github. I would recommend against manually resolving submodules put getNormanAlphaspeed wrote: ↑Thu Feb 14, 2019 5:49 amThe 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.
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?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- NormanAlphaspeed
- Posts: 68
- Joined: Fri Jan 13, 2017 7:15 am
- Location: Puerto Rico
- Contact:
Re: How to compile the firmware
As I posted before, git submodule update --init just does evidently nothing and returns to cmd without apparently doing anythingrussian wrote: ↑Thu Feb 14, 2019 6:13 amThis does not sound like the way you are supposed to be using github. I would recommend against manually resolving submodules put getNormanAlphaspeed wrote: ↑Thu Feb 14, 2019 5:49 amThe 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.
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 other command hasn't been mentioned and I'll try it out now: 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
AlphaX Auto Electronics
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
Re: How to compile the firmware
You dont have a git folder in firmware? Try CD..NormanAlphaspeed wrote: ↑Thu Feb 14, 2019 7:26 amAs I posted before, git submodule update --init just does evidently nothing and returns to cmd without apparently doing anythingrussian wrote: ↑Thu Feb 14, 2019 6:13 amThis does not sound like the way you are supposed to be using github. I would recommend against manually resolving submodules put getNormanAlphaspeed wrote: ↑Thu Feb 14, 2019 5:49 amThe 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.
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 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
Re: How to compile the firmware
Try the git command(s) from C:\Users\user\Downloads\rusefi-master
Notice this is one folder above "firmware"
Notice this is one folder above "firmware"
Welcome to the friendlier side of internet crazy
- AndreyB
- Site Admin
- Posts: 14381
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: How to compile the firmware
I believe git command should not care
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: How to compile the firmware
Yes it does. It does not work in firmware folder.
You have to be in the git folder. If you show hidden files, you see the git folder in the folder.
so type cd.. one time first and it should work fine.
- NormanAlphaspeed
- Posts: 68
- Joined: Fri Jan 13, 2017 7:15 am
- Location: Puerto Rico
- Contact:
Re: How to compile the firmware
Same error
BTW I haven't deleted any folder or anything. AlphaX Auto Electronics
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
Re: How to compile the firmware
You cloned into that directory? not copied?NormanAlphaspeed wrote: ↑Thu Feb 14, 2019 3:23 pmSame error
eror3.PNG
BTW I haven't deleted any folder or anything.
Re: How to compile the firmware
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.
cd C:\Users\user\Downloads
git clone https://github.com/rusefi/rusefi.git
cd rusefi
git submodule update --init
I believe the commands will be something like this.
cd C:\Users\user\Downloads
git clone https://github.com/rusefi/rusefi.git
cd rusefi
git submodule update --init
Last edited by kb1gtt on Fri Feb 15, 2019 5:05 pm, edited 1 time in total.
Welcome to the friendlier side of internet crazy
- NormanAlphaspeed
- Posts: 68
- Joined: Fri Jan 13, 2017 7:15 am
- Location: Puerto Rico
- Contact:
Re: How to compile the firmware
Nothing yet.
BTW, there is a . git inside the "rusefi" folderAlphaX Auto Electronics
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
- AndreyB
- Site Admin
- Posts: 14381
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: How to compile the firmware
git clone has created a new 'rusefi' folder. You should be somewhere inside the folder to invoke orher git command including git aubmodjlez
cd rusefi
cd rusefi
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- NormanAlphaspeed
- Posts: 68
- Joined: Fri Jan 13, 2017 7:15 am
- Location: Puerto Rico
- Contact:
Re: How to compile the firmware
Well that was quite stupid of me lol
Color me burned out.
It is finally working, thanks everyone.
Compiled fine, finally. Thanks everyone!
AlphaX Auto Electronics
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
https://www.facebook.com/AlphaXAutoElectronics/
Tuned by AlphaSpeed
https://www.facebook.com/AlphaSpeedPR
Re: How to compile the firmware
I just edited my prior post which included the commands you followed. Not this thread makes out to look bad
At least now if someone find it, they'll have the proper commands to try.
At least now if someone find it, they'll have the proper commands to try.
Welcome to the friendlier side of internet crazy
Re: How to compile the firmware
Hi everybody!
I used manual for compile the firmware and come to this stage....
Where i made something wrong?
Who meeted with this problem also?
I used manual for compile the firmware and come to this stage....
Where i made something wrong?
Who meeted with this problem also?
- Attachments
-
- 123.png (70.12 KiB) Viewed 66182 times
- AndreyB
- Site Admin
- Posts: 14381
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: How to compile the firmware
Where did you get these source codes how exactly? How did you get chibios submodule exactly?
I see chibios/os/ports on your screenshot. I do not see "ports" folder at https://github.com/rusefi/ChibiOS/tree/4012d627c92b0e60bdbfdfca4af823852c341e18/os
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 see chibios/os/ports on your screenshot. I do not see "ports" folder at https://github.com/rusefi/ChibiOS/tree/4012d627c92b0e60bdbfdfca4af823852c341e18/os
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?
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- AndreyB
- Site Admin
- Posts: 14381
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: How to compile the firmware
I've just edited the first post in that 2013 topic. There were updates in the comments but first post was very very outdated.Kavabanga wrote: ↑Sun Jul 07, 2019 11:10 pmI took it here
https://rusefi.com/forum/viewtopic.php?f=9&t=253
We are chatting now, let's use https://rusefi.com/forum/viewtopic.php?f=13&t=1198 or Skype for chatting.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Re: How to compile the firmware
Is it possible to use the STM32CubeIDE for compiling?
Re: How to compile the firmware
Anything is possible, just depends on how much effort you want to put into it.
Welcome to the friendlier side of internet crazy
Re: How to compile the firmware
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:
Now I want to modify some GPIO and Timer setting of your firmware and compile it.
Below is the first headache of make:
Re: How to compile the firmware
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
As i had experience, The cygwin sometimes goes unstable especially with lib(s).
https://www.youtube.com/watch?v=H3ZQDkpKwQo
Re: How to compile the firmware
The Linux way!
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
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
Re: How to compile the firmware
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 ;-(