public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] change default RedBoot "fis load" and "exec" - how?
Date: Mon, 10 Jul 2006 11:19:00 -0000	[thread overview]
Message-ID: <44B237C3.2090604@wpkg.org> (raw)

I have a Freecom FSG-3 device (ARM, IXP425 network, RedBoot).

By default, RedBoot starts Linux in the following way:

RedBoot> fis load kern1
RedBoot> exec -c "console=ttyS0,115200 root=/dev/hda1 mem=64M@0x00000000"

kern1 sits on /dev/mtd1, as seen here from Linux:


# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00040000 00020000 "RedBoot"
mtd1: 00180000 00020000 "kern1"
mtd2: 00180000 00020000 "kern2"
mtd3: 00020000 00020000 "RedBoot config"
mtd4: 00020000 00020000 "FIS directory"


I compiled my own kernel, saved it to /dev/mtd2 (kern2), and boot it as 
follows:

RedBoot> fis load -b 0x00020000 kern2
RedBoot> exec

To do this, I have to ctrl+C when device boots, and type the appropriate 
"fis load..." and "exec" commands.

Is there an easy way to make these new "fis load..." and "exec" commands 
the default ones for RedBoot?

I don't have a JTAG pinout for this device, so I wouldn't like to 
compile RedBoot from scratch, then flash it, and possibly brick the device.

I checked RedBoot documentation, but didn't find any commands to just 
update the default startup commands.



-- 
Tomasz Chmielewski
http://wpkg.org

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2006-07-10 11:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-10 11:19 Tomasz Chmielewski [this message]
2006-07-10 11:52 ` Gary Thomas
2006-07-10 12:12   ` Tomasz Chmielewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44B237C3.2090604@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=ecos-discuss@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).