jabdoa2 / asksin_ota_bootloader Goto Github PK

Hi,
I have an unmodified sw1pbu and would like to modify the firmware using flash-ota. I'm able to flash an official firmware image without problems, however the device rejects any custom firmware created with hex2eq3.php
Looking at the stock firmware the format seems to be a list of [uint16 length][data][uint16 crc] where length is always a multiple of 16. The first block is 15-1716, then there are interleaved blocks 116 and 1716, and at the end a couple of blocks with 1716 length. as the SPM_PAGESIZE is 256 i assume that the 1716 blocks contain one page worth of data with a 16 byte header?, also the data does not seem to contain any valid atmel code. I assume it is encrypted? maybe the 16 byte header is an aes IV?
Please let me know if it should be possible to flash a custom eq3 file or if that only works after installing the custom bootloader, also, does the custom bootloader accept stock eq3 files?
Thanks,
Mo

Hi,

your bootloader is currently missing any sort of license.
This makes it impossible to integrate your bootloader into any binary distribution of firmware binaries (for example to flash onto AskSin boards) because the bootloader is licensed as "All rights reserved" at the moment.

A license like MIT: https://choosealicense.com/licenses/mit/ would be ideal, because it allows the bootloader to be integrated in MIT and GPL licensed projects alike.

Licenses like the Creative Commons (used by the AskSin++ project itself) are unfavorable for software projects, because they don't apply to and protect compiled binaries.

Could you add an appropriate license agreement to your repo? (GitHub can help you, just add a new file called "LICENSE.md" via the web interface)

Thanks,
Tobias

Building the bootloader on a Raspberry PI (latest wheezy image with GCC 4.6.3 as well as when updated to jessie with GCC 4.9 and avr-gcc 4.8.1) results in a bootloader with the following behavior:

• after flashing bootloader.hex with avrdude, the device resets and jumps into bootloader; serial UART messages can be read
• an OTA flash of a .eq3 firmware file with flash-ota from hmland works, and after receiving the firmware file, the device correctly enters the firmware; if compiled with #USE_SERIAL, UART messages can be read

But as soon as the device is disconnected from voltage, it becomes useless:
When switching on voltage, the config LED blinks once (usually signalling that it has jumped into the bootloader) but then nothing happens anymore... and no messages at all can be read via UART.

This happens when using an unmodified "git clone" version of the bootloader...
A ready-built bootloader from https://owncloud.isengard.at/public.php?service=files&t=0df535e31ad6999664f0e84c95bd2ea5 works just fine with the same firmware...