CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD - page 10 - Creative Uses of CHDK - CHDK Forum supplierdeeply
« previous next »
Pages: 1 ... 5 6 7 8 9 [10] 11 12 13 14 15 ... 71   Go Down

CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD

  • 704 Replies
  • 144928 Views
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #90 on: 04 / November / 2012, 11:07:33 »
Advertisements
Quote from: SticK on 04 / November / 2012, 10:56:29
   poke(0x7938, 0), without special preceding characters?
No, put "." or "=" before the Lua command (for example .poke(0x7938, 0)). You want to execute that on the camera.
Quote
I intend to do this in 2 steps:
  a) first keep the IS connected and wedge the toothpick, and if this passes,
  b) disconnect the IS+SHUTTER and test.
Hmmm, I thought you're talking about the iris and the shutter. So this won't do what you expect.
First of all, 0x7938 is only evaluated in connection with IrisError!
Second, by disconnecting IS, you'll most probably get a different error, not ISDriveError, and DisableISDriveError won't help.

I think you're expecting a single line solution. If there's a solution, it will be much more complicated than that.
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #91 on: 04 / November / 2012, 11:10:07 »
Oh my ... I'm sorry // my confusion .. the IRIS yes!  The IRIS is standalone, so I can disconnect it easy // will show results soon.
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #92 on: 04 / November / 2012, 12:10:11 »
RESULT .. this is interesting ...

> Disconnect IRIS
> PUP -> PLAY // OK (SHUTTER is CLOSED)
> poke()  // swallowed OK
> REC ==> SHUTTER opens -- nice.
> Camera does not go into REC (ie still "No Image" PLAY mode in live view), but, does not shut down
> PTP error after 1 minute (edit: if needed, a 2nd open window to test other commands)
> I shutdown using POWER BUTTON:  means camera still active!
> SHUTTER closes
> Camera shuts down
> PUP attempt
> Camera does not PUP (no USB) ==>> common after a major electrical aberration.
> Unplug AC adapter (to be sure)
> Reconnect IRIS  ==> Have to reconnect the offender to "revive" the camera.
> PUP OK
> REC OK - camera back to normal.

Now I can repeat the sequence.  I am trying to get the firminfo.txt file by

  =return call_event_proc("UIFS_WriteFirmInfoToFile",0)

but I get a return value of -1 and the txt file does not appear.  This is what I think I used once before when I got a successful txt file.
« Last Edit: 04 / November / 2012, 16:35:58 by SticK »
Logged
*

Offline Microfunguy

  • ****
  • 4037
    • StereoData Maker
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #93 on: 04 / November / 2012, 12:20:15 »
Did you do a "UI.Create" first ?
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #94 on: 04 / November / 2012, 12:34:49 »
Thank you. Attached.
Logged
*

Offline reyalp

  • ******
  • 13946
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #95 on: 04 / November / 2012, 15:32:21 »
Quote from: srsa_4c on 04 / November / 2012, 09:40:28
Stopping the watchdog alone won't solve the problems. Anyway, "System.Create" registers event procedures named "StartWDT" and "StopWDT". There is a good chance that calling these will have the same effect (i.e. nothing) as calling most of the Disable[some hardware] eventprocs.
StopWDT does work, I used it in the canon basic loader: http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Loader (IIRC if put a long blinker sequence early in the boot sequence, watchdog would be hit before the reboot was complete)

However, hitting the watchdog generates it's own specific romlog type, I don't think other errors rely on the watchdog to shut down.

taskBye seems to be responsible for normal shutdowns, not sure if it's used in error cases though. Digging through the exception hook code mentioned earlier might provide some insight.
Logged
Don't forget what the H stands for.
*

Offline srsa_4c

  • ******
  • 4451
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #96 on: 04 / November / 2012, 16:45:05 »
Quote from: reyalp on 04 / November / 2012, 15:32:21
However, hitting the watchdog generates it's own specific romlog type, I don't think other errors rely on the watchdog to shut down.
Right, the ROMLOG provided by SticK is old, so the watchdog doesn't seem to be hit.
The problem here is (as proven by SticK's latest post), that once control is reaching "hardwaredefect", it's already too late for normal operation. The error condition surely affects other parts of the code. Unfortunately the code generating this error is called indirectly, so it's hard to tell where the caller is.
Quote
taskBye seems to be responsible for normal shutdowns, not sure if it's used in error cases though. Digging through the exception hook code mentioned earlier might provide some insight.
Hooking DebugAssert seems to be easy (it provides a hook address), HardwareDefect doesn't provide such thing (and even if it did, it would be useless in this case).
Logged
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #97 on: 04 / November / 2012, 17:18:49 »
Lastest ROMLOG as of today ... note that even though USB was down (PTP error) I could still use the POWER button to shutdown.  This I presume was saved when USB went down.
Logged
*

Offline reyalp

  • ******
  • 13946
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #98 on: 04 / November / 2012, 17:29:24 »
Quote from: SticK on 04 / November / 2012, 17:18:49
Lastest ROMLOG as of today ... note that even though USB was down (PTP error) I could still use the POWER button to shutdown.  This I presume was saved when USB went down.
If the camera generates a romlog, it shuts down. If you were able to shut off with the power button, then it's extremely unlikely the romlog is connected with this event. The romlog contains a timestamp, so if you note when an event happens, you can determine if the romlog corresponds to that event.

Your romlog is in SsStartupTask.c which along with cameralog messages suggest it happened when preparing shoot mode (SS = shoot sequence or something like that)

The following cameralog items are interesting too:
Code: [Select]
00069320: M:LensError.c 0x01000000
00069320: M:IR_RST_E
00069320: M:LensError.c 0x20000000
IR_RST_E iris reset ?
Logged
Don't forget what the H stands for.
*

Offline SticK

  • *****
  • 779
Re: CHDKPTP: S90 Primary Focal Plane Configuration - hacking out the CCD
« Reply #99 on: 04 / November / 2012, 17:57:56 »
Quote "If you were able to shut off with the power button, then it's extremely unlikely the romlog is connected with this event. "
I did the procedure twice to be sure, and in both cases it was exactly the same.  On the first pass I myself was perplexed why PTP went down but I was still able to shutoff the camera with the POWER button, ie clean shutdown with shutter closure and PDN.  So on the second time I watched for that carefully, and yes the same thing.  Thus srsa's poke() override has some effect and must have something to do with this unusual behavior in my opinion.  I tabulated my procedure as carefully as I could so all the details would be there - I don't believe I missed anything.

Quote "IR_RST_E iris reset ?"
I don't think I'm the right guy to answer your question.  If you can elaborate, maybe I can help.
Logged
Pages: 1 ... 5 6 7 8 9 [10] 11 12 13 14 15 ... 71   Go Up
« previous next »
 

Related Topics