search

master2be1 / 400plus

0 stars 0 forks source link

Add option to disable hack #82

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Please, describe the enhancement of feature requested below:
According to Sergei at the forum, eventproc_DisableBootDsk() disables bootdisk 
and the hack.

I think we could add a menu entry, so users can disable the camera on-the-go 
(if the hack starts acting weird, for example) without formatting the card.

Original issue reported on code.google.com by eduardo....@gmail.com on 29 May 2011 at 11:28

GoogleCodeExporter commented 9 years ago 
so far this is the only way to disable the hack, fortunately in the future, we 
can make it temporarily on a power-on basis... we need to find a reliable way 
to detect some indication that the hack should not be loaded in early phase of 
the booting... FileIO seems out of question.
Alex's suggestion is one option, if we can find some button RAM address, we can 
detect the button hold on power-up, and skip the hack.

Original comment by fired...@gmail.com on 30 May 2011 at 9:28

GoogleCodeExporter commented 9 years ago 
I think it would be nice to see a way of <temporarily> disabling 400plus at 
power-on (by possible trapping of a button press) - the normal camera software 
would only execute in this mode.  But it would be available again upon next 
power-on (if no trapping of button press detected).  And then in addition, a 
new menu entry (hidden deep somewhere) that truly disables the 400plus hack by 
removing the boot flag to boot with CF.  That is... if you can pull it off!

Original comment by mike.guf...@gmail.com on 18 Jul 2011 at 9:21

GoogleCodeExporter commented 9 years ago 
I'll work on this as soon as i get free time. Even more i think i can remake 
the firmware activation firmware, so one will be able to activate the firmware 
temporary or permanently.

Original comment by fired...@gmail.com on 18 Jul 2011 at 10:45

GoogleCodeExporter commented 9 years ago 
We could use the WDT task to block the pings to the watchdog, this way we can 
have a reboot.
I was thinking to use some CF function to indicate that the hack should not be 
started... it is possible to save some custom settings to the rom (eeprom i 
guess), but ineed to check further for this...
Alex suggested that we can use the FIO from the bootloader ... there seems to 
be some basic FIO routines there which can be used in the init process...
So far i have no luck in finding a ram address of any button, so if the 
suggested so far is working we can at least make a menu for temp. Disable the 
hack.

Original comment by fired...@gmail.com on 2 Sep 2011 at 3:49

GoogleCodeExporter commented 9 years ago 
closed by r1344

Original comment by fired...@gmail.com on 5 May 2012 at 1:30

GoogleCodeExporter commented 9 years ago

Original comment by fired...@gmail.com on 5 May 2012 at 1:30