From: joseph biswal <joseph.biswal@gmail.com>
To: Chris Zimman <czimman@bloomberg.com>
Cc: Gary Thomas <gary@mlbassoc.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Redboot run image issues
Date: Mon, 23 Feb 2009 05:21:00 -0000 [thread overview]
Message-ID: <6aca9e460902222121u1a07eb34g65b2b51d5d8776ab@mail.gmail.com> (raw)
In-Reply-To: <AE37CDDF7D55EB4AB77E0D63F38594CBF415@ny2545.corp.bloomberg.com>
My final intent is to get my redboot port to boot from the NAND flash.
I am trying to run this image from NAND flash but it gets stuck even
before spitting anything on the console. Hence i turn to the BDI
debugger where i try running the image from RAM and see if it works.
I am running on a MX31 based board with Freescale PDK1.4.
On Sun, Feb 22, 2009 at 9:30 PM, Chris Zimman <czimman@bloomberg.com> wrote:
>> Whereas, when i load and runthe same redboot.bin from an existing
>> working version of "redboot.bin " in RAM, i get the following
>> : It gets stuck after printing "phys_addr=0x80100000" on the serial
>> console. I am guessing something somewhere is wrong in the memory
>> location but i am not sure where to start with. Would it be a problem
>> with the linker script, mlt file or something else?
>> ARe there other files in the HAL i need to look into? WHat actuallly
>> happens when "LaunchRunIMage" in the redboot code is invoked??
>
> That's not going to work because the Redboot code isn't relocatable like
> that. Like you can't just load it and launch it from any location. If I
> understood you right, you're trying to launch a ROM or ROMRAM image from
> within Redboot. This is probably not what you want.
>
> You can configure a Redboot image to be launched from RAM, but this is
> generally not necessary unless you're doing special things (eg. replacing a
> Reboot ROM mode image, etc.)
>
> Beyond that, without seeing what's going on in the HAL setup
> (hal_platform_setup.h), it's difficult to guess which of any number of things
> it may be tromping over that could cause it to hang.
>
> I'm still missing what it is that you're ultimately trying to do here.
>
> --Chris
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2009-02-23 5:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 5:21 joseph biswal
2009-02-21 12:16 ` Gary Thomas
2009-02-22 18:17 ` joseph biswal
2009-02-22 21:20 ` Chris Zimman
2009-02-23 2:47 ` joseph biswal
2009-02-23 3:30 ` Chris Zimman
2009-02-23 5:21 ` joseph biswal [this message]
2009-02-23 9:43 ` Chris Zimman
2009-02-25 23:37 ` joseph biswal
2009-02-23 14:58 ` Rutger Hofman
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=6aca9e460902222121u1a07eb34g65b2b51d5d8776ab@mail.gmail.com \
--to=joseph.biswal@gmail.com \
--cc=czimman@bloomberg.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary@mlbassoc.com \
/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).