[bootcoder]

Should I write the hex bytes into the .MOD?

Yes.

As ASCII?

No, you should use binary file editor.

---

Last edited by bootcoder; 05-09-2015 at 04:50 PM.

[marabella]

bootcoder I worship you..


00077850.558 - [OPEN_DEBUG_MENU] plus LF in notepad Ctrl or Strg + Return.
DEVELOP.MOD - 07 01 2C 1F 10 03 1E 16 05 2D I have used Frhed to make this file and to fill in the content.

Card door open, MENU plus ON.

Cheers!

[thibs]

bootcoder I worship you..


00077850.558 - [OPEN_DEBUG_MENU] plus LF in notepad Ctrl or Strg + Return.
DEVELOP.MOD - 07 01 2C 1F 10 03 1E 16 05 2D I have used Frhed to make this file and to fill in the content.

Card door open, MENU plus ON.

Cheers!

congrats on this

[bootcoder]

00077850.558 - [OPEN_DEBUG_MENU] plus LF in notepad Ctrl or Strg + Return.
DEVELOP.MOD - 07 01 2C 1F 10 03 1E 16 05 2D I have used Frhed to make this file and to fill in the content.

Card door open, MENU plus ON.

Congratulations!

Do you see anything difference in menu to previous models ?
This was combination for "type 1" file and I am just curious: do you have an idea what "type 2" file should do ?
I am not sure if we should test "type 2" file, until we know what it does.

---

Last edited by bootcoder; 05-10-2015 at 07:28 AM.

[marabella]

Yes I'm cautious and I totally agree with you. Furthermore my camera still is covered by warranty (2 years).
AFAIK I will lose warranty if I make any changes to parameters.
So I kindly request somebody, whose camera is out of warranty, to do further tests .
But I guess that type 2 will open a Development Menu 2. See picture above. Edit: Wrong guess! There are 7 pages from Menu1 to 7.


But I dared enabling Debug Mode:
Sreen now displays a red "debug mode" in the lower right corner.
There is a new Test Mode in the menu:
- Capture System test
- AF Test (here you find the global AF-adjustment)
- Debug Mode disable (I don't know why here too)


This looks like the K20D's menu.

[marabella]

Out of curiosity I did more testing and "yes", type 1 content is essential.
Debug Menu will not open without it.


Some more pics from Debug Menu attached FYI.
Page 7 is missing due to board's restriction. It only covers information about versions -FW, Board, DSP, Build.

[richandfleur]

This looks like the K20D's menu.

I'm interested to see the similarities, in structure at least, across the different models and CPU/languages.
Pentax went through a range of different owners over the years, but it looks like their core approach has been consistent throughout, 'Movie SR' rubbish aside.


Good work all, congrats!

[bootcoder]

Code:

006ae8c0h: 2A 00 00 00 44 65 76 65 6C 6F 70 6D 65 6E 74 20 ; *...Development 
006ae8d0h: 4D 65 6E 75 37 00 00 00 16 E9 7C 40 46 57 20 20 ; Menu7....é|@FW  
006ae8e0h: 20 20 20 20 20 56 45 52 20 20 20 20 20 20 20 20 ;      VER        
006ae8f0h: 20 20 20 20 00 00 00 00 42 4F 41 52 44 20 20 20 ;     ....BOARD   
006ae900h: 20 56 45 52 20 20 20 20 20 20 20 20 20 20 20 20 ;  VER            
006ae910h: 00 00 00 00 44 53 50 20 43 48 49 50 20 56 45 52 ; ....DSP CHIP VER
006ae920h: 20 20 20 20 20 20 20 20 20 20 20 20 00 00 00 00 ;             ....
006ae930h: 42 55 49 4C 44 20 49 4E 46 4F 20 20 20 20 20 20 ; BUILD INFO      
006ae940h: 20 20 20 20 20 20 20 20 00 00 00 00 5B 4D 45 4E ;         ....[MEN
006ae950h: 55 5D 00 00 43 61 6E 63 65 6C 00 00 5B 4F 4B 5D ; U]..Cancel..[OK]

I guess this menu is only for firmware updates ? Perhaps Type 2 content enables this ?
Many different update files can be accepted:

Code:

007e0000h: 64 50 61 63 6B 61 67 65 00 43 00 43 3A 5C 4B 42 ; dPackage.C.C:\KB
007e0010h: 35 35 38 44 43 52 2E 42 49 4E 00 43 3A 5C 4B 42 ; 558DCR.BIN.C:\KB
007e0020h: 35 35 38 43 43 52 2E 42 49 4E 00 43 3A 5C 4B 42 ; 558CCR.BIN.C:\KB
007e0030h: 35 35 38 2E 42 49 4E 00 43 3A 5C 4B 42 35 35 38 ; 558.BIN.C:\KB558
007e0040h: 46 4C 4C 2E 42 49 4E 00 43 3A 5C 46 57 44 43 32 ; FLL.BIN.C:\FWDC2
007e0050h: 32 36 42 2E 42 49 4E 00 43 3A 5C 4E 4F 57 41 49 ; 26B.BIN.C:\NOWAI
007e0060h: 54 00 43 3A 5C 4B 42 43 48 47 2E 42 49 4E 00 43 ; T.C:\KBCHG.BIN.C
007e0070h: 3A 5C 46 57 42 59 50 41 53 53 00 43 3A 5C 46 57 ; :\FWBYPASS.C:\FW
007e0080h: 44 45 4C 2E 42 49 4E 00 03 00 00 00 00 00 00 00 ; DEL.BIN.........

[marabella]

You're a god!

---------- Post added 05-10-15 at 03:06 PM ----------

Code:

006ae8c0h: 2A 00 00 00 44 65 76 65 6C 6F 70 6D 65 6E 74 20 ; *...Development 
006ae8d0h: 4D 65 6E 75 37 00 00 00 16 E9 7C 40 46 57 20 20 ; Menu7....é|@FW  
006ae8e0h: 20 20 20 20 20 56 45 52 20 20 20 20 20 20 20 20 ;      VER        
006ae8f0h: 20 20 20 20 00 00 00 00 42 4F 41 52 44 20 20 20 ;     ....BOARD   
006ae900h: 20 56 45 52 20 20 20 20 20 20 20 20 20 20 20 20 ;  VER            
006ae910h: 00 00 00 00 44 53 50 20 43 48 49 50 20 56 45 52 ; ....DSP CHIP VER
006ae920h: 20 20 20 20 20 20 20 20 20 20 20 20 00 00 00 00 ;             ....
006ae930h: 42 55 49 4C 44 20 49 4E 46 4F 20 20 20 20 20 20 ; BUILD INFO      
006ae940h: 20 20 20 20 20 20 20 20 00 00 00 00 5B 4D 45 4E ;         ....[MEN
006ae950h: 55 5D 00 00 43 61 6E 63 65 6C 00 00 5B 4F 4B 5D ; U]..Cancel..[OK]

I guess this menu is only for firmware updates ? Perhaps Type 2 content enables this ?
Many different update files can be accepted:

Code:

007e0000h: 64 50 61 63 6B 61 67 65 00 43 00 43 3A 5C 4B 42 ; dPackage.C.C:\KB
007e0010h: 35 35 38 44 43 52 2E 42 49 4E 00 43 3A 5C 4B 42 ; 558DCR.BIN.C:\KB
007e0020h: 35 35 38 43 43 52 2E 42 49 4E 00 43 3A 5C 4B 42 ; 558CCR.BIN.C:\KB
007e0030h: 35 35 38 2E 42 49 4E 00 43 3A 5C 4B 42 35 35 38 ; 558.BIN.C:\KB558
007e0040h: 46 4C 4C 2E 42 49 4E 00 43 3A 5C 46 57 44 43 32 ; FLL.BIN.C:\FWDC2
007e0050h: 32 36 42 2E 42 49 4E 00 43 3A 5C 4E 4F 57 41 49 ; 26B.BIN.C:\NOWAI
007e0060h: 54 00 43 3A 5C 4B 42 43 48 47 2E 42 49 4E 00 43 ; T.C:\KBCHG.BIN.C
007e0070h: 3A 5C 46 57 42 59 50 41 53 53 00 43 3A 5C 46 57 ; :\FWBYPASS.C:\FW
007e0080h: 44 45 4C 2E 42 49 4E 00 03 00 00 00 00 00 00 00 ; DEL.BIN.........

Mmh, this exceeds my skills. 558 obviously leads to the camera model but DCR/CCR/FLL? May be these are parts of the firmware?

[bootcoder]

@marabella
haha not true, I am still puzzling on decompressor

Code:

0x40701C3C ; 'DETECTED DSP  F/W FILE'     -> 'C:\KB558.BIN'    0x01C01610 bytes
0x40701C54 ; 'DETECTED DSP CORE FILE'     -> 'C:\KB558DCR.BIN' 0x01201610 bytes
0x40701C6C ; 'DETECTED CPU CORE FILE'     -> 'C:\KB558CCR.BIN' 0x00200210 bytes
0x40701C84 ; 'DETECTED DSP FULL F/W FILE' -> 'C:\KB558FLL.BIN' 0x01201610 bytes

There are 2 processor cores inside: one named CPU and one named DSP, both ARM.

[marabella]

A step further on.
With your help my primary mission is accomplished - getting access to the global AF-adjustment.
I thought I actually would need this because one specific lens was pretty much out of focus.
But I had made a big mistake. I did the focussing tests under artificial light conditions.
I should have done this under daylight conditions. This lens can easily be corrected via the usual menu.

Next mission: Removing two annoying restrictions. Enable remotely triggered bracketing and time-lapse shooting.
That's the major challenge - hopeless I fear.

@richandfleur
AFAIK this work has been started with the release of the K10D.
This Debug mode could be a usefull source to answer your question.

[bootcoder]

Next mission: Removing two annoying restrictions. Enable remotely triggered bracketing and time-lapse shooting.

Isn't this possible using USB remote camera control, or smartphone with WLAN ?

[marabella]

No way. I own a Pentax FluCard which is supported by the K-S1. Yes one can remotely trigger the camera but only in single shot mode.
Furthermore you can't combine multi shooting/bracketing with the inbuild selftimer or an infrared remote control.
All of these options are located in the same menu folder but only one option is alterable - OR-ELSE type like, not AND-OR.


Hah, have a look at this: https://www.pentaxforums.com/forums/184-pentax-k-s1-k-s2/293959-k-s1-anachron...e-trigger.html
You may laugh out loud. That's ok. This is the only working solution so far. I made it up from old junk just for the fun of it.

[bootcoder]

You may laugh out loud. That's ok. This is the only working solution so far.

Great solution!

[bobbotron]

It'd be cool if you guys could figure out a way to turn off the high speed flash sync ceiling, so you could use a cactus HSS trigger with a pentax body at shutter speeds greater than 1/180!