current setenv

GoogleGroups
1

Hi guys,

Sorry if this is a repeated thread but i've tried some threads to no
avail.

my current beagle is re c3, it was previously working through user
boot button, in an attempt to do an auto boot i did:

setenv bootargs 'console=ttyS2,115200n8 console=tty0 root=/dev/
mmcblk0p2 rw rootfstype=ext3 rootwait
omapfb.video_mode=1024x768MR-16@60'

setenv bootcmd 'mmcinit; fatload mmc 0 0x80300000 uImage; bootm
0x80300000'

saveenv

with that my nand got messy so i restored it following:
http://code.google.com/p/beagleboard/wiki/BeagleboardRevC3Validation

with the following files
   1. MLO as MLO
   2. u-boot as u-boot.bin
   3. u-boot for flash as u-boot-f.bin
   4. ramdisk image as ramdisk.gz
   5. Kernel (uImage) as uImage.bin
   6. reset.scr as boot.scr
   7. x-loader image as x-load.bin.ift
   8. Regular script file as normal.scr

its able to boot now but my monitor is not able to display with
warning "unable to display please set input computer to
1280x1024@60Hz"

im thinking its the setenv prob..?

Kindly advice, thanks, calvin

2

Use the MLO, u-boot.bin and uImage from http://www.angstrom-distribution.org/demo/beagleboard/

And use this as boot.scr:
http://dominion.thruhere.net/koen/OE/uboot-flash.cmd.scr

That will reset the uboot env to a sane default and flash a proper MLO + uboot combination to NAND

3

Hi Koen what is your sequence to copy these files?

Thanks n regards

4

Hi Koen what is your sequence to copy these files?

The only one that really matters is to copy the MLO file first. In
some cases, long file names can confuse u-boot, so try to avoid
copying files with long file names early in the process.

5

Jason,

When is the Beagle XM going to be available for purchase?

Digitkey have leadtime = 17 Nov 2010 and google does not give any other information.

Regards
Brian

6

Which in my case boils down to “don’t use OSX since that adds files like .spotlight-v100”

7

Hi, the problem still remains, after reseting the nand. serial shows
angstrom is booted
but my monitor refuses to show anything with the error

"Attention
cannot display this video mode, change computer display input to
1280x1024@60Hz"

A line in the Kernel boot process shows

[ 0.000000] Kernel command line: console=ttyS2,115200n8 mpurate=600
buddy=unk
nown vram=12M omapfb.mode=dvi:640x480MR-16@60 omapdss.def_disp=dvi
root=/dev/mmc
blk0p2 rw rootfstype=ext3 rootwait

You guys know anyway to change the display resolution?

8

Jason,

When is the Beagle XM going to be available for purchase?

Digitkey have leadtime = 17 Nov 2010 and google does not give any other
information.

Not a good idea to thread hijack for such a question. I'm currently
thinking we'll start shipping to Digi-Key when the new memories arrive
at the end of this month.

9

What is boot.scr?

I am using the latest MLO, u-boot.bin and uImage from
http://www.angstrom-distribution.org/demo/beagleboard/ and am
getting:

Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24)
Loading u-boot.bin from nand

U-Boot 2009.11-rc1-00601-g3aa4b51 (Jan 05 2010 - 20:56:38)

OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial
Board revision C4
Die ID #3554000400000000040373050f01a006
Hit any key to stop autoboot: 0
OMAP3 beagleboard.org # boot
mmc1 is available
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

3194800 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
   Image Name: Angstrom/2.6.32/beagleboard
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 3194736 Bytes = 3 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

But then everything runs fine.

I havent flashed to nand yet, so I am thinking this could solve the **
Unable to read "boot.scr" from mmc 0:1 ** issue, but I was just
curious.

Is boot.src something that isnt needed with newer versions, and that
is why Angstrom will still boot properly?