A495 porting thread - page 12 - DryOS Development - CHDK Forum supplierdeeply

A495 porting thread

  • 346 Replies
  • 98412 Views
Re: A495 porting thread
« Reply #110 on: 30 / May / 2011, 13:08:42 »
Advertisements
Delete all files except DISKBOOT.BIN.

After the camera crashes, is there a CHDK folder and subfolders on the card ?

Re: A495 porting thread
« Reply #111 on: 30 / May / 2011, 13:11:21 »
Ok - some interesting news:

First try: (CHDK Autoboot - Start with Playbackbutton)

Same thing like before (Card Error - CHDK bootscreen without logo - Card Error)

Second Try: (CHDK Autoboot - Start with pushing the On/Off button short)

Same thing like before

Third Try: (CHDK Autoboot - Start with pushing the On/Off Button for 2 seconds)

Cam boots normaly - (Card locked message) - the lens drives out - but them CHDK starts with the Logo-Screen !!!
After that the cam freezes with the attached image.

Re: A495 porting thread
« Reply #112 on: 30 / May / 2011, 13:15:32 »
Delete all files except DISKBOOT.BIN.

After the camera crashes, is there a CHDK folder and subfolders on the card ?

While power on the Cam in Playback mode with write protect and autostart SD-Card - Cam crashes and ther are no file other than the diskboot.bin on the card.

While Power on the cam with ON/OFF Button the same - no new files on the card.

Re: A495 porting thread
« Reply #113 on: 30 / May / 2011, 13:33:58 »
Cam boots normaly - (Card locked message)

Probably because the keyboard task is disabled.


Re: A495 porting thread
« Reply #114 on: 30 / May / 2011, 13:47:33 »
The clue staring me in the face here is that the spytask starts but when control goes back to the Canon firmware,  it detects the locked SD card and stops (normal behaviour for the camera when it sees a locked card and CHDK is not running).

So I need to wade through the code and figure out why it is not disabling the detection of the locked card. I seem to remember it ties in through kbd.c so microfunguy could be right about disabling the keyboard task being the exact wrong thing to do while debugging this.



Ported :   A1200    SD940   G10    Powershot N    G16

Re: A495 porting thread
« Reply #115 on: 30 / May / 2011, 14:09:14 »
Yes, the platform kbd.c 'my_kbd_read_keys()'

For example, lines 292 and 294 here http://tools.assembla.com/chdk/browser/trunk/platform/a480/kbd.c

Re: A495 porting thread
« Reply #116 on: 30 / May / 2011, 14:32:07 »
Yes, the platform kbd.c 'my_kbd_read_keys()'

For example, lines 292 and 294 here http://tools.assembla.com/chdk/browser/trunk/platform/a480/kbd.c
Yea - I got that far too - its identical to the A495 code.

So either :

1) the CHDK keyboard task (mykbd_task via taskcreate_PhySw_my) is not starting or
2) its crashing on a bad stub or
3) the SD_READONLY_FLAG is different between firmware version (seems unlikely). 

This is where trying to do this blind when you don't have access to the camera becomes painful.  My next step normally would be to start inserting code to blink the LED's at various steps in the process (poor man's debugger) until I figured out what was breaking.  Painful to do that remotely - you tend to wear out the patience of your volunteer testers.

Hmmmmm....
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A495 porting thread
« Reply #117 on: 30 / May / 2011, 14:37:59 »


Re: A495 porting thread
« Reply #118 on: 30 / May / 2011, 14:41:42 »
Let's try this - the Autofocus LED and the Green Power LED should come on and stay on if the code gets to the point where it tries to start the keyboard task.  If that works - I'll move the AF led to turn on when the actual keyboard task starts.
http://www.box.net/shared/b2yknn3d87
Ported :   A1200    SD940   G10    Powershot N    G16

Re: A495 porting thread
« Reply #119 on: 30 / May / 2011, 14:54:11 »

Only one light lights.

The green led flashes and stops when the camera hangs.

 

Related Topics