I want to try some simple hacking, but I’m very new at this stuff. I figure the first step would be to compile the firmware myself and make sure I can get it running before I try messing with any code. Unfortunately, I am currently running WinXP. Has anyone successfully compiled the firmware on a windows machine? If so, what compiler did you use? Thanks.
Yes, someone on the v0.92 thread has done it.
Thanks, I’ll look there.
Use WinAVR and Python 2.5.
Make sure the winavr and python directories are in the path variable (google this).
Check the Firmware page on how to set things up: http://mutable-instruments.net/shruthi1/firmware
Note: you have to enter the directories in the base.mk file with backslashes, like “C:\\WinAVR\\bin” . However, if the make script returns errors like “file … not found”, try to put a slash at the end, e.g. " C:\\WinAVR\\bin/ ". This did it for me with the lastest source code.
Great! Thanks for the tips. I’ll try to do a build this weekend and report back.
hello to the community !
i’ve order on kit of Shruthi and i’m trying to build firmware on windows machine in order to add addon feature on midi out. I’m using WinAVR with GCC compiler and Python.
I’ve some trouble with external make files (relative paths, “\” instead of “/” …). Is it possible to use and edit WinAVR internal makefile without using externals make files ?
Here is my attempt to build a 0.92 firmware in a winXP machine:
Already had arduino-0022 software with GCC-4.3.2 somewhere in my computer, moved to C:\\ (that looks to be necessary).
Installed WinAVR-20100110 and Python 2.6.6 (msi).
Downloaded shruthi-1-a4544c0.zip and avril-54d37ea.zip, inside the shruthi-1 there’s an empty avrlib folder where I expanded the avril one.
Like explained in the firmware page, edited the avrlib/makefile.mk paths:
AVRLIB_TOOLS_PATH = C:\\arduino-0022\\hardware\\tools\\avr\\bin/
AVRLIB_ETC_PATH = C:\\arduino-0022\\hardware\\tools\\avr\\etc/
then cmd, navigated to the folder and “make resources”, “make”.
Make size didn’t work to me, maybe because of this or for the older GCC version at the end I have two file that are larger than the ones you can download from this website, mine are shruthi1.hex 177KB and shruthi1.mid 130KB.
I’m afraid there’s something wrong, ideas?
make size doesn’t work because you don’t have the moose installed
but you should still be able to find the size in shruthi1.size (the actual firmware size is the sum of the first two columns).
my shruthi1.size shows 63252 (text)+ 532 (data) = 63784, same as downloaded it doesn’t change after “make” commands.
I tried new paths:
AVRLIB_TOOLS_PATH = C:\\WinAVR-20100110\\bin/
AVRLIB_ETC_PATH = C:\\WinAVR-20100110\\bin/
now smaller file sizes, shruthi1.hex 176KB and shruthi1.mid 129KB.
have you tried to bootload it to the Shruthi ?
(You can’t damage it - if your firmware file is mumbo-jumbo, you’ll see some erratic or no LED reaction and it won’t boot up properly after restart - but you’ll simply have to upload the original firmware again)
If the problem persists, you may also try Python 2.5 (Python does the hex to mid / syx conversion).
I had trouble with the python things on some older make script, however the .hex file was apparently fine.
Worked perfectly with Python 2.5.
no I can’t, my shruthi is away at a friend’s house, but I will and let you know.
I’ve got my Shruthi back and looks like I’ve successfully uploaded the firmware via MIDI, thanks stuartm
I had troubles too, wasn’t enough to rename the .mid file to .syx I had to use the --syx option.
The .mid file is basically the .syx encapsulated in a MIDI Playback file, and you spotted correctly that just renaming does not do the trick.
with great effort make it work, have but “make midi” command says:
python tools/hex2sysex/hex2sysex.py -o build/shruthi1/shruthi1.mid build/shruthi1/shruthi1.hex
process_begin: CreateProcess(NULL, python tools/hex2sysex/hex2sysex.py -o build/shruthi1/shruthi1.mid build/shruthi1/shruthi1.hex, …) failed.
make (e=2): The system cannot find the file specified.
make.EXE: ***** [build/shruthi1/shruthi1.mid] Error 2
(shruthi1.hex exists at above-mentioned path)
Do you have python installed on your computer ?
Yes, version 2.5. Path variable is set too.
Looks like the “python” tool is not in the path (at least not in the environment in which make is spanning processes) In avrlib, locate the line with the HEX2SYSEX = … definition. Try to replace “python” by the path to your python install.
If python is in the path of your shell, you can try directly typing:
python tools/hex2sysex/hex2sysex.py --syx -o build/shruthi1/shruthi1.syx build/shruthi1/shruthi1.hex
Add the --obsolete_manufacturer_id flag if your Shruthi is running an old version of the bootloader.
editing makefile.mk python path gives the same result.
typing command in shell returns:
Hmmm, you’re on the right track. Maybe it’s just that this forum thing makes two dashes – look like a single one.
Thanks, now it works! =)