Getting the RevE Board Back Into Bootloader Mode about chameleonmini-rebooted HOT 5 CLOSED

As it happens, the reason I was re-flashing the device to begin with is to test out some logging firmware mods related to #37 from last week. The firmware files are located here for testing. Pretty basic add-ons to the source, I just can't test them out at the moment! Note that this add-on gives the RevE boards the same LIVE logging capabilities as the RevG versions. This makes interactive sessions with a portable phone and my Android app possible...

from chameleonmini-rebooted.

yeah, the linux flashing isn't solved, meaning we haven't figured out how to do it. :(
There were some discussions on issues #11 #12 It tooks some time before we managed to flashed the compiled firmware in this repo using the tools needed. We wrote it down in the wiki aswell.

But basically, figuring out a way to solve the linux flashing would be great.

from chameleonmini-rebooted.

So is the issue that the manufacturer locked the chips except for with these bootloader flashers? Will these utilities restore the Chameleon firmware on my device?

from chameleonmini-rebooted.

Dunno actually about locked chip, we only know bits and pieces in the flashing process.
Classic lockdown the firmware in order to make money, sadly, having a closed firmware also means high demands for bugfixes etc from the manufacturer which didn't happen. Almost kill off the rebooted product.

If you use the original firmware files with the windows tools, you will get a working rev E rebooted again.
or should atleast, dunno what you messed up. I messed up several times, but with tools or with rewriting from debugger I got my device up again.

from chameleonmini-rebooted.

@maxieds please try reading Wiki as it has been recently reworked. The Makefile also includes a convenient make dfu-prog if needed. @iceman1001 due to age I guess this could be closed.

from chameleonmini-rebooted.