• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 430 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

fat boot partition limitation on OMAP3530

Charles Wu13376
Prodigy 115 points

Other Parts Discussed in Thread: OMAP3530

Hello,

 

I found OMAP3530 seems to be unable to boot from a FAT primary partition which max cyclinder no is less than 4 (63 * 255 * 4 *512=31MB)

The total size of my MLO and Uboot is about 2MB, so using 31MB space for only 2MB code seems to be wasteful.

Could you explain this issue for me?

Thanks for help.

 

  • 0
    TI__Guru**** 182356 points

    I dont think there is any limitation. I can boot the evm with a 8MB FAT partition. Please check my SD partitions below.

    Disk /dev/sdc: 2032 MB, 2032664576 bytes
    255 heads, 63 sectors/track, 247 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00000000

       Device Boot      Start         End      Blocks   Id  System
    /dev/sdc1   *           1           1        8001    6  FAT16
    /dev/sdc2               2           8       56227+  83  Linux

  • 0 in reply to Bin Liu
    Genius 3685 points

    The problem is, that the ROM code won't accept a FAT32 formattet boot partition of size less than 32MB. In this case you need to use either FAT12/16 as indicated by Bin Lui. (Same default value as Windoes formatting scheme. In case of a MMC drive less than 32MB it will as well use FAT12/16 and not FAT32). The problem only occurs if you in Linux create a FAT32 partition less than 32MB (which is totally valid), but not recommended by Microsoft...

    Best regards - I hope this clarified the problem :-)
      Søren

  • 0 in reply to Soren Steen Christensen
    Prodigy 115 points

    You got the point.

    Thanks  ; )