G11 porting - page 4 - DryOS Development - CHDK Forum supplierdeeply

G11 porting

  • 527 Replies
  • 143480 Views
Re: G11 porting
« Reply #30 on: 27 / December / 2009, 07:00:42 »
Advertisements
« Last Edit: 27 / December / 2009, 07:24:12 by kingcang »

*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #31 on: 27 / December / 2009, 07:10:26 »
Okay, i was able to get a chdk supported camera into my hands (A590IS), so i modified the blinker code to the led adresses for this model (found in the wiki) and tried my custom diskboot.bin build on this camera.
Result: Display stays dark, and all LEDs are set to ON after 1-2 Seconds. :)
So my build toolchain seems to work. I tried this build also on the G11, but nothing happens, camera looks "dead".
I then did a build, which covers the known led adress range for the G10,  but again nothing happens. Also increasing the range does not show any success, LEDs are allways off.

So i think, i have to take a look on the encoding/FI2 stuff. ;)
 

Re: G11 porting
« Reply #32 on: 27 / December / 2009, 07:19:41 »
what to do with the other end of the jack plug

Those diagrams show schematically how you connect the components to the jack plug.

In practice, you connect to the wires in the cable that are already connected to those parts of the plug.

Use a testmeter on the resistance range to determine where each wire connects to on the plug.

(I am now going out until this evening).
« Last Edit: 27 / December / 2009, 07:21:16 by Microfunguy »

*

Offline fe50

  • ******
  • 3105
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: G11 porting
« Reply #33 on: 27 / December / 2009, 07:25:56 »


Re: G11 porting
« Reply #34 on: 27 / December / 2009, 07:27:34 »
« Last Edit: 27 / December / 2009, 10:01:47 by kingcang »

*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #35 on: 27 / December / 2009, 08:26:14 »
Problems could be
- wrong encoding. You can try the same code as an FI2. To make an FI2, you must start with an unencoded diskboot, and you must use the correct keys and PID for your camera

Okay, i made some tests and i was able to create a FI2 file that the G11 recognizes as a valid firmware.
I simply used the same keys as in G10 (extracted from G10 FW-Dump) and compiled with that keys a fi2encdec.exe. Then i tested this tool by downloading a original G10 FW from the canon site and decompressed the FW. It works without errors. Then i changed the HDR to 0x000031DF and placed my diskboot.bin (with the led blinker code) into the map file. The created FI2 file was accepted from the camera (camere shows the message: "Update firmware version? 1.0.0.0 -> 1.0.0.0") and when i press the "OK" button display goes off, ON/OFF Led stays on, and the G11 looks up until i remove the battery. So i think this means, that the G11 has accepted the FI2 file and tries to start my "fake" Firmware Update / diskboot.bin file, right?
« Last Edit: 27 / December / 2009, 08:37:50 by ERR99 »

*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #36 on: 27 / December / 2009, 09:43:13 »
Success! With the FI2 methode i got finally the led blinker code running. With my current (pretty wide) adress range i got the AF-Led and the display illumination switched on.  :)
Now i have to do some binary search i think...

Re: G11 porting
« Reply #37 on: 27 / December / 2009, 09:54:38 »


*

Offline ERR99

  • ****
  • 339
Re: G11 porting
« Reply #38 on: 27 / December / 2009, 10:02:24 »
Okay, if find the AF-LED address, it is the same as for the SD1100IS:

LED AF: 0xC0223030

So this adress is allready the default LED-AF adress in the FW-Dumper tool (e.g. found in Blinker_Java_Version_by_Syrius.zip).
So i will try to create a FW-Dumper FI2 file for FW-Dumping based on this dumper.  :xmas

Re: G11 porting
« Reply #39 on: 27 / December / 2009, 10:10:50 »
« Last Edit: 27 / December / 2009, 11:42:19 by kingcang »

 

Related Topics