Why does ALARM ignore my boot.scr?

[gusrown]

I have two Odroids U3 I've been working with and one I have heavily tinker with. Today I wanted to force the resolution to 1080p using the following in my boot.scr:

$this->bbcode_second_pass_code('', '
setenv initrd_high "0xffffffff"
setenv fdt_high "0xffffffff"
setenv fb_x_res "1920"
setenv fb_y_res "1080"
setenv hdmi_phy_res "1080"
setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; bootm 0x40008000"
setenv bootargs "console=tty1 console=ttySAC1,115200n8 fb_x_res=${fb_x_res} fb_y_res=${fb_y_res} hdmi_phy_res=${hdmi_phy_res} root=/dev/mmcblk0p1 rootwait ro mem=2047M"
boot
')

I then created the scr file with

$this->bbcode_second_pass_code('', 'mkimage -A arm -C none -T script -d boot.txt boot.scr')

And it didn't work. At all. Even if I put a nonexistent partition like rooot=/dev/mmcblk0p3 it boots normally.

I assumed that I could've messed too much with the Odroid and decided to do a fresh install on my second install. I finished the install about 5 minutes ago and decided to try again with a fresh made boot.scr file and again, not working.

Has this functionality been removed and I'm an idiot? After making the boot.scr file I copy it over to /boot, is there something I have to do after that?

[gusrown]

I was looking at the documentation and found this:


Default Env
The default env provided in U-Boot will attempt the following:


$this->bbcode_second_pass_quote('', '
')1) Load boot.scr script from the first FAT type partition from the boot media.
2) Load boot.scr script from the second FAT type partition from the boot media.
3) Load kernel from its on media/ramdisk position (This is the Android Boot)

[pepedog]

Yes.
Also you have setenv bootcmd "fatload mmc ..............

[gusrown]

Thanks for the reply. Turns out boot.scr is not used on the Odroid U3 anymore, it's now done via uEnv.txt file in /boot