[beagleboard] boot configurations

So I have recovered my board back to the demo image, but I am lost trying to change the boot parameters. It appears from what I have read I either need to interrupt the boot sequence, or create a boot.scr file.

Now I have two more mysteries to fight. Typing to the serial port during boot sequence is equally ineffectual as typing on the usb keyboard. Can someone enlighten me as if one of those is suppose to work? Or what I could do to get one to work?

As for mkimage, that is not on the image, can I download it with opkg? Which package is it in? Opkg search seems to never find anything.

Is there a sample boot script input I can start from, for the moment I just want to fix the screen resolution. If I change the resolution, do I need to change the vram size to handle the increased size?

Thanks much for any pointer. My board is an xM I got a couple of weeks ago, and I am still stumbling around trying to figure out what is moved where an how to build the tools and images I need?
Rich


Hi Richard


Never heard back from you I gave up on trying to follow these Angstrom Instructions


Not sure what your end goal is ?

I loaded an image very quickly following these instructions below but I had to ask they fix the links to downlaod the zip files


http://www.keil.com/support/man/docs/ds5gs/ds5gs_2bb_setup.htm

anyway look at the link above there is a trouble shooting page that explain boot params

I have a C4 and looking at these instructions i could see that I had no Image in NAND and must laod from SD

Typing printenv from Uboot showed boot commands for me

You say "but I am lost trying to change the boot parameters"

what are you trying to do?

The recovery page has a boot.scr

I found these guys have little info to help beginners and you are luckt to get 1 specific question answered


— On Sat, 10/2/10, Rich Hyde rich.hyde@gmail.com wrote:


> From: Rich Hyde rich.hyde@gmail.com
> Subject: [beagleboard] boot configurations
> To: beagleboard@googlegroups.com
> Date: Saturday, October 2, 2010, 12:27 AM
>
> So I have recovered my board back to the demo image, but I am lost trying to change the boot parameters. It appears from what I have read I either need to interrupt the boot sequence, or create a boot.scr file.
> Now I have two more mysteries to fight. Typing to the serial port during boot sequence is equally ineffectual as typing on the usb keyboard. Can someone enlighten me as if one of those is suppose to work? Or what I could do to get one to work?
> As for mkimage, that is not on the image, can I download it with opkg? Which package is it in? Opkg search seems to never find anything.
> Is there a sample boot script input I can start from, for the moment I just want to fix the screen resolution. If I change the resolution, do I need to change the vram size to handle the increased size?
> Thanks much for any pointer. My board is an xM I got a couple of weeks ago, and I am still stumbling around trying to figure out what is moved where an how to build the tools and images I need?
> Rich
> On Oct 1, 2010 8:31 PM, “rafaelaroca” <rafaelaroca@ieee.org> wrote:
> > Hi,
> >
> > I just got a Beagle Board XM that Bill from Special Computing kindly
> > sent to me…
> >
> > As I don’t have a DVI monitor, I want to setup the S-Video output.
> >
> > So, using the default files that came with the SD Card, I created
> > user.cmd with the contents:
> >
> > root@beagleboard:~# cat /media/mmcblk0p1/user.cmd
> > led 1 off
> > mmc init
> > setenv bootargs ‘console=tty0 console=ttyS2,115200n8 rootwait ro
> > vram=12M omapfb.mode=tv:ntsc omapdss.def_disp=tv fixrtc buddy=unknown’
> > if test “${beaglerev}” = “AxBx”; then
> > setenv rdaddr 0x81000000
> > setenv optargs mem=80M@0x80000000 musb_hdrc.fifomode=5
> > elif test “${beaglerev}” = “Cx”; then
> > setenv rdaddr 0x88000000
> > setenv ramroot /dev/ram0 rw ramdisk_size=131072 initrd=${rdaddr},128M
> > setenv optargs mem=80M@0x80000000 mem=128M@0x88000000
> > musb_hdrc.fifomode=5
> > else
> > setenv rdaddr 0x88000000
> > setenv ramroot /dev/ram0 rw ramdisk_size=131072 initrd=${rdaddr},128M
> > setenv optargs mem=80M@0x80000000 mem=384M@0x88000000
> > fi
> > run loadramdisk
> > led 0 off
> > run loaduimage
> > led 1 on
> > run ramboot
> >
> > then I executed:
> >
> > mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n “Test” -d ./
> > user.cmd ./user.scr
> >
> > After rebooting the board, I checked the kernel command line:
> > root@beagleboard:~# dmesg |grep command
> > [ 0.000000] Kernel command line: console=ttyS2,115200n8
> > mem=80M@0x80000000 mem=384M@0x88000000 mpurate=1000 buddy=none
> > camera=lbcm3m1 vram=12M omapfb.mode=dvi:640x480MR-16@60
> > omapdss.def_disp=dvi root=/dev/ram0 rw ramdisk_size=131072
> > initrd=0x88000000,128M rootfstype=ext2
> >
> > root@beagleboard:~# dmesg |grep command
> > [ 0.000000] Kernel command line: console=ttyS2,115200n8
> > mem=80M@0x80000000 mem=384M@0x88000000 mpurate=1000 buddy=none
> > camera=lbcm3m1 vram=12M omapfb.mode=dvi:640x480MR-16@60
> > omapdss.def_disp=dvi root=/dev/ram0 rw ramdisk_size=131072
> > initrd=0x88000000,128M rootfstype=ext2
> >
> > And it shows DVI!!! Did it execute my commands?
> >
> > Could anyone help or suggest whats wrong here?
> >
> > thanks a lot
> >
> > Rafael
> >
> > –
> > You received this message because you are subscribed to the Google Groups “Beagle Board” group.
> > To post to this group, send email to beagleboard@googlegroups.com.
> > To unsubscribe from this group, send email to beagleboard+unsubscribe@googlegroups.com.
> > For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
> >
>
> –
> You received this message because you are subscribed to the Google Groups “Beagle Board” group.
> To post to this group, send email to beagleboard@googlegroups.com.
> To unsubscribe from this group, send email to beagleboard+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.

|

and the proper download link is?