Executing Event Procedures by name - page 3 - General Discussion and Assistance - CHDK Forum supplierdeeply

Executing Event Procedures by name

  • 43 Replies
  • 19255 Views
*

Offline ewavr

  • ****
  • 1057
  • A710IS
Re: Executing Event Procedures by name
« Reply #20 on: 26 / December / 2009, 05:44:07 »
Advertisements
Well, it's a nice paperweight with a yellow LED.
Bad news...

Don't play with the "factory mode" stuff unless you are very sure what you are doing.

May camera be in factory mode? How about USB connection, it works?

*

Offline reyalp

  • ******
  • 13443
Re: Executing Event Procedures by name
« Reply #21 on: 26 / December / 2009, 05:52:07 »
May camera be in factory mode? How about USB connection, it works?
:o

If I plug it in, I get new hardware found "DCP connect". Naturally, windows does not have a driver for it. Libusb test program doesn't see it. Shows up as an unknown device in dev manager.

Oh, and I get green and yellow led.

edit:
lsusb on linux says ID 04a9:3086 Canon Inc.
« Last Edit: 26 / December / 2009, 05:54:34 by reyalp »
Don't forget what the H stands for.

*

Offline ewavr

  • ****
  • 1057
  • A710IS
Re: Executing Event Procedures by name
« Reply #22 on: 26 / December / 2009, 06:02:36 »
If I plug it in, I get new hardware found "DCP connect".
Indeed, this is factory mode.
So, CHDK (in minimal configuration, boot.c only without spytask ) can be loaded?

*

Offline reyalp

  • ******
  • 13443
Re: Executing Event Procedures by name
« Reply #23 on: 26 / December / 2009, 06:12:34 »
If I plug it in, I get new hardware found "DCP connect".
Indeed, this is factory mode.
So, CHDK (in minimal configuration, boot.c only without spytask ) can be loaded?
I'm working on that, thanks for your hints :)
Don't forget what the H stands for.


*

Offline reyalp

  • ******
  • 13443
Re: Executing Event Procedures by name
« Reply #24 on: 26 / December / 2009, 06:22:03 »
Yay

ClearFactoryMode()


Thanks ewavr!
Don't forget what the H stands for.

Re: Executing Event Procedures by name
« Reply #25 on: 26 / December / 2009, 07:07:00 »
That is the first recorded 'bricking' of a camera by CHDK and definitely the first disaster-recovery !


*

Offline reyalp

  • ******
  • 13443
Re: Executing Event Procedures by name
« Reply #26 on: 26 / December / 2009, 07:21:43 »
That is the first recorded 'bricking' of a camera by CHDK and definitely the first disaster-recovery !
Wasn't really bricked, luser error.  :-[

I wanted to see what factory mode looked like. Turns out, it looks like a brick! But the camera is actually running. Even CHDK was running, but it doesn't display and PTP doesn't load.

But yeah, I'll be a little more cautious before calling random eventprocs.

So
FA.Create registers the factory mode functions.
SetFactoryMode (I think, I tried several) sets something in ROM which indicates factory mode.
ClearFactoryMode undoes the ROM setting. ClearFactoryMode can be called from CHDK spytask with the appropriate wrapper.

Both call WRITEADJTABLETOFROM which I guess does the deed. I wonder if this means my original factory adjustments have been nuked ?

If anyone wants to roll the dice, there's also
SetDurianMode
ClearDurianMode

Durian ?!?
Don't forget what the H stands for.

*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Executing Event Procedures by name
« Reply #27 on: 26 / December / 2009, 08:01:49 »
haha, "don't forget what the H stands for" never made more sense than in this thread :D
great you recovered the cam.
 


*

Offline whoever

  • ****
  • 280
  • IXUS950
Re: Executing Event Procedures by name
« Reply #28 on: 26 / December / 2009, 12:31:21 »
Congratulations on the quick success! And "durian" definitely sounds like an irresistible temptation, what a pity that I don't have one in my cam...

Now, after the happy end, I admit it was a bit of disappointment, -- I actually hoped that we would get a working flasher in the end of your adventure. Alas, let's wait till ewavr bricks his ;)

P.S. Thanks, Wim. Very sobering, indeed.
« Last Edit: 26 / December / 2009, 13:27:41 by whoever »

*

Offline fe50

  • ******
  • 3134
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Executing Event Procedures by name
« Reply #29 on: 26 / December / 2009, 12:39:03 »
Both call WRITEADJTABLETOFROM which I guess does the deed. I wonder if this means my original factory adjustments have been nuked ?
I guess rather not...let badpixel.lua report the bad pixels from your reanimated bady...

*EDIT: did you check the SD card ? maybe there are some log files, like DC97/MISC/CANON/FACTORY/RSTFNO

PS: would be nice if we could find a Canon service manual for one of the newer Powershots,
i guess the service tools & procedures should be similar on many cameras,
as on the good old Pixma IPxxx printer series...


BTW - Yeah: Don't forget what the H stands for.  :haha
« Last Edit: 26 / December / 2009, 12:47:47 by fe50 »

 

Related Topics