multipart on new cams (Re: mighty-hoernsche.de autobuild retirement)

I noticed that some newer platforms (e.g. m3 and g7x2) now have CAM_MULTIPART defined to 1. Does that still mean SD cards requiring multiple partitions?

I noticed that some newer platforms (e.g. m3 and g7x2) now have CAM_MULTIPART defined to 1. Does that still mean SD cards requiring multiple partitions?

IIRR, it´s not required, it´s an option for cards > 32GB.

  https://chdk.fandom.com/wiki/Prepare_your_SD_card#Bootable_SD_Card_Method Method 4

Edit2: Cams supporting multipart.
 Search "CAM_MULTIPART" (83 hits in 80 files of 7242 searched)
  D:\hostluaPortable\CHDK-Shell\trunk\trunk-6214\platform\a1000\platform_camera.h (1 hit)
Line 58:   
a1100
a2000
a2100
a3000
a3100
a410
a470
a480
a490
a495
a550
a560
a570
a580
a590
a610
a630
a640
a650
a710
a720
d10
g10
g11
g12
g1x
g5x
g7
g7x2
g9
Line 431
generic\main.c (2 hits)
Line 53: #if !CAM_MULTIPART
Line 129: #if CAM_MULTIPART
generic\wrappers.c (1 hit)
Line 1281: #if CAM_MULTIPART
ixus1000_sd4500
ixus100_sd780
ixus105_sd1300
ixus110_sd960
ixus120_sd940
ixus130_sd1400
ixus200_sd980
ixus300_sd4000
ixus700_sd500
ixus70_sd1000
ixus750_sd550
ixus75_sd750
ixus80_sd1100
ixus850_sd800
ixus85_sd770
ixus860_sd870
ixus870_sd880
ixus900_sd900\notes.txt (3 hits)
Line 45:     * CAM_MULTIPART enabled (mount.c)
Line 54:     * multi partition Support still disabled ("CAM_MULTIPART 1" does crash camera)
Line 143: * CAM_MULTIPART (mount.c) does crash camera
ixus900_sd900
ixus900_sd900\sub\100c\mount.c (1 hit)
Line 1: // Multiple Partition support, used if CAM_MULTIPART enabled
ixus90_sd790
ixus950_sd850
ixus95_sd1200
ixus960_sd950
ixus970_sd890
ixus980_sd990
ixus990_sd970
m3
s100
s110
s3is
s5is
s80\main.c (1 hit)
Line 132:         #if CAM_MULTIPART
s90
s95
sx1
sx10
sx100is
sx110is
sx120is
sx130is
sx20
sx200is
sx210is
sx30
tx1
Edit3:  https://chdk.setepontos.com/index.php?topic=14566.0

IIRR, it´s not required, it´s an option for cards > 32GB.

  https://chdk.fandom.com/wiki/Prepare_your_SD_card#Bootable_SD_Card_Method Method 4

Edit2: Cams supporting multipart.
 

Code: [Select]

Search "CAM_MULTIPART" (83 hits in 80 files of 7242 searched)

Well, the problem is CHIMP's camera metadata generator tool uses it as an indication that the card must be reformatted with FAT16.

May I suggest that CAM_MULTIPART be defined as follows:

• required
• supported?

P.S. Please split this topic starting with my previous post.

May I suggest that CAM_MULTIPART be defined as follows:

• required
• supported?

Well, that define isn't intended to indicate what kind of partition the Canon firmware will load DISKBOOT.BIN from, and I'd be reluctant to add a value for that since it has no meaning inside CHDK.

Cameras released in 2011 and later support booting from FAT32, and thus do not need FAT16. This also corresponds to the change from DryOS R45 to R47. Per our list https://chdk.fandom.com/wiki/P-ID_(Table) the last 2010 / R45 powershot is S95, P-ID 0x3212. The first 2011 / R47 is A3300, P-ID 0x3223

Cameras released in 2011 and later support booting from FAT32, and thus do not need FAT16. This also corresponds to the change from DryOS R45 to R47. Per our list https://chdk.fandom.com/wiki/P-ID_(Table) the last 2010 / R45 powershot is S95, P-ID 0x3212. The first 2011 / R47 is A3300, P-ID 0x3223

Presumably P-ID will have to come from camera_info.csv, which would require significant changes to the metadata generator.

Edit: I believe I found a reasonable solution. The generator already determines whether a camera supports FAT32 (or later) based on model ID. Please confirm that ixus990_sd970 doesn't.

Edit: I believe I found a reasonable solution. The generator already determines whether a camera supports FAT32 (or later) based on model ID. Please confirm that ixus990_sd970 doesn't.

ixus990_sd970 definitely doesn't support FAT32 boot, since it's a DryOS 31 cam from 2009. It does support multipartition.

Cameras released in 2011 and later support booting from FAT32, and thus do not need FAT16.

Ah, well i may be partly to blame 

since a few models that have 'no need for FAT16' do have it since i requested to give those cams dual boot capabilities.
as far as i know these include the S100, S110 and M3. however, since dmitrys stated the g7x (II) has also dual boot.
there might be more models now that support dual boot, and in these cases it is: FAT16/exFAT formatted.
Phil, do we have a current list of all >2011 models that support dual boot?
For these i use the in-cam dual partition tool and use chimp for creating the bootflag.

since a few models that have 'no need for FAT16' do have it since i requested to give those cams dual boot capabilities.
as far as i know these include the S100, S110 and M3. however, since dmitrys stated the g7x (II) has also dual boot.
there might be more models now that support dual boot, and in these cases it is: FAT16/exFAT formatted.
Phil, do we have a current list of all >2011 models that support dual boot?
For these i use the in-cam dual partition tool and use chimp for creating the bootflag.

Here's the full list (as of 6222):

m3
g1x
g5x
g7x2
s100
s110

In the meantime, I updated Data/Product/CHIMP/cameras.json on GitHub to include the new models (without requiring partitioning).

I added experimental exFAT support. It should allow updating CHDK on a partitioned exFAT card. Is somebody willing to test it?

So looking at the (edit: CHDK) source, I noticed only the 121a sub of M3 actually has the multipart boot code.

In general, we should try not to have platform define features that aren't defined for all subs. I'll try to add the others at some point. Doing changes blind *also* isn't great, but in this case the code is likely identical except offsets.