about this blog

Here you can find latest hack progress reports and other raw information.


tags


recent entries   


Donate for GH1 hack project! 

-April 23, 2010

GH1 firmware update research 

-April 19, 2010

GH1 related 

-April 17, 2010

More info on Panasonic 

-April 14, 2010

Panasonic Cameras 

-April 12, 2010


recent comments

When your supplemental succeeds, you on too. You aren’t in contention with each other to ... 

-October 03, 2019

In some ways, splitting from with a co-conspirator you logical with but aren’t married to ... 

-October 03, 2019

When your share in succeeds, you follow to too. You aren’t in make an analogy ... 

-October 02, 2019

In some ways, splitting from with a doodad you accepted with but aren’t married to ... 

-October 02, 2019

When your party succeeds, you succeed to too. You aren’t in controversy with each other ... 

-October 02, 2019


archive

april 2010

march 2010

september 2009

august 2009



topics

General (13)

Dumping (1)

Disassembling (5)

Features (0)


admin*

Script


Wednesday, August 12, 2009


7:37



Four necessary improvements are:
 

1) Handing of jump tables. This is very frequently used feature.

2) Script to handle offset tables (many of them are present),

   so pressing two keys automatically changes all to offsets

   (until it is proper address and stops as soon as it is not)

   add xref and start analizing procedures.

3) Many parameters are passed by registers. If we could track them somehow and  allow to quickly define this in function definition, so comments can be seen right after commands before call (ala pc.w32).

4) FR module have almost ready auto-comments. Is it desirable to make them work inside IDE (as gray auto-comments). As most people are quite new to this assembler.

If you have time and expirience working with IDA writing IDC scripts and/or plugins and modules, please, contact me.



Disassembling  comments (2)



Saturday, August 8, 2009


13:50



AUTORUN.xxx working script
%A = 1000
WHILE %A < 1004
{
PRINT "Hex value %x" %A
%A += 1
}
PAUSE
%B = 50
PRINT "B=%d" %B
PAUSE
EXIT

 

As you can see, it uses integer variables, loop and printing of values.



General  comments (1)



Saturday, August 8, 2009


6:39



Some info about GX20 v1.01 and MODSET and AUTORUN functions.

MODSET.xxx works with turning on with open or closed (!) SD door (without any buttons).
Note! You must not have AUTORUN.xxx for MODSET.xxx to work :-)

All previously mentioned commands seems to work.
 
Additional info below:

[VLENS_CTRL] displays VLENS CONTROL on screen and do not react to keys I tried. We must find key combination that toggles SDM On/off and PZ On/Off.
 
[OPEN_DEBUG_MENU] Opens large debug menu on startup there you can make all functions. Like dumping your lens ROM. :-)
Especially interesting is AF PINT DISP as it displays some displacements.


AUTORUN.xxx works on every camera start, and in case of synax error it hangs sometimes.

Extra info, you could use FILEOUT "STRING" to write STRING to CHKDAT.xxx file. String will be appended to end of file.

WAIT without parameters causes syntax error.
With any parameter it wait indefinetely. Parameter may be TaskID.

You could also note that interpreter runs in his own thread, at least AF and metering works perfectly.


General  comments (0)



Friday, August 7, 2009


5:00



Enabling debug mode.
 
Make file named 'MODSET.xxx' in flash card root.
Note! xxx is different for each model.
in file write commands exactly as they are provided, use notepad or other simple text editor.
 
MODSET file name

Camera model

File name

K10D with firmware v1.10 MODSET.421 (don't work with v1.20 and v1.30!)
GX10 with firmware v1.10 MODSET.429 (same as K10D)
GX20 v1.01 MODSET.454
K20D v1.03 MODSET.442
K200D v1.00.00.03
MODSET.445
K7 v1.01
MODSET.474
Km v1.10 MODSET.464

 
Available commands

Command

Meaning

[DEBUG_MODE EN] Enables debug mode
[DEBUG_MODE DIS] Disables debug mode
[RELEASE_AGING] Test shutter by making many expositions
[OPEN_DEBUG_MENU] Opens debug menu
[SW_DEBUG_MENU EN] Enables debug menu
[SCRIPT_EN_MODE EN] Enables script interpreter
[SCRIPT_EN_MODE DIS] Disables script interpreter
 
 
Example of proper MODSET.xx file
[DEBUG_MODE EN]
[SCRIPT_EN_MODE EN]
 
Turn camera off.
Turn camera on with MENU button pressed.
 
I don't guarantee that this will work on all cameras the same.
But easy to check.
 

If in original it don't work leave flash door open then turning camera back on.



General  comments (75)



Friday, August 7, 2009


3:46



How to turn build in script interpreter
 
You must enable script mode :
 
MODSET.xxx file
[SCRIPT_EN_MODE EN]
 
Make 'AUTORUN.xxx' file (xxx same as in MODSET file) with script inside.
 
Available BASIC keywords
END, EXIT, PAUSE, WAIT,
GOTO, IFGOTO, ALLCLR, CLS,
PRINT, LANGUAGE, COLOR, $ % ( for values )
GOSUB, IFGOSUB , RETURN, IF, ELSE,
WHILE, INTERVAL, CYCLE, FILEOUT, FSEARCH,
TIMERON, TIMEROFF.

Looks like quite full functional BASIC 
You could try "hello world" first.
 
AUTORUN.xxx hello world example
PRINT "Hello World";
EXIT
 
According to first test results, you must turn camera on with MENU button and after firmware version number you'll see your program execution result.
 
Test volunteers are welcome.


General  comments (11)




1 - 5 of 5















(c) 2009 Pentax Hacking Community