The benefits of hacking the library are custom texts, and imagery, the benefits of hacking the firmware are limitless

Modifying the bitmaps is really just for fun, although I can see higher contrast colour schemes might be useful. Homebrewed languages might be useful for some people too

I want to learn enough about the DEVO Tx's to be able to replace the firmware rather than hacking the original to do different things

Originally Posted by rcH4x0r

Modifying the bitmaps is really just for fun, although I can see higher contrast colour schemes might be useful. Homebrewed languages might be useful for some people too

I want to learn enough about the DEVO Tx's to be able to replace the firmware rather than hacking the original to do different things

Agreed with you there, if we can get the firmware to source I could work on the code, I am fairly proficient in C and C like languages but I know nothing about decompiling these things.

Originally Posted by rcH4x0r

Modifying the bitmaps is really just for fun, although I can see higher contrast colour schemes might be useful. Homebrewed languages might be useful for some people too

I want to learn enough about the DEVO Tx's to be able to replace the firmware rather than hacking the original to do different things

I have to say, that in this case modifying the bitmaps is a must. You will see when your DEVO 8 arrives, you won't see s..t on the display!

Rewriting the whole firmware from scratch is a big longlasting step.
I agree with that in the long term, but I would like to achive a few smaller goals before...

The DEVOs have a lot of functionality which are nice, and I wouldn't like to dismiss them.

FDR


P.S: For a reference this was the original thread, which started the hacking:
http://www.rcgroups.com/forums/showthread.php?t=1031074

Originally Posted by FDR_

There are some information about it:
http://9xforums.com/forum/viewtopic.php?f=5&t=362
They even link your pages...

The telemetry module IS the standard RF module of the DEVO 8 and 12. They do all the communication throw it. It is only a revised version of some kind. There are reports, that telemetry works with the original modules too...

It is said that telemetry only has a range of about 15 feet with the original module. The updated moduel extends the range.

I am working on a complete re-skin of mine, here is the beginning .

One of the things the library editor is missing is the ability to edit non-image related stuff, I want to edit texts, fonts, etc too.

NorCalMatCat looking good!

Hi hackers

Just wanted to let you know I am offering a bounty of 30 USD for anyone who can implement the timer mapped to throttle feature for the 10mw and 100mw firmwares for the 6s and 8s. Hopefully others will contribute as well.

http://www.rcgroups.com/forums/showthread.php?t=1608554

btw norcal, that skin looks cool.

Originally Posted by bytemuncher

Hi hackers

Just wanted to let you know I am offering a bounty of 30 USD for anyone who can implement the timer mapped to throttle feature for the 10mw and 100mw firmwares for the 6s and 8s. Hopefully others will contribute as well.

http://www.rcgroups.com/forums/showthread.php?t=1608554

btw norcal, that skin looks cool.

Thanks, I am going to slowly improve it as I go along, already did some more revisions .

While inside my Devo 8 to change out a broken switch I snapped a pic of the CPU, an STM32F103

Originally Posted by NorCalMatCat

While inside my Devo 8 to change out a broken switch I snapped a pic of the CPU, an STM32F103

Cool, thanks!

So the DEVO 8 uses STM32F103VCT6, the DEVO 7 uses STM32F100C8T6B.

The 32F100 in the DEVO 7 has only one SPI port, that's why it misses the USB port...

From what I can tell it seems making a firmware for this thing would be easy, but getting to know how all the hardware communicates seems like the tough one... Once someone gets the hardware aspect figured out I am more then ready to do some code ROFL

I like the skin, nice to see someone using the tool. I will have a look at adding string support shortly, it shouldn't be too tricky.

Thanks for the picture, the SST25VF032B (32Mbit) looks like it is connected to SPI1 - maybe settings & resources (bmps, fonts etc). That ties in nicely with code I found that reads and analyses data from the SPI port.....

Edit: It looks like both DAC pins are in use for SPI (PA4 & PA5) and I can't see any refs to the DAC base address in the code. I wonder where the catchy tunes are coming from?

Originally Posted by rcH4x0r

I like the skin, nice to see someone using the tool. I will have a look at adding string support shortly, it shouldn't be too tricky.

String tables:

DEVO 6 Lib v0.1: address=0x0017C400 languages=English,German,Chinese strings=272 strlen=32
DEVO 6 Lib v0.2: address=0x00182600 languages=English,Chinese,German,French,Spanish strings=316 strlen=32
DEVO 8 Lib v0.0.3: address=0x0017EC00 languages=English,German,Chinese,French strings=284 strlen=32
DEVO 8 Lib v0.0.4: address=0x00184C00 languages=English,Chinese,German,French,Spanish strings=328 strlen=32
DEVO 12 Lib v1.0.6: address=0x0073E200 languages=English,French,German,Chinese strings=436 strlen=48
DEVO 12 Lib v1.0.7: address=0x00754680 languages=English,Chinese,German,French,Spanish strings=480 strlen=48

The encoding seems like UTF-7 for the western languages and UTF-16 for chinese...