DIYEFI.org Forum

One of users (JOleg) already started porting SECU-3 firmware to GCC (and mostly finished). He will add his results into repository soon and I will put link to it here. Depending on results of JOleg's work I will try megre his changes to main branch of firmware.

This is a link to Russian topic viewtopic.php?f=52&t=1177

Oh no! JOleg should have been committing changes as he went so that there was a clear path between old and new and so that it was easy to see what changed and why. But, there is no point in crying over spilt milk! Great to hear! :-)

Thanks for updating us silly English speakers too! :-)

Fred.

Link to JOleg's repository http://subversion.assembla.com/svn/secu3doc/JOleg/

I've finished porting source code to GCC (WinAvr)!
- Code can be compiled either by GCC or IAR;
- Makefiles are used.

To build project you need to run configure.bat with two options: type of microcontroller and type of compiler. Example:
configure.bat M32 GCC
or
configure.bat M32 IAR

It will create Makefile for you and start building project. If you are going to use IAR you must set environment variable IAR_HOME, this variable is used by Makefile.
It is possible to create configure.sh for Linux

Code is not fully tested and currently I have some issue related to code build by GCC (wrong calculation of advance angle). I will let you know when I solve this issue.

STC wrote:I've finished porting source code to GCC (WinAvr)!
- Code can be compiled either by GCC or IAR;
- Makefiles are used.

Awesome work! :-)

Also, I've already fixed issue with advance angle. Now it should work properly.

I've created configure.sh script for Linux

Today I've improved Makefiles a little bit. Automatic generation of dependencies and checking have been added.

STC wrote:Today I've improved Makefiles a little bit. Automatic generation of dependencies and checking have been added.

I'll have to have a look at how you've done that! My make file deps are manual and prone to error, not cool. I need to improve that situation. Thanks for posting about it! :-)

A couple of comments:

If you're going to manually wrap lines, do it at 80 chars for readme type files. You seem to be doing it at 85 which makes it soooo hard to read in a std terminal. Or just don't wrap them and let the editor of the reader do it for you.

Consider switching to markdown readme format (.md) as it will display very nicely on github and is pretty easy to read in text too. See freeems-vanilla repo readme for an example.

I also added an ignore file for you. See the sticky on git usage in freeems general if you don't know how to pull it in WITHOUT using the github UI.

Fred.