From: "Zimman, Chris" <czimman@bloomberg.com>
To: <ajmas@bigfoot.com>, <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Boot issue without hardware debugger
Date: Thu, 01 Jun 2006 00:18:00 -0000 [thread overview]
Message-ID: <3B530EF12E388B408ECC3162BA8C00F401BBE730@ny2526.corp.bloomberg.com> (raw)
Andre,
Perhaps your hardware setup (eg. memory controller, UARTs, etc.) is
being done by the JTAG debugger and Redboot isn't currently doing the
right setup for your platform?
--Chris
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Andre-John
Mas
Sent: Wednesday, May 31, 2006 6:20 PM
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Boot issue without hardware debugger
Hi,
I am in the process of modifying a modified redboot to our needs. The
problem I have now is that if the hardware debugger is plugged in
everything works, but when it is removed the system won't boot properly,
instead it gives me:
+$T0440:fe00cba0;01:000052ac;
I am not sure if the following build warning is of signaficance, or how
to resolve it:
BFD: /home/mas/workspace/bootloader_install/bin/bootloader.elf: warning:
Empty loadable segment detected, is this intentional?
Is there something I should be checking for?
Andre
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
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 reply other threads:[~2006-06-01 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 0:18 Zimman, Chris [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-31 22:20 Andre-John Mas
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=3B530EF12E388B408ECC3162BA8C00F401BBE730@ny2526.corp.bloomberg.com \
--to=czimman@bloomberg.com \
--cc=ajmas@bigfoot.com \
--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).