saveenv at xM

Hi guys!

I just began to work with xM having huge background experience with C3. I begin to use the same commands like I did at C3 and have problems. The u-boot.bin from “Beagleboard demo files” wants to save the environment into NAND, which I expect to be absent at xM A3. So, u-boot just hangs with the following log:

OMAP3 beagleboard.org # saveenv
Saving Environment to NAND…
Erasing Nand…

Also a question: is it correct to use the same arguments for bootargs to enable DSP? like: mem=99M@0x80000000 mem=128M@0x88000000

So, is it possible to save the environment somehow at xM? I also think it is necessary to create some user guide for xM like it was for Cx. You can consider me as a volunteer in writing docs but I need to know all instructions myself before writing anything…

regards,
Max

On the xM you need to do all that in the boot.scr script file..

Regards,

Hi Maxim,

BB-xM doesn't have NAND flash, it can boot from SD card only. Thus,
basically you have two options:

1. Change default boot command in U-Boot sources which is a little bit
annoying (file "include/configs/omap3_beagle.h" string "#define
CONFIG_EXTRA_ENV_SETTINGS");

2. Setup a boot script for U-Boot (usually it's a file boot.scr). This
file has special format (I guess some kind of CRC checking) so in
order to produce this file you should do the next steps:

a) Make a file with your new U-Boot commands:

    cat << EOF > my_boot_cmd
    mmc init
    reset
    EOF

(Just kidding, don't use "reset", use you commands instead :slight_smile: ).

b) Use next command (make sure you have "uboot-mkimage" installed, on
ubuntu "apt-get install uboot-mkimage"):

    mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n
"Beagleboard-xM boot script" -d my_boot_cmd boot.scr

c) Copy boot.scr to the FAT partition on your SD card (where you have
MLO, u-boot.bin, uImage etc.).

What about "mem=99M@0x80000000 mem=128M@0x88000000" - these parameters
are just a part of your kernel boot command-line parameters. So
probably using of "mem=" argument depends on your kernel
configuration.

Cheers,
Max.