Hey kids, wow what a difference a few months make... cheap little thing has already been RMA'd once for the dreaded lens error, but apparently CHDK is working on the SX100... aaaanyway....
So, the dual partition thing. Is it confirmed working on this unit? From reading the various other units that utilize this trick, I've made the first partition primary 1, active, 32M, FAT16, with the partition type descriptor set to Empty (0x0)... I've also tried leaving it as FAT16 (0x6) but as DG says, it's unimportant,
"it even boots from FAT16 with 0x83". Right. So, then I the partition remainder of the card as primary 2, W95 FAT32 (0xb) and mkfs.msdos /dev/mmcblk2p1 & mkfs.vfat -F32 /dev/mmcblk2p2...
[root@cameramad ~]# fdisk -l /dev/mmcblk2
Disk /dev/mmcblk2: 8219 MB, 8219262976 bytes
69 heads, 29 sectors/track, 8022 cylinders
Units = cylinders of 2001 * 512 = 1024512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/mmcblk2p1 * 1 32 32001+ 0 Empty
/dev/mmcblk2p2 33 8022 7993995 b W95 FAT32
[root@cameramad ~]# So I lock it, boot up CHDK, and it still wants to write to the tiny 32M partition.
Looking in
~/chdk/svn/trunk/platform/sx100is/sub/100c/boot.c I verified that DG's code is indeed there, but I have no way of checking the address validity other than telling you guys "it don't work for me."
(slightly off topic: I thought the standard was to not include the "IS" on platform? Shouldn't this just be /sx100/)Could it be something simple? Does CHDK expect some specific offset or something?
