Task can dump firmware from 0xFFC00000 (Mostly matches blinked firmware, looks like I just have an error log).It's possible, it appears some newer non a-series cameras are now starting at 0XFFC00000
ROM:FFC00058 LDR R0, =0xFFC0002B
ROM:FFC0005C MCR p15, 0, R0,c6,c5
FFC0013C loc_FFC0013C ; CODE XREF: ROM:FFC00148j
ROM:FFC0013C CMP R1, R3
ROM:FFC00140 LDRCC R2, [R0],#4
ROM:FFC00144 STRCC R2, [R1],#4
ROM:FFC00148 BCC loc_FFC0013C
ROM:FFC0014C LDR R1, =0x12AD3C
ROM:FFC00150 MOV R2, #0
ROM:FFC00154
ROM:FFC00154 loc_FFC00154 ; CODE XREF: ROM:FFC0015Cj
ROM:FFC00154 CMP R3, R1
ROM:FFC00158 STRCC R2, [R3],#4
ROM:FFC0015C BCC loc_FFC00154
ROM:FFC00160 B loc_FFC001A0
.section .entry
.org 0x1ef4
MOV R0, #2
TEQ R0, #2
LDR SP, =0x1900
MOV R11, #0
B startup
I get 4 logos rather than one, but I think that's a different issue.I presume that you have wrong values for vid_get_bitmap_buffer_width() or vid_get_bitmap_screen_width() in platform/*/sub/*/lib.c file. I had similar problem and substituting 720 for 360 fixed it for me.
Yes, this is how the sd990 looked at first: http://chdk.setepontos.com/index.php/topic,2972.msg29795.html#msg29795 (http://chdk.setepontos.com/index.php/topic,2972.msg29795.html#msg29795)QuoteI get 4 logos rather than one, but I think that's a different issue.I presume that you have wrong values for vid_get_bitmap_buffer_width() or vid_get_bitmap_screen_width() in platform/*/sub/*/lib.c file. I had similar problem and substituting 720 for 360 fixed it for me.
The video stuff was partially those settings, but once that was resolved the aspect ratio was also off. I found the SX200IS did some hacks to adjust the aspect ratio and incorporated them into the SD1200IS. I also got the keyboard working. Things seem to be in pretty good shape now. Oh and raw shooting works in CRW mode.Have you verified that the raws have correct image data ? On some cameras, there are multiple buffers. If you only have one right, this could cause the badpixel problem.
Zebra/Edge Overlay don't seem to be using the right data (probably a wrong vid buffers?)Could be. Note that the sx200 zebra fix is #ifdef'd for sx200 only right now.
Screen refresh is kind of weird. Like if I exit a menu but the previous menu was smaller then i still can see the exited menu.Are you sure they exit themselves, or is the canon firmware just erasing them ? The latter is normal.
Sometimes menus exit by themselves
No way to exit main menu (?) Is this normal? Or because I'm using my PLAY key as PRINT/ALT?Pressing menu in alt mode should toggle the CHDK menu.
Have you verified that the raws have correct image data ? On some cameras, there are multiple buffers. If you only have one right, this could cause the badpixel problem.I've developed multiple images and they correspond with the associated JPEG.
Are you sure they exit themselves, or is the canon firmware just erasing them ? The latter is normal.Okay just verified and indeed the menus are still active, just that they are overwritten. Using the down arrow selects the next item and does a redraw.
This seems to be an issue on newer cameras http://chdk.setepontos.com/index.php/topic,4333.0.html (http://chdk.setepontos.com/index.php/topic,4333.0.html)Have you verified that the raws have correct image data ? On some cameras, there are multiple buffers. If you only have one right, this could cause the badpixel problem.I've developed multiple images and they correspond with the associated JPEG.QuoteAre you sure they exit themselves, or is the canon firmware just erasing them ? The latter is normal.Okay just verified and indeed the menus are still active, just that they are overwritten. Using the down arrow selects the next item and does a redraw.
The main menu issue is similar, pressing menu does indeed toggle the menu, however it stays visible until canon overwrites it.
I don't know if any of you guys have been working on this at all, but if the SD 1200 was ported I would really really appreciate itSee http://chdk.wikia.com/wiki/FAQ#Q._My_camera_isn.27t_ported_yet._Is_a_port_planned_.3F_When_will_it_be_ready_.3F_How_can_I_help_.3F (http://chdk.wikia.com/wiki/FAQ#Q._My_camera_isn.27t_ported_yet._Is_a_port_planned_.3F_When_will_it_be_ready_.3F_How_can_I_help_.3F)
I'd even try to pay 10 bucks or so through pay pal to whoever could get it ported before dec 10th if it enabled my camera to do raw pictures and time-elapses. I know that that sounds like a scam, so you'd have to take my word on it (from my end, 10 bucks to take raw pictures / make hdrs and time elapses is worth it).:lol
I haven't seen any left overs since playing with the stubs and eventually changing RefreshScreen to match ScreenUnlock (As I though I had done originally when I was experiencing problems.) So it's possible I'm just mistaken about before and my settings were wrong when I saw the problem, or perhaps there is a certain use-case that causes the screen left overs that I encountered before.means that menus opened before are already closed and not appearing into screen and, if so, what am i wating to place this on my camera? o yeah my sd got broken. ill try to use some codes from other ports (that i think shouldnt work) and try to port them to 1200is (if i am lucky) just to see what can i get.
Yeah, I think its a bug in CHDKA feature, not a bug ;)
I made a new folder 101Canon so the JPG ends up in 101 and the raws are in 100Canon :(
RAW File in Dir with JPEG Enable [?] / Disable [ ](https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fimages3.wikia.nocookie.net%2F__cb20080702211009%2Fchdk%2Fimages%2F8%2F8c%2FAllbest51-425_SD400_RAWMenu.jpg&hash=0e3ce97f09b572331d26f1f9ce2d7c13)
Saves RAW files in the same folder as the JPEG files. If disabled then RAW files are always saved in the 100CANON folder.
| u:get_usb_power | |
| 1: psysw_status[0] | 1:conf.mem_view_addr_init |
| 2: psysw_status[1] | f:focus busy |
| 3: psysw_status[2] | z:zoom busy |
" BL sub_FFC11B20\n"in boot.c taskcreate_Startup_my()
For diskboot startup, I suggest commenting outOoops, this is the wrong one. That would be for the play/rec power up handling.Quote" BL sub_FFC11B20\n"in boot.c taskcreate_Startup_my()
I tried commenting that line out and compiled.I was told that the current version crashes. If you get a card locked instead with only this change, that means it's a step in the right direction. If you simply get "card locked" with any diskboot, it may not be loading at all (BOOTDISK string not in place, not encoded with dancing bits, or other problem)
I have a 2gb SD card formatted with fat16. When I put in the locked card with the diskboot file it just starts normally and displays card locked.
Since starting normally using the PS.FI2 does not get around the SD write protect I suspect there are other things in the way including the write protect check and bypassThe write protect override is done in the keyboard task. See SD_READONLY_FLAG
As far as I know the diskboot.bin just has not worked so far and we primarily use it with the PS.fi2 boot method.
Yes AirForceOne but I am not sure that's what I've read and everybody seems to be sure about this, but there's still a small possibility this camera just works in a different way, however it easy to think that it is simply not-possible because the aperture seems to be somehow attached to zooming (when zooming farther aperture is bigger ranging from 2.8 on 1x to 4.9 in 3x optical zoom), I will try to buy an adapter and some lenses for this camera when i have a chance and see the quality of the pictures so I could say if changing aperture manually on an adapted lens is useful or somehow worth the money. I have links to the amazon article if someone is interested on trying (I'm wishing to find more feedback about the adapter and lenses before trying it myself)
if someone has tried them before post what you think of it.
I would like to merge this with the main trunk on https://tools.assembla.com/chdk/, but i don't know how to proceed about that, since I don't have any experience with SVN and online collaboration projects.
The font on this is small but readable.
How would one use the flash feature? I attempted to change the manual setting to adjust power level, but it doesn't seem to change it.
Do you think repairing the USB remote function would be a difficult task?
As far as I know none of the manual overrides in the menu work. However the shutter speed can be adjusted through one of the scripts up to 64 seconds.
The functions for changing focus modes, zooming from script, USB remote appear to be working fine through the script. USB remote appears to work without a script too but I think I have a setting wrong for the sync.
Anyway, I'm uploading sources, and diff log to trunk 903. Have fun.
When i'm configuring the colors of the menu and stuff, the colors to choose from are different in play mode and record mode.It's not really a bug, it's a kind of "feature": the original Canon firmware use different color palettes in playback & record mode on most (IMO all) cameras...
the thing with the resolutionDid someone try to solve this with the ASPECT values in camera.h ?
when I took long exposure photos for light painting or stuff like that, there was somewhat purplish stain in the top left corner...Amp glow; on long exposures, the darkframe subtraction setting may help somewhat...
Firmware Ver GM1.00BFrom what I've heard, Canon almost never offers firmware updates. If you have a firmware different from 100c, it will not work for you. The only way is to make a new port.
I'm uploading the capt_seq.c file with overrides fixedAdded to the trunk, changeset #912 (http://tools.assembla.com/chdk/changeset/912/).
Yossar - is the port ready for the Autobuild Server ?
Works fine on my ixus 95 is! Thanks!I compiled without those features (and games) since I haven't needed them for testing. If you can't wait for autobuild, you can try compiling the sources with chdk shell.
Cant find text reader and calendar in misc menu. Is it a bug or feature?
PS. When I make fat16 1Gb card bootable from CHDK menu - the DISKBOOT file do not starting with locked card. Only manual starting with PS.FI2Autostart (with diskboot.bin & locked card) is only possible with FAT12 or FAT16 formatted partitions, this is a limit of the Canon firmware loading mechanism.
Do you know any other way of first upgrading my firmware to 100c?I think firmware update will be possible at canon repair-support centers or via mail to canon support-site.
Or would it be very difficult to compile CHDK for the 100b version?
I'm not sure they will upgrade your firmware without a specific problem. Asking them to upgrade it so you can run CHDK might not be a good idea.Do you know any other way of first upgrading my firmware to 100c?I think firmware update will be possible at canon repair-support centers or via mail to canon support-site.
Or would it be very difficult to compile CHDK for the 100b version?
Compilation of chdk for 100b (i think) will be more difficult and longer process.Depends. If you are a programmer and understand CHDK, you can probably do it in less time than shipping to canon and back: http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version (http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version)
(freshly formated with my camera; 2Gb).Did you try Yossar's firmware? Did it started on your formated card?
It is not crappy, it is lovely.
CHDK may be somewhat handy for SD1200, but it's really-really pity that there is no real aperture (iris) in the camera. DOF is unresolvable issue on my sister's SD1200 (why,WHY did buy her this cam:((), so it kills the full joy of ability for long exposure & RAW it'd have with CHDK. I'm not counting scripts here, you know what I mean ;( My "old reliable" A720IS is much better. :)
Thanks, 13k lines of code, I asked and I got it!How many codes would you have to write and where?
What does your question mean, I cannot understand it ?
Do yourself a favour, buy a Panasonic FZ38 or similar, like I have.
I am having trouble finding the "Firm Update" option in the menus. It should be right bellow the "Transition" option right?Yes; it's only there when you've started the camera in PLAYBACK mode (with the [>] button)...
Just start the camera in PLAYBACK mode !
The "Firmware update" menu item is visible when the camera is started in playback mode (lens retracted) & there's a file "PS.FI2" stored in the card's root...
raw is so so though not very happy with quality, also it takes too much time saving on card, ufraw may be used to open
CHDK may be somewhat handy for SD1200, but it's really-really pity that there is no real aperture (iris) in the camera. DOF is unresolvable issue on my sister's SD1200 (why,WHY did buy her this cam:((), so it kills the full joy of ability for long exposure & RAW it'd have with CHDK. I'm not counting scripts here, you know what I mean ;( My "old reliable" A720IS is much better. :)
Now then, who already has anything _worth_ to show using wonderful CHDK on this crappy little camera, any creative use?
I've checked in the screen layout stuff based on hwntws report in PM.
Still looking for report on diskboot.
There is some serious WTF inboot.call of this port, but it will be difficult to sort out without having the camera.
edit:
looks like the main problem was NEED_ENCODED_DISKBOOT not set at all :blink:, explains the card locked message with diskboot present.
I've set the correct diskboot encoding for this camera, and checked in the other changes.http://drop.io/reyalp_chdk/asset/ixus95-sd1200-100c-0-9-9-diskboot-test-1-zip (http://drop.io/reyalp_chdk/asset/ixus95-sd1200-100c-0-9-9-diskboot-test-1-zip)
I've added a new build that uses low memory zebra like sx20. This will be uglier, but might work:
http://drop.io/reyalp_chdk/asset/ixus95-sd1200-100c-0-9-9-zebratest-1-zip (http://drop.io/reyalp_chdk/asset/ixus95-sd1200-100c-0-9-9-zebratest-1-zip)
I am almost embarassed to ask, but quite frankly I do not understand this process of encoding with keys.You don't need any keys to make diskboots, just a version of dancingbits which supports the desired encoding version. The latest in the chdk tree supports all known variants. Keys are needed for FI2. (quite why one is OK in the CHDK tree and the other is not, I don't know... possibly historical accident)
I have set encoding to '2' for the IXUS95 but it does not work (card locked).
Do I need keys for all the cameras that have encoded diskboots ?
I can also confirm diskboot working now. With zebra, the green AF indicator boxes prevent zebra from being drawn below them (zebra stops maybe 20 rows above them), and the draw over modes are not functional.Low memory mode means zebra won't restore anything.
DNG output still looks funny, the green channel seems to be completely missingMaybe the bayer pattern is wrong. Here's a build with "Red Green Green Blue" instead of "Green Blue Red Green"
CRW screenshot (http://www.rootzilla.org/~para/pics/ixus/crw.jpg)
DNG screenshot (http://www.rootzilla.org/~para/pics/ixus/dng.jpg)
Everything else seems to be working pretty well now. If anyone wants me to test something specific just tell me :)
Maybe the bayer pattern is wrong. Here's a build with "Red Green Green Blue" instead of "Green Blue Red Green"Thanks, that's much better 8)
http://drop.io/reyalp_chdk/asset/ixus95-sd1200-100c-0-9-9-dngtest-1-zip (http://drop.io/reyalp_chdk/asset/ixus95-sd1200-100c-0-9-9-dngtest-1-zip)
Note that the color matrix appears to copied from sd990, so it the calibration will probably be a bit off.
#define CAM_COLORMATRIX1 \
1484685, 1000000, -530958, 1000000, -208054, 1000000, \
143142, 1000000, 793552, 1000000, 83907, 1000000, \
146290, 1000000, -44679, 1000000, 430414, 1000000
#define CAM_ACTIVE_AREA_X1 8
#define CAM_ACTIVE_AREA_Y1 12
#define CAM_ACTIVE_AREA_X2 3692
#define CAM_ACTIVE_AREA_Y2 2772
I can also confirm diskboot working now. With zebra, the green AF indicator boxes prevent zebra from being drawn below them (zebra stops maybe 20 rows above them), and the draw over modes are not functional.
Low memory mode means zebra won't restore anything.QuoteDNG output still looks funny, the green channel seems to be completely missingMaybe the bayer pattern is wrong. Here's a build with "Red Green Green Blue" instead of "Green Blue Red Green"
CRW screenshot (http://www.rootzilla.org/~para/pics/ixus/crw.jpg)
DNG screenshot (http://www.rootzilla.org/~para/pics/ixus/dng.jpg)
Everything else seems to be working pretty well now. If anyone wants me to test something specific just tell me :)
http://drop.io/reyalp_chdk/asset/ixus95-sd1200-100c-0-9-9-dngtest-1-zip (http://drop.io/reyalp_chdk/asset/ixus95-sd1200-100c-0-9-9-dngtest-1-zip)
Note that the color matrix appears to copied from sd990, so it the calibration will probably be a bit off.
Thanks, that's much better 8)I've checked both of these in.
After fiddling around a bit with dng4ps2 and the Adobe dng validator, I came up with these additional changes:
Not sure if this is an issue, but bracketing doesn't work if you set the camera in custom timer mode (worked with this - http://chdk.setepontos.com/index.php/topic,4324.msg52457.html#msg52457 (http://chdk.setepontos.com/index.php/topic,4324.msg52457.html#msg52457) build). Of course, it's not really a problem, since we have scripts, but sometimes it would be just a bit easier to do this with custom timer.I can confirm this- and doing the equivalent in SDM will run the bracketing sequence properly.
Also, "native" video zoom doesn't work, although works ok with scripts.
Otherwise great work, thanks to everyone who's helping with builds :)
The ixus95 does not have multipartition support implemented yet. Since diskboot now works, there's no reason to expect that multipartition won't work on this camera when someone gets around to implementing it.Hello,The CHDK folder can be in either partition.CHDK will only use the folder on the same partition the rest of the camera sees. In a bootable dual partition setup, this means your CHDK folder must be on the large partition. Only diskboot.bin on the small partition is used.QuoteI used SDMInste to set up my 16Gb so that both partitions are ~8G, so that if I set the switch on the card to 'Lock', I load chdk, and if I unlock it, it doesn't, and there's still enough space on the primary partition for the camera to store images in it when not running chdk.Are you saying that CHDK successfully autoboots from a FAT32 partition if you have the lock engaged ? If this is true, then you don't need to partition at all. If it isn't true, there's something wrong with your description.
The normal way to have the camera see the large partition without CHDK is to swap them so the large one is first. You can normally swap back by manually loading CHDK, but AFAIK that is not available on sx20 (someone might want to try the my canon basic manual loading method...)
I would like to try this as my Ixus 95 does not support using two partitions and the SDM intstaller method, among others, does not work, sadly.
I have already posted that my Ixus 95 will reboot using your Canon Basic method. What I now need help with is how to use it in order to mimic the two partition boot method- one very small fat1n and one large fat32 partition for autoboot plus max use of space.
../lib/armutil/libarmutil.a(reboot.o): In function `reboot':
reboot.c:(.text+0x64): undefined reference to `_reboot_fw_update'
collect2: ld returned 1 exit status
Oops, I didn't update the checked in version of stubs_entry.S for this camera when I added ptp support, because this camera isn't in the batch builds.Does the PTP support have anything interesting added? I recall there was an extended set of PTP tools developers could use for debugging and all that.
I've updated it. You could also build with PRIMARY.BIN in place to generate it yourself.
please someone who owns sd1200 test how much memory is free after chdk loading on SD1200 in play mode with empty memory card ( black screen - no pictures),
i tried to convert the above file into zip(from .7z to .zip) but it becomes unusable
@gaurav@Whim Why don't you simply state that the build is available from the CHDKDE website?Quotei tried to convert the above file into zip(from .7z to .zip) but it becomes unusable
to unpack a 7-zip archive you need the open source 7-zip (http://www.7-zip.org/download.html) program
(it will also work with most other archive types) The .7z archive format is a bit more efficient.
However, in the spirit of Xmas, see zip attached (build 1005)
wim
Thank you so much for all the work. I am a big fan of CHDK from using it on my previous unit Canon A590IS.SD1200 is not ixus950, it's ixus95. It's not currently in the main autobuild, but you should be able to find some builds in this thread.
Now I have a SD1200IS with original firmware version 1.00c. I have downloaded the latest CHDK build for model ixus950 from the build server, copied on a freshly formated and made bootable SDHC card using CardTricks but can't seem to run CHDK for some reason - whether with locked or unlocked SDHC card. Play->Menu->Update firmware is option not visible at all.
SD1200 is not ixus950, it's ixus95. It's not currently in the main autobuild, but you should be able to find some builds in this thread.
I loaded the sd1200is beta onto my camera and noticed a few quirks. Is this the appropriate place to report/discuss potential bugs?Yes.
it possible to shoot longer than 64 sec? For example ixus 80 can take a 2048 sec exposure.No, the code required to support this feature has not been added to ixus95
it possible to shoot longer than 64 sec? For example ixus 80 can take a 2048 sec exposure.No, the code required to support this feature has not been added to ixus95
A cod has not added to chdk or has not added to ixus 95 firmware?Not added to CHDK.
How to add? Maybe i try to do this?A cod has not added to chdk or has not added to ixus 95 firmware?Not added to CHDK.
How to add? Maybe i try to do this?Look at any of the cameras that do support extra long exposure (CAM_EXT_TV_RANGE set in camera.h) and implement the equivalent. The exp_drv_task code must come from your cameras firmware dump, not one of the existing ports.
Try the custom timer option. Specify the delay until the first exposure and the number of exposures. I find that this works using SDM, but not CHDK (for HDR using bracketing)
Hello All,
One-press bracketing for the Ixus 95 SD1200 does not work (it does in SDM) and I cannot get zoom during video to function. It is enabled and there is a stub for it. The stub is the same in CHDKDE and SDM, does anyone have it working?
I also find that Remote does not work well in CHDK, but does in SDM 1.85, on the Ixus 95
I heard that this camera has 12 bit raw. Does it positively affect DNG quality much(given higher pixel density), compared to older cameras' 10bit raw?I do not know about that, but here is a shot from my Ixus 95, originally in RAW http://www.flickr.com/photos/31637627@N08/4603083887/#in/photostream (http://www.flickr.com/photos/31637627@N08/5513471214/#in/photostream)
I think you've give a wrong link...flickr says: This photo was taken on May 13, 2010 using a Canon PowerShot G9.I heard that this camera has 12 bit raw. Does it positively affect DNG quality much(given higher pixel density), compared to older cameras' 10bit raw?I do not know about that, but here is a shot from my Ixus 95, originally in RAW http://www.flickr.com/photos/31637627@N08/4603083887/#in/photostream (http://www.flickr.com/photos/31637627@N08/4603083887/#in/photostream)
Best,
Colin
Whoops,No offence, Colin, but your HDR is not something that illustrate 12 bit advantage.
I cannot do the original RAW, but this one is a three shot HDR done in RAW, from my Ixus 95 http://www.flickr.com/photos/31637627@N08/5513471214/#in/photostream (http://www.flickr.com/photos/31637627@N08/5513471214/#in/photostream)
Best,
Colin
I heard that this camera has 12 bit raw. Does it positively affect DNG quality much(given higher pixel density), compared to older cameras' 10bit raw?See http://chdk.setepontos.com/index.php?topic=2468.msg30570#msg30570 (http://chdk.setepontos.com/index.php?topic=2468.msg30570#msg30570)
So it means 12 bit ADC makes no sense in terms of SD1200 raw quality. Thanks.I heard that this camera has 12 bit raw. Does it positively affect DNG quality much(given higher pixel density), compared to older cameras' 10bit raw?See http://chdk.setepontos.com/index.php?topic=2468.msg30570#msg30570 (http://chdk.setepontos.com/index.php?topic=2468.msg30570#msg30570)
unfortunately I'm stuck with the 1.00B firmware, therefor I'd like to compile the 1.00C CDHK version for 1.00B models. Can someone please comment in a few lines what would be necessary to get this running?Dump your camera's firmware,
So, I prepared the developement environment (took some time cause I'm not using windows but linux) and run cdhk-pt like its advertised on the wiki. I made it to the point where it says you should convert the adresses using a adress file for the reference port. Where do I get this? I have the firmware dump for 100c so I suppose I can extract the adresses from that but how?Probably better to ask about that over in the CHDK-PT thread ? For example, did you look at this :
OK, I will have a look there...Be aware that I recently discovered a bug where CHDK-PT dissassembles an LDRD instrucion as STRD. Should be easy to fix when I get a quiet minute but its always worth looking at the code produced against your reference port.
Yeah, I'm running chdk-pt under Ubuntu 11.04 with Wine, runs without problems!
Do forum users agree that adding more cameras to the list shown in the post above, will provide the fix for bracketing/custom timer shooting, where needed?The SD1200 is not currently included in the list of cameras that get this fix but probably should be.
Yes, I tested it and it worksDo forum users agree that adding more cameras to the list shown in the post above, will provide the fix for bracketing/custom timer shooting, where needed?The SD13001200 is not currently included in the list of cameras that get this fix but probably should be.
@reyalp : I can't submit patches this week - can you just add it directly ?
Done, changeset 1224 (http://tools.assembla.com/chdk/changeset/1224)Yes, I tested it and it worksDo forum users agree that adding more cameras to the list shown in the post above, will provide the fix for bracketing/custom timer shooting, where needed?The SD13001200 is not currently included in the list of cameras that get this fix but probably should be.
@reyalp : I can't submit patches this week - can you just add it directly ?
Colin
Then when I hit OK to update from 1.0.0.0 to 1.1.0.0, I get a red CHDK logo for half a second, then it goes back to "no image".The appearance of the logo means that you have successfully loaded CHDK.
I do not get anywhere from a locked card.Did you follow the steps to make the card bootable first ?
Do I have to make some changes to the CHDK files for this camera?No.
And this camera doesn't have a "Direct Print" button, so I've seen mention of using quick press / long press of certain buttons... but I'm not sure..I checked the code. It says that the "Play" button is the <ALT> button.
OMG, THANK YOU!I do not get anywhere from a locked card.Did you follow the steps to make the card bootable first ?
can anybody tell me how to start the chdk from my ixus95 with the firmware update? There is no update firmware option in the menu. How do i make it appear?http://chdk.wikia.com/wiki/Prepare_your_SD_card (http://chdk.wikia.com/wiki/Prepare_your_SD_card)
unfortunately I'm stuck with the 1.00B firmware, therefor I'd like to compile the 1.00C CDHK version for 1.00B models. Can someone please comment in a few lines what would be necessary to get this running?
That P&S folder is also gone. Can anyone put up a copy of 1.00c somewhere?The box.com account got overloaded with too many downloads this month. Should be back next month.
Edit: - anyone have the A570 1.01a firmware dump? The box repository is offline.Not really, i've moved the "big" folders outside the public available share folder.
Some time ago, Box.net added the "Download folder" button for public shares also for free accounts; ATM there's no way to disable this...
Now users often use this button and download the whole CHDK folder or complete sub-folders like the "P&S fw dumps" folder.
Therefore the traffic limit of 10GB per month was reached after a few days...
71c71
< int *canon_data_src = (int *)0xFFECD3E4; //From end of first function
---
> int *canon_data_src = (int *)0xFFECD364; //From end of first function
133c133
< " LDR R0, =0xFFECD3E4\n"
---
> " LDR R0, =0xFFECD364\n"
164a165
>
213c214
< " BL sub_FFE6083C\n"
---
> " BL sub_FFE607BC\n"
Can you tell me what method you used to boot CHDK? As there isn't a ps.fi2 or ps.fir file, it looks like EOScard is my only option but as I don't use Windows, I'll have to hunt around for a Windows machine to hijack...All kinds of good information about that here : http://chdk.wikia.com/wiki/Prepare_your_SD_card (http://chdk.wikia.com/wiki/Prepare_your_SD_card)
All kinds of good information about that here : http://chdk.wikia.com/wiki/Prepare_your_SD_card (http://chdk.wikia.com/wiki/Prepare_your_SD_card)Many thanks for that pointer - I'd looked at it but hadn't scrolled down far enough! I'm not sure whether I could actually use STICK as this isn't an official build so wouldn't be downloadable but I've got it successfully booting and running the intervalometer script by using hexedit.
If you want something simple, just use the new STICK utility - there is an info box and link at the top of that page. Works on Windows, Linux or Apple.
Added thefull 4MB dump (dumped with cBasic udumper) by luddek from this forum post (http://chdk.setepontos.com/index.php?topic=4324.msg95589#msg95589) to the CHDK P&S FW dumps (http://tinyurl.com/chdkfiles) repository.
- IXUS 95 / SD1200 1.00B
#define CAM_EXT_TV_RANGE 1 The long exposure can probably quite easily be added to 1.00c as well.How would one go getting the 100b firmware changes checked in?Typically you create a patch file and submit it here :
There was a bug in void *vid_get_bitmap_active_palette(). Please test this patch.This patch does it. Menu colors after reset are what they should be. Custom palette is present both in play and Rec mode. CHDKPTP Palette matches Palette on camera. Well done. Thanks.
The FAT32 part in boot.c was commented out. Then it makes no sense to define 'multipart' in platform_camera.h. Can anyone confirm that the multipartition function works (FW 1.00c)?Someone updated the wiki today for the SD1200 to point out that large microSD cards will work formatted FAT32 with firmware update booting. But the wiki still says that multipartition support is not available for this camera.
I tried to get two partitions working, I think I succeeded, but frankly it is all a bit confusing. What I did find was that the CHDK menu item ... /SDcard/make 2 partitions results in one (the boot) partition being too small to hold a a full CHDK distribution and I got an error msg Modules cannot load.The FAT32 part in boot.c was commented out. Then it makes no sense to define 'multipart' in platform_camera.h. Can anyone confirm that the multipartition function works (FW 1.00c)?Someone updated the wiki today for the SD1200 to point out that large microSD cards will work formatted FAT32 with firmware update booting. But the wiki still says that multipartition support is not available for this camera.
The code to provide multipartition support is in the source, so either the wiki is wrong (and it is available) or it does not work.
If somebody with the camera volunteers to test, we can fix this.
What I did find was that the CHDK menu item ... /SDcard/make 2 partitions results in one (the boot) partition being too small to hold a a full CHDK distribution and I got an error msg Modules cannot load.When correctly formatted, the small (or boot partition) needs to be jusy big enough for the DISKBOOT.BIN file. You only need that one file installed there. STICK and CHIMP will set thinga up that way for you. Your manual approach might need alll the files until you get things setup correctly though.