Can't create vexpress android images on cards >4GB
Bug #907447 reported by
Tixy (Jon Medhurst)
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Image Tools |
Fix Released
|
Undecided
|
Tixy (Jon Medhurst) |
Bug Description
On larger cards, creating Android images for vexpress fails because the sdcard partition will be >2GB and an attempt is made to format this as FAT16. This is because VexpressConfig() specifies fat_size = 16, so the boot partition is understandable by ARMs boot monitor.
I propose to fix this by making setup_android_
Related branches
lp:~tixy/linaro-image-tools/sdcard-partition-as-fat32
- Loïc Minier (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedlinaro_image_tools/media_create/partitions.py (+1/-1)
Changed in linaro-landing-team-arm: | |
assignee: | nobody → Tixy (Jon Medhurst) (tixy) |
importance: | Undecided → Medium |
status: | New → In Progress |
Changed in linaro-landing-team-arm: | |
milestone: | none → 2012.01 |
status: | In Progress → Fix Released |
Changed in linaro-image-tools: | |
assignee: | nobody → Tixy (Jon Medhurst) (tixy) |
milestone: | none → 12.01 |
status: | New → Fix Released |
To post a comment you must log in.
On Wed, Dec 21, 2011, Tixy (Jon Medhurst) wrote: partitions( ) always use
> On larger cards, creating Android images for vexpress fails because the
> sdcard partition will be >2GB and an attempt is made to format this as
> FAT16. This is because VexpressConfig() specifies fat_size = 16, so the
> boot partition is understandable by ARMs boot monitor.
>
> I propose to fix this by making setup_android_
> FAT32 for the sdcard partition. (The option for boards to specify
> fat_size only seems to exist for those with restrictions in boot
> partition format. I don't think it makes sense to also use this for the
> sdcard partition.)
FAT16 on Vexpress was suggested for compatibility with the boot
monitor; if it supports FAT32, then that would be ideal.
--
Loïc Minier