forum.heinrichsweikamp.com

Hallo,

Die neue 2.10beta hat einige Änderungen an internen
Programmteilen die aufgrund der Erhöhung von 16 auf 32MHz nötig sind. Damit sollten auch einige selten auftretenden Probleme mit dem Logbuch behoben sein.

-> http://www.heinrichsweikamp.com/de/ostc_2n/firmware/

P.S.: Profi-Tipp für alle, die mit dem Bootloader V2 arbeiten: Wenn Ihr die "tinybld.ini" im Bootloader Verzeichnis öffnet und den Abschnitt [WEB] mit:
[pre]
[WEB]
HEXURL=http://www.heinrichsweikamp.net/autofir ... latest.hex
TXTURL=http://www.heinrichsweikamp.net/autofir ... latest.txt
[/pre]
ersetzt, könnt die immer letzte Version (Beta oder Stable) in English auch so beziehen.

Gruß,
Matthias


Hi,

The new 2.10beta has some changes at internal routines that were necessary due to the increase from 16 to 32MHz clock speed. With this, the spurious errors in the logbook should be fixed now.

-> http://www.heinrichsweikamp.com/en/ostc_2n/firmware/

You can install it with the bootloader V2 (No reset in the unit required!). Instead of choosing "Web download" just install it manually by selecting the HEX file with "browse".

P.S.: For advanced users that use the bootloader v2: If you open the "tinybld.ini" in the bootloader directory and replace the section [WEB] with:
[pre]
[WEB]
HEXURL=http://www.heinrichsweikamp.net/autofir ... latest.hex
TXTURL=http://www.heinrichsweikamp.net/autofir ... latest.txt
[/pre]
you'll always get the latest version (Beta or stable) in English with the bootloader v2 directly.

Cheers,
Matthias

Hallo Matthias,

nach dem ersetzen kommt folgende Fehlermeldung:

Looking for http://www.heinrichsweikamp.net/autofim ... latest.hex
Could not access site information


Gruß Uwe

firmware mit "r" natürlich (Gerade oben geändert...)

Gruß,
Matthias

Any idea about the releasedate of the next stable firmware?

I think within January - just some more test dives with the 2.10beta to do. We also need some translations in Spanish...

Regards,
Matthias

Thanks for the informations!

I was updating my firmware yesterday (with jDiveLog on a Mac). It worked all well. But after rebooting i had have two warnings blinking on the main screen: CF56 and CF57. They're both set to 200 by default. This is way to much I don't know if this has a relation to the beta-firmware - i just wanted to report this issue...

CF65, are you sure ?

CF56, i suppose

uups, you're right. i changed it...

Normal, CF56 and CF57 have been changed to no decimal in 2.02beta, so the old default value is now out of the recommended range.

This happens when users don't want to have their CF reset with the update...

regards,
Matthias

Thanks, Matthias. I was updating from 2.01 to 2.10 directly...