public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: joseph biswal <joseph.biswal@gmail.com>
To: Chris Zimman <czimman@bloomberg.com>, Gary Thomas <gary@mlbassoc.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Redboot run image issues
Date: Wed, 25 Feb 2009 23:37:00 -0000	[thread overview]
Message-ID: <6aca9e460902251537y72771a9fy19dca123ecdbf1d1@mail.gmail.com> (raw)
In-Reply-To: <AE37CDDF7D55EB4AB77E0D63F38594CB0487D5@ny2545.corp.bloomberg.com>

Hi Chris/GAry:

My NAND boot works fine with this particular image. The issue looks
like whe i do a "RUN" of this same working piece of image out of RAM,
it seems to get stuck.

I debugged using BDI breakpoints as well as "diag_printfs" and looks
like it does not go beyond  HAL_MMU_OFF in
packages/hal/arm/mx31/ads/current/src/redboot_cmds.c. I don't
understand the flow in LaunchrunImage()  since it falls on the thin
line of swtching the MMU on and off. Any hints?

Would it be related to any of the relocations

void launchRunImg(unsigned long addr)
{
    asm volatile ("mov r12, r0;");
    HAL_CLEAN_INVALIDATE_L2();
    HAL_DISABLE_L2();
    HAL_MMU_OFF();


Thanks in Advance!
-Munro.



On Mon, Feb 23, 2009 at 3:42 AM, Chris Zimman <czimman@bloomberg.com> wrote:
>> 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.
>
> Without having seen your code, I don't know exactly what you're doing at
> startup, but booting from flash vs. starting from memory *typically* will use
> a different code path as far as the startup is concerned.
>
> Because NAND isn't linearly addressable, in a typical NAND boot scenario, it
> usually copies a very small amount of code from the NAND into a local buffer
> and starts executing from there.  That code is responsible for getting the
> rest of the code out of NAND and into memory.  Just taking a quick look at
> the Freescale site, it appears that for at least some version of Redboot,
> they've made the necessary change to copy the Redboot image from NAND into
> SDRAM.
>
> See:
>
> http://www.freescale.com/files/dsp/doc/app_note/AN3672.pdf?fpsp=1&WT_TYPE=App
> lication%20Notes&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentatio
> n
>
> --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

  reply	other threads:[~2009-02-25 23:37 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
2009-02-23  9:43             ` Chris Zimman
2009-02-25 23:37               ` joseph biswal [this message]
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=6aca9e460902251537y72771a9fy19dca123ecdbf1d1@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).