When creating a FAT32 partition with partition manager, actually an exFAT partition will be created (partition type 0x07 instead of 0x0b). This is a problem when creating bootable SD-cards for devices using AM335x ARM Cortex-A8 processor (e.g. BeagleBone boards). The processor is not able to load exFAT partitions. IMHO partitionmanager should distinguish between FAT32 and exFAT (currently, exFAT is not an available file system option in the list). At least the current entry "fat32" should be renamed to "exFAT" as this is actually what is created. STEPS TO REPRODUCE 1. create a FAT32 partition OBSERVED RESULT the partition type is set to 0x07 (exFAT) (can be checked with e.g. fdisk) EXPECTED RESULT the partition type should be 0x0b (FAT32)
Hmm, I checked MBR partition codes, I think it should be 0x0c (MBR with LBA addressing)
(In reply to Andrius Štikonas from comment #1) > Hmm, I checked MBR partition codes, I think it should be 0x0c (MBR with LBA > addressing) Here they also use "c": https://elinux.org/Building_for_BeagleBone#Test_your_new_U-Boot Btw, actual filesystem created is still FAT32, not exfat. It's partition type that was set to 0x07.
Git commit 59c9ba2f8d644357e759e6584b4cddad545d4feb by Andrius Štikonas. Committed on 15/10/2019 at 20:37. Pushed by stikonas into branch '4.0'. Set MBR partition type of FAT32 partitions to 0x0c. M +1 -1 src/plugins/sfdisk/sfdiskpartitiontable.cpp https://invent.kde.org/kde/kpmcore/commit/59c9ba2f8d644357e759e6584b4cddad545d4feb