public inbox for
 help / color / mirror / Atom feed
* RE: [ECOS] Redboot run issues when HAL_MMU_OFF is issued
       [not found] <>
@ 2009-03-02 17:09 ` Chris Zimman
  0 siblings, 0 replies; only message in thread
From: Chris Zimman @ 2009-03-02 17:09 UTC (permalink / raw)
  To: joseph biswal; +Cc: ecos-devel, ecos-discuss

> I am trying to do a rom update to update the redboot  and in the
> process, i need to do a run.
> But "run"'s getting stuck as you saw.
> What is  " _heap1" with reference to the linker script.  How does the
> "start address" in the  line "RAM: 0x00000000-0x0ff00000,
> [0x00014020-0x0fed1000] available" get populated. In my case it points
> to _heap1. My golden working redboot image had a different  "start
> address" and it worked fine without issues.

Hi Joe

Without seeing the sources, I can't really say too much more, but I can tell
you in principle that you're making this way too hard if all you're trying to
do is update Redboot.

Freescale tends to do their own versions of Redboot, and (no offense
Freescale folks) they aren't the cleanest ports.

I don't really have cycles to dig through their tree right now unfortunately.
You may consider talking to eCosCentric if you want a supported port to the


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-03-02 17:09 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <>
2009-03-02 17:09 ` [ECOS] Redboot run issues when HAL_MMU_OFF is issued Chris Zimman

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).