The SX1 IS Porting Thread - page 26 - General Discussion and Assistance - CHDK Forum

The SX1 IS Porting Thread

  • 381 Replies
  • 112172 Views
Re: The SX1 IS Porting Thread
« Reply #250 on: 13 / May / 2009, 08:46:06 »
Advertisements
pev69,
thanks for the tip on the user menu.  Sorry to be a pain in the butt, I wish I could help somehow.

*

Offline reyalp

  • ******
  • 12373
Re: The SX1 IS Porting Thread
« Reply #251 on: 14 / May / 2009, 01:09:06 »
See reply #212:
http://chdk.setepontos.com/index.php/topic,3410.msg33101.html#msg33101

Hey reyalp, or other devs, perhaps the debug_led should be permanently disbled for the SX1 for now?! Because no direct address has been found for other than the AF assist lamp. Actually it should be fixed from the core code, something stupid is going on that turns the debug LED off repeatedly.
Try looking at sub_FF905E5C, I think the LED addresses should be based from 0xC02200B4
Don't forget what the H stands for.

*

Offline rlk

  • *
  • 9
Re: The SX1 IS Porting Thread
« Reply #252 on: 15 / May / 2009, 12:12:22 »
I got it to work on an 8 GB card.  This is very useful, since my wife's nephew is performing in a concert tomorrow and I'd like to be able to video it in HD.  Here's exactly what I had to do:

1) Create two partitions on the card.  I created a 2 MB partition and a balance of the card partition.

In Linux, the commands were as follows.  Note that "-" is something you do, "#" is the superuser prompt (don't type it), ">" is the prompt from a command, and ">>" is the prompt from a sub-command.

Code: [Select]
- Insert the card into the computer.  Make sure it's unlocked.  If there is an existing filesystem or filesystems on the card, unmount them!
# fdisk /dev/mmcblk0 [i](note that this will vary depending upon your hardware)[/i]
> [i]delete all existing partitions[/i]
> p [i](create a partition)[/i]
>> 1 [i](partition 1)[/i]
>> 1 [i](start on cylinder 1)[/i]
>> +2M [i](2 MB)[/i]
> p [i](create a partition)[/i]
>> 2 [i](partition 2)[/i]
>> (enter) [i](start on the first available cylinder)[/i]
>> (enter) [i](default -- the rest of the card)[/i]
> w [i]write the partition table out[/i]
> q
# mkdosfs -F 16 -n CHDK /dev/mmcblk0p1 [i](create a FAT16 filesystem with volume name CHDK -- that's optional -- on the first partition)[/i]
# mkdosfs -F 32 -N CANON_SX1 /dev/mmcblk0p2 [i](create a FAT32 filesystem on the second partition -- again, the name is optional, but my import script uses it)[/i]
[i]Make sure the filesystems aren't mounted at this point![/i]
# dd if=/dev/mmcblk0p1 of=bootsect.bin bs=512 count=1
- Hex/binary edit bootsect.bin; starting at byte 0x40, change the next 8 bytes to "BOOTDISK"
# dd if=bootsect.bin of=/dev/mmcblk0p1
- Mount the card -- depending upon your system setup, it might be to remove the card from the reader and reinsert it
- Find where the two filesystems are mounted -- it might be something like /media/CHDK and /media/CANON_SX1.  We'll assume that the first, small partition is at /media/CHDK and the big one is at /media/CANON_SX1.
# cp VERS.REQ DISKBOOT.BIN /media/CHDK
# cp -r CHDK /media/CANON_SX1
- Umount and remove the card.
- Lock the card.
- Insert the card in the camera and turn the camera on.

At this point, CHDK booted -- but the card showed up with only about 1 MB free, so obviously it wasn't seeing the second partition.  So in CHDK, I did the following:

- Press the alt button
- Menu
- Debug
- Create card with two partitions

Of course, once I turned the camera off, CHDK was no longer available.  No problem.  Reinsert the card into the computer (make sure the partitions aren't mounted), and repeat all the steps starting from the first mkdosfs command.  Now it all works.

I'm not positive why my initial attempt didn't work.  I suspect that the problem is that I wasn't setting the two partitions to the correct system ID.  It's possible -- indeed, likely -- that if I did the following fdisk command everything would have worked correctly from the get-go:

Code: [Select]
# fdisk /dev/mmcblk0 [i](note that this will vary depending upon your hardware)[/i]
> [i]delete all existing partitions[/i]
> p [i](create a partition)[/i]
>> 1 [i](partition 1)[/i]
>> 1 [i](start on cylinder 1)[/i]
>> +2M [i](2 MB)[/i]
> p [i](create a partition)[/i]
>> 2 [i](partition 2)[/i]
>> (enter) [i](start on the first available cylinder)[/i]
>> (enter) [i](default -- the rest of the card)[/i]
> t [i](change a partition's system ID)[/i]
>> 1 [i](partition 1)[/i]
>> 1 [i](ID 1 -- FAT12)[/i]
> t [i](change a partition's system ID)[/i]
>> 1 [i](partition 2)[/i]
>> b [i](ID 0xb -- W95 FAT32)[/i]
> w [i]write the partition table out[/i]
> q

Re: The SX1 IS Porting Thread
« Reply #253 on: 15 / May / 2009, 12:31:59 »
No problems with chdk and cards greater then 4GB for me.  I used the standard mac instructions.
« Last Edit: 16 / May / 2009, 09:46:03 by miahill9 »


*

Offline pev69

  • **
  • 55
Re: The SX1 IS Porting Thread
« Reply #254 on: 15 / May / 2009, 22:55:42 »
... and this should end the general discussion here about making CHDK work, because this is the _SX1_ porting thread. CHDK works in SX1 normally with the booting method and not with the FW update method and that's it. So unless you have new suggestions about fixing the FW update method in SX1 (or other SX1 specific issues), all other general CHDK queries and instructions should go to other threads.
« Last Edit: 15 / May / 2009, 23:08:40 by pev69 »

Re: The SX1 IS Porting Thread
« Reply #255 on: 16 / May / 2009, 12:21:14 »
It's not working:
Quote
The TX1 and 'S' series cameras have a separate button for video mode but these can still be started with the remote switch.
To enter the Rec control mode, push the Movie Button for a short time (less than 0.5Sec), the blue <ALT> LED will light.
(If you push the Movie Button for more than 0.5Sec, the camera will start normal movie recording).
In the Rec control mode, when you press/release the remote switch, the camera starts recording, exits the Rec control mode and the blue <ALT> LED turns off.
To stop movie recording, re-enter the Rec control mode by briefly pressing the movie button and then press/release the remote switch.(or push the Movie button for longer than 0.5Sec.).
The camera Sx1 has two buttons, one for video, one for a photo. After activation of the remote control the camera does a picture, and should make video entry.
Whether probably to correct it in the following version?

*

Offline rlk

  • *
  • 9
Re: The SX1 IS Porting Thread
« Reply #256 on: 16 / May / 2009, 17:29:06 »
I'm having what appears to be a performance issue recording video in HD mode.  After a few seconds (exactly how long depends upon the video quality setting -- at max quality, almost immediately; at lower quality it takes a bit longer) I see a vertical row of boxes near the right edge of the screen, with the bottom one or two filled in.  After a bit longer, four boxes fill in and they turn red, and then recording shuts off. 

I presume the boxes indicate how much buffering is being used by the camera; when the buffer fills up, recording (of necessity) shuts off.

This works fine without CHDK.  Reformatting the card (nuking CHDK), works fine again.

I'm using a generic (Micro Center branded) class 6 8 GB SDHC card, in case it matters (which it might very well).  Has anyone else observed this?

Re: The SX1 IS Porting Thread
« Reply #257 on: 16 / May / 2009, 21:01:54 »
I'm having what appears to be a performance issue recording video in HD mode.  After a few seconds (exactly how long depends upon the video quality setting -- at max quality, almost immediately; at lower quality it takes a bit longer) I see a vertical row of boxes near the right edge of the screen, with the bottom one or two filled in.  After a bit longer, four boxes fill in and they turn red, and then recording shuts off. 

I presume the boxes indicate how much buffering is being used by the camera; when the buffer fills up, recording (of necessity) shuts off.

This works fine without CHDK.  Reformatting the card (nuking CHDK), works fine again.

I'm using a generic (Micro Center branded) class 6 8 GB SDHC card, in case it matters (which it might very well).  Has anyone else observed this?

I am assuming that you are talking about shooting video directly, no scripts or use of the remote?

I am using a class 6 4GB Sandisk that was partitioned.  As far as I understand, it is not strictly necessary to partition up to and including 4GB cards - I did it simply to keep the data recorded in a FAT32 sector, no other reason.

I have shot several HD videos varying from full natural HD to CHDK fully compressed HD (setting at 1) while CHDK is on board the camera (not in alt mode) and I have had no problem like yours.

In your case you must make a separate partition because FAT12/16 cannot work on cards greater than 4GB.  Is it a problem with incorrect card formatting slowing down data speed (just a guess)??


*

Offline rlk

  • *
  • 9
Re: The SX1 IS Porting Thread
« Reply #258 on: 17 / May / 2009, 10:15:21 »
I am assuming that you are talking about shooting video directly, no scripts or use of the remote?

I am using a class 6 4GB Sandisk that was partitioned.  As far as I understand, it is not strictly necessary to partition up to and including 4GB cards - I did it simply to keep the data recorded in a FAT32 sector, no other reason.

I have shot several HD videos varying from full natural HD to CHDK fully compressed HD (setting at 1) while CHDK is on board the camera (not in alt mode) and I have had no problem like yours.

In your case you must make a separate partition because FAT12/16 cannot work on cards greater than 4GB.  Is it a problem with incorrect card formatting slowing down data speed (just a guess)??

That's correct -- just ordinary video.

It's certainly possible that incorrect formatting is causing the problem.  Any guidelines about how best to format the card?

Re: The SX1 IS Porting Thread
« Reply #259 on: 17 / May / 2009, 11:47:29 »
Comments struck out because of feedback from anOn

(feeling foolish right now.... :( )

For fboesch, pev69 and others...

I've been doing some more testing and found the following; (sorry if it may have been previously mentioned)


Half Press + Down Click
Regarding Disable Overrides (Extra Photo Operations)
First, as a newbie this is very confusing - we seem to have disable x disable = enable which is okay for a programmer but confusing for the rest of the world.

Anyhow, according to the User Guide, this "Allows the use of a half-press + DOWN button press to quickly toggle any override settings on and off."

However, using half shutter and down click does not do this on the SX1 IS, instead it enables  / disables the histogram which as I reported previously seems to be addressing the wrong memory at half press so I wonder if these two errors are linked?


Half Press + Up Click
This is the most difficult one.
If the zebra pattern is disabled....
** - With all overrides set to Off, and the menu item "Disable Overrides" set to ON or OFF, the Status will toggle from OFF / ON /OFF with each up click.  When ON is selected, the screen display comes up with "NO OVERRIDES", but when OFF is selected, the "NO OVERRIDES" status remains on screen until half press is released.

With any override such as Tv enabled, (Factor = 1), the same thing will happen as above except that the screen information will toggle immediately in the ON and OFF direction between "NO OVERRIDES" and "Tv 1.000" (for example) (as expected)

With the menu item "Disable Overrides" set to DISABLED, nothing changes with each up click (also as expected)


If the zebra pattern is enabled in the case of the double asterisk above, the function is the same, except that th "NO OVERRIDES" message will be cleared from the screen correctly at each toggle OFF. (as expected - possibly because of additional screen updating taking place)

In all of the above cases, MF is also being toggled ON and OFF with the Overrides with each up click which is not desirable.


So in summary, it seems that the down click is affecting the histogram, and what should be the down click is actually being activated by an up click.


Also, regarding the zebra pattern, I have found that if I have the Canon gridlines displayed and I activate it, the top 4~5mm of the two vertical lines remain on screen (but you probably found this already) - maybe something to do with the screen addressing difficulties?



---------------------------------------------------

Additional Information For Newbies Like Me - who are discovering the little secrets of this wonderful software...

The April 2009 User Guide is an excellent document but as I believe is known by the developers, one or two items have been omitted, this being a couple of them

Half Press + Right Click
A half press of the shutter and right click on the controller has the effect of turning the Show OSD (OSD Parameters) menu item on or off.  Although this is not mentioned in the User Guide, it is mentioned here http://chdk.wikia.com/wiki/CHDK_firmware_usage

Half Press + Left Click
This has the effect of toggling ON/OFF the Zebra Grid.   - again its mentioned here http://chdk.wikia.com/wiki/CHDK_firmware_usage
« Last Edit: 18 / May / 2009, 00:23:00 by archiebald »

 

Related Topics