uEnv.txt vs boot.cmd

This forum is for discussion about general software issues.

uEnv.txt vs boot.cmd

Postby blippy » Wed Oct 11, 2017 12:31 pm

I am using a Cubietruck. I have Armbian Jessie on a bootable uSD card. I have Arch Linux ARM on my SATA drive.

I want to be able to tell the uSD card to boot from /dev/sda1 instead.

The whole boot process is a mystery to me. If I change boot.cmd, do I have to "activate" it somehow?

Why doesn't /boot contain uEnv.txt by default?
If I create /boot/uEnv.txt, will it be used automatically?
Will it be used in preference to boot.cmd?
Do I need to install any extra software in order to get uEnv.txt to work?
blippy
 
Posts: 5
Joined: Sat Oct 07, 2017 1:57 pm

Re: uEnv.txt vs boot.cmd

Postby blippy » Wed Oct 11, 2017 12:42 pm

OK, it looks like I have to do
mkimage -C none -A arm -T script -d boot.cmd boot.scr
to "activate" it.

Oo, fark me, it worked!
blippy
 
Posts: 5
Joined: Sat Oct 07, 2017 1:57 pm

Re: uEnv.txt vs boot.cmd

Postby blippy » Wed Oct 11, 2017 12:47 pm

Is there a way I can decompile boot.scr to boot.cmd?
blippy
 
Posts: 5
Joined: Sat Oct 07, 2017 1:57 pm


Return to General

Who is online

Users browsing this forum: No registered users and 1 guest