Cool! Is there any way to do firmware development without (yet) buying the actual hardware ? Some sort of ECU simulator ?
Cool! Is there any way to do firmware development without (yet) buying the actual hardware ? Some sort of ECU simulator ?
ALDLdroid author, Android application for ALDL ECU
https://play.google.com/store/apps/d...roux.aldldroid
Like us on Facebook
Visit the app's Website
Great question! Yes, there is a rusefi_simulator.exe way. I've just added an extended version of the response to the FAQ @ http://rusefi.com/forum/viewtopic.php?f=5&t=10&p=7948
"Thank you for the order you placed with Digi-Key."
Looks like I will have a stm32f4disovery board soon :P It was 29$ tho with the shipping to Canada.
I have experience with Java, quite a bit on Android and have done some project in C/C++. We will see if/how I can help.
I'm also participating in an Android app for MS that works with ini file so I assume if you use ini file that works with TunerStudio, the app might already work with rusEFI. Otherwise, I can always have a look and see what it would take to make it work, probably not much. App is here: https://play.google.com/store/apps/d...id=com.msdroid
ALDLdroid author, Android application for ALDL ECU
https://play.google.com/store/apps/d...roux.aldldroid
Like us on Facebook
Visit the app's Website
I am a java dev by day :)
The .ini file is @ https://svn.code.sf.net/p/rusefi/cod...e/tunerstudio/ - we are using F32 a lot, do you support it?
Pretty sure I don't, is that something that Phil added for you ? I don't think I've ever seen that for MS. What does it mean, my best guess would be a 32 bits float (4 bytes) ?
Btw, I got Sourcery CodeBench Lite for ARM EABI and Cygwin with make installed. I'm able to compile from the command line. I have Eclipse setup with the ARM plugin, now the issue I have is the following:
22:03:15 **** Incremental Build of configuration Default for project win32_functional_tests ****
make all
cygwin warning:
MS-DOS style path detected: C:\Users\Seb\Desktop\rusEFI\win32_functional_tests \
Preferred POSIX equivalent is: /cygdrive/c/Users/Seb/Desktop/rusEFI/win32_functional_tests/
CYGWIN environment variable option "nodosfilewarning" turns off this warning.
Consult the user's guide for more details about POSIX paths:
http://cygwin.com/cygwin-ug-net/usin...sing-pathnames
Compiling chcore.c
make: i686-pc-mingw32-gcc: Command not found
make: *** [build/obj/chcore.o] Error 127
rules.mk:118: recipe for target 'build/obj/chcore.o' failed
22:03:15 Build Finished (took 210ms)
Does that ring a bell to you ?
ALDLdroid author, Android application for ALDL ECU
https://play.google.com/store/apps/d...roux.aldldroid
Like us on Facebook
Visit the app's Website
F32 was added pretty recently, maybe for open5xx? yes 32bit float
Yes it does ring a bell - you need to add minigw gcc/g++ in Cygwin setup. Regular gcc there is a problem with semicolons and windows and its in the way of incremental build.
Cool, it compiles now! You might want to add "minigw gcc/g++" to the cygwin part here: http://rusefi.com/forum/viewtopic.php?f=5&t=9 :)
Thanks man!
ALDLdroid author, Android application for ALDL ECU
https://play.google.com/store/apps/d...roux.aldldroid
Like us on Facebook
Visit the app's Website
Bookmarks