(yet again) updated BB validation page

ok, i think i've incorporated most peoples' suggestions here, at
least for now:

http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidationv2

thoughts? i didn't mean for this to become such an epic saga.

rday

Nicely done, Robert.

This should make it a lot easier for people new to the platform to understand the basics of what's happening.

Cheers,
Kai

The instructions for creating a vfat partition neglect to mention the important part: marking it as bootable. There a nice shell script that handles everything for you:

http://www.xora.org.uk/2009/09/07/omap3-card-formatter-license/

regards,

Koen

It also neglects to put MLO on the SD card, revB boards shipped with a broken MLO (and uboot), so having a known good MLO and u-boot on SD is fairly crucial. Unless you like reboot failures, nand ecc errors, I2C funkiness and weird shutdown behaviour.
And linking to the broken uboot sources isn't going to help people either. The 2009.01 uboot with musb patches is broken and should not be used.

And notice the GPL violation by not having the *exact* sources and buildscripts for the ramdisk available.

regards,

Koen

i don't mention it because i'm not convinced it's true. the card
i'm using:

# fdisk -l /dev/sdb

Disk /dev/sdb: 3957 MB, 3957325824 bytes
255 heads, 63 sectors/track, 481 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xdedd7ca1

   Device Boot Start End Blocks Id System
/dev/sdb1 1 481 3863601 c W95 FAT32 (LBA)

>
> ok, i think i've incorporated most peoples' suggestions here, at
> least for now:
>
> http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidationv2
>
> thoughts?

It also neglects to put MLO on the SD card, revB boards shipped with
a broken MLO (and uboot), so having a known good MLO and u-boot on
SD is fairly crucial. Unless you like reboot failures, nand ecc
errors, I2C funkiness and weird shutdown behaviour.

  ah, i was unaware of that. (although, in my defense, i do write
that the validation is for C2 and C3 boards but, yes, i should cover
off the other possibilities.)

And linking to the broken uboot sources isn't going to help people
either. The 2009.01 uboot with musb patches is broken and should not
be used.

  i'm not keen on leaving that "Sources" section in, anyway, since it
adds nothing to the validation procedure. i'll toss it.

And notice the GPL violation by not having the *exact* sources and
buildscripts for the ramdisk available.

  i've been considering simply switching completely to the angstrom BB
demo image since i'm fairly familiar with that. and, really, once
you're up and running in linux, the validation is pretty much over so
the choice of linux distro is fairly irrelevant. i think i'll do
that.

rday

ok, i think i've incorporated most peoples' suggestions here, at
least for now:

http://code.google.com/p/beagleboard/wiki/BeagleboardRevCValidationv2

thoughts?

The instructions for creating a vfat partition neglect to mention the important part: marking it as bootable. There a nice shell script that handles everything for you:

http://www.xora.org.uk/2009/09/07/omap3-card-formatter-license/

i don't mention it because i'm not convinced it's true. the card

I know I needed that step...

i'm using:

# fdisk -l /dev/sdb

Disk /dev/sdb: 3957 MB, 3957325824 bytes
255 heads, 63 sectors/track, 481 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xdedd7ca1

  Device Boot Start End Blocks Id System
/dev/sdb1 1 481 3863601 c W95 FAT32 (LBA)
#

i've *never* set that partition bootable and i've never had a
problem booting. can someone else clarify this?

.. but maybe it's only needed when there are >1 partitions. Or maybe the ROM code got fixed in ES3.X :slight_smile:

regards,

Koen

i'll just add that you *might* need to set it bootable, for totally
arbitrary reasons.

rday

is there a corresponding angstrom ramdisk.gz image i could use in
place of the arago one?

rday

Not at the moment. If you're validating on an SD card you might as well use the sd card instead of a ramdisk. Personally, I'm too stupid for ramdisks and NFS, so I always validate using SD when available or NAND/NOR.

And I spent way too many times explaining to users that ramdisks don't save their changes :slight_smile:

regards,

Koen

Hi,

I am using the OMAP DSS V4L2 driver in user pointer mode to access my cameras memory mapped buffers. The camera side works well. The omap dss doesn't set the buffer flags to 0 after displaying a frame. Thus after two frames I am unable to dequeue any dss buffer.

Anyone got any clue?

Sebastian

Mon, 30 Nov 2009, Robert P. J. Day wrote:

i've *never* set that partition bootable and i've never had a
problem booting. can someone else clarify this?

i'll just add that you *might* need to set it bootable, for totally
arbitrary reasons.

I cannot say if the partition *really* needs to be set bootable but a quick look at OMAP35x TRM (section "1.4.7.6.3 File System Handling" at page 3497 in spruf98c.pdf) reveals that:

"The image used by the Booting procedure is taken from a specific booting file named MLO. This file has to be located in the root directory on an active primary partition of type FAT12/16 or FAT32."

"An MMC/SD card can be configured as floppy-like or hard-drive-like:
� When acting like a floppy, the content of the card is a single FAT12/16/32 file system without an MBRholding a partition table.
� When acting like a hard drive, an MBR is present in the first sector of the card. This MBR holds a table of partitions, one of which must be FAT12/16/32, primary, and active"

This indeed says that the partition must be set bootable.

as i read the above, then, the partition needs to be bootable only
if you're booting from the MMC/SD card (that is, via the USER button),
so that you're picking up the x-loader from the MMC/SD card. does
that sound right?

  if you're using the flash-resident x-loader, then it doesn't matter.
at least, that's the way i read it.

rday

Mon, 30 Nov 2009, Robert P. J. Day kirjoitti:

I cannot say if the partition *really* needs to be set bootable but
a quick look at OMAP35x TRM (section "1.4.7.6.3 File System
Handling" at page 3497 in spruf98c.pdf) reveals that:

"The image used by the Booting procedure is taken from a specific
booting file named MLO. This file has to be located in the root
directory on an active primary partition of type FAT12/16 or FAT32."

"An MMC/SD card can be configured as floppy-like or hard-drive-like:
� When acting like a floppy, the content of the card is a single
FAT12/16/32 file system without an MBRholding a partition table. �
When acting like a hard drive, an MBR is present in the first sector
of the card. This MBR holds a table of partitions, one of which must
be FAT12/16/32, primary, and active"

This indeed says that the partition must be set bootable.

as i read the above, then, the partition needs to be bootable only
if you're booting from the MMC/SD card (that is, via the USER button),
so that you're picking up the x-loader from the MMC/SD card. does
that sound right?

if you're using the flash-resident x-loader, then it doesn't matter.
at least, that's the way i read it.

This is exactly as I understand it also.

One suggestion I'd like to add regarding a Linux terminal program,
minicom can be a bit daunting for a newbie and in at least one case on
this list where it looked as though it should have worked, it didn't.
I suggested using "gtkterm" which has been around for many years, but
not well known, very easy to use with no or minimal configuration - you
just fire it up and from the menu select "Configuration --> Port" if you
have multiple /dev/ttyS or /dev/ttyUSB interfaces - one will work and
you're connected. The configuration can be saved as default, so it will
work immediately gtkterm is launched.
Regards
Sid.

I forgot to add, that some distros use /media, so the MMC partitions get
mounted as /media/LABEL1, /media/LABEL2 (if they are lablelled as
recommended).
Regards
Sid.

This seems to imply that MLO _doesn't_ need to be the first file,
simply that it needs to be called 'MLO' an in the root directory, or
am I reading it wrong?

Benno