code you HAVE RUN on your dslr - page 11 - DSLR Hack development - CHDK Forum
« previous next »
Pages: 1 ... 6 7 8 9 10 [11] 12 13 14 15   Go Down

code you HAVE RUN on your dslr

  • 141 Replies
  • 89410 Views
*

ASalina

Re: code you HAVE RUN on your dslr
« Reply #100 on: 04 / June / 2008, 08:36:40 »
Advertisements
I don't know if this will help, but I've managed to accidentally completely reboot the 40D with buggy programs. In particular, the led scanner I started with caused this to happen. I threw some wild data somewhere and it caused a complete reboot.

I can try to recreate it later if it'll help.
Logged
*

Offline owerlord

  • ***
  • 115
Re: code you HAVE RUN on your dslr
« Reply #101 on: 04 / June / 2008, 09:57:10 »
Quote from: jeff666 on 04 / June / 2008, 07:44:26
1. garbage in memory which isn't initialized during startup
or
2. Multi-tasking-related CPU-settings are still active and code (other tasks) is run although it isn't valid anymore.

I tired all initialize code I could think of. The bootloader clears all pending proceses, and clears memory - I checked it by dumping the ram - all is cleared. I even copied the data section from the firmware - all with the same effect - restart, after waiting the screen get up and the menu apears - and nothing works.

As I wrote earler : the Startup Task code hangs in some part - and it don't reach the main initialization code.

ASalina: You tried to jump to FF810000 ? mayby the 40D don't have this problem. I'll make your work easyer.
Logged
*

Offline jeff666

  • ****
  • 181
  • A720IS
Re: code you HAVE RUN on your dslr
« Reply #102 on: 04 / June / 2008, 10:11:01 »
Quote from: ASalina on 04 / June / 2008, 08:36:40
I threw some wild data somewhere and it caused a complete reboot.

This is not what we need. We need a "controlled reboot" which
1. resets the hardware
2. lets us decide what code to execute afterwards.

Your "approach" probably didn't meet the second requirement.


Quote from: owerlord on 04 / June / 2008, 09:57:10
I tired all initialize code I could think of.

You don't address my suggestion. Did you run the code I posted (and that works in every CHDK-supported cam)?

Cheers.
Logged
*

Offline owerlord

  • ***
  • 115
Re: code you HAVE RUN on your dslr
« Reply #103 on: 04 / June / 2008, 10:57:10 »
"You don't address my suggestion. Did you run the code I posted (and that works in every CHDK-supported cam)?"

Maybe you didn't notice our tests, but:

!!! THE CODE IS VERY DENGEROUS !!!
Logged
*

ASalina

Re: code you HAVE RUN on your dslr
« Reply #104 on: 04 / June / 2008, 19:24:30 »
Quote from: jeff666 on 04 / June / 2008, 10:11:01
Quote from: ASalina on 04 / June / 2008, 08:36:40
I threw some wild data somewhere and it caused a complete reboot.

This is not what we need. We need a "controlled reboot" which
1. resets the hardware
2. lets us decide what code to execute afterwards.

Your "approach" probably didn't meet the second requirement.


I wasn't suggesting it as any kind of approach, of course. I was suggesting that it was possibly a clue to the reboot process.
Is there a memory location that controls power to the camera?
I don't know, but the camera seemed to cleanly reboot while in the "upgrade state."

Anyway, I'm trying to process 150M bytes of blinked out data with adc. Lots of SYNC errors. So I'm rather too busy to be defending myself here, right now.
Logged
*

Offline owerlord

  • ***
  • 115
Re: code you HAVE RUN on your dslr
« Reply #105 on: 04 / June / 2008, 19:31:48 »
Don't bother to defend yourself. Your observations are usefull - they suggest it's possible in the 40D. I didn't got a full restart even once on the 400D :-)

apropos, your analysing of data - if it fail - I can propose my method. more tests?, but It worked here, hope it'll work on 40D.
Logged
*

Offline _MAG_

  • *
  • 47
Re: code you HAVE RUN on your dslr
« Reply #106 on: 05 / June / 2008, 02:33:32 »
ASalina try isolate photodiode from external light. Or use non-internal sound card...
You use photodiode from mouse? They sense only IR light (need to filter i sink).
« Last Edit: 05 / June / 2008, 02:45:17 by _MAG_ »
Logged
*

ASalina

Re: code you HAVE RUN on your dslr
« Reply #107 on: 05 / June / 2008, 02:42:21 »
Quote from: owerlord on 04 / June / 2008, 19:31:48

apropos, your analysing of data - if it fail - I can propose my method. more tests?, but It worked here, hope it'll work on 40D.

If you have the time I would appreciate it. I've just spent >12 hours trying to dump and decode the rom without success. adc itself takes over two hours per run.
I'm thinking that I should modify the program so that it outputs a long string of 0xAA's
so I can capture it and figure out the maximum transmission rate to make calibration of the decoding program a bit easier, but I'd love to hear your method if you think it would be better.


@_MAG_

The photodiode is covered with black plastic tape and I'm using an old Ensoniq AudioPCI card (48khz max).
« Last Edit: 05 / June / 2008, 02:45:21 by ASalina »
Logged
*

Offline mx3

  • ****
  • 372
Re: code you HAVE RUN on your dslr
« Reply #108 on: 05 / June / 2008, 02:52:27 »
Quote from: ASalina on 05 / June / 2008, 02:42:21
but I'd love to hear your method if you think it would be better.
patch flasher so it would save ROM to card
Logged
skype: max_dtc. ICQ: 125985663, email: win.drivers(at)gmail, eVB decompiler
*

Offline DataGhost

  • ****
  • 314
  • EOS 40D, S5IS
    • DataGhost.com
Re: code you HAVE RUN on your dslr
« Reply #109 on: 05 / June / 2008, 03:21:36 »
Adc shouldn't take too long. I wrote my own one calibrated to my blinker. If your data did blink properly, you might have to adjust some settings in adc to get rid of the 'sync errors'.
Logged
Pages: 1 ... 6 7 8 9 10 [11] 12 13 14 15   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal