From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: "Olaf Peters" <olaf.peters@technolution.nl>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] GDB stubs on EDB7211
Date: Thu, 08 Feb 2001 06:55:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010208085256.00aca7d0@larwe.com> (raw)
In-Reply-To: <JGEEJKHHJODGMOKKPBENOENLCAAA.olaf.peters@technolution.nl>
Hello Olaf,
>Thanks for your help so far.
Well, I actually haven't helped you yet :)
>I tried to built the EDB7211 gdb stubs with eCos 1.3.1, but it
>doesn't work (I followed the guidelines in the ecos-tutorial-arm.pdf file).
>Any suggestions why the EDB7211 GDB stubs I built myself with eCos 1.3.1
>don't work and the shipped images do work?
One thing I discovered recently with help from the Red Hat guys is that if
you make a global change to your eCos configuration (such as switching from
RAM to ROM startup), it is advisable to delete the build tree completely
rather than just doing a make clean. Perhaps that issue has bitten you?
Also, what tools are you using? (I have an ulterior motive in asking, btw ;)
I have not tried to build stubs. However I _have_ built ROM-bootable
applications, so I know that much is possible. I have also noticed some
bizarre behavior on the EDB7209 board [with EP7212 on it], perhaps you
might get a better result if you follow the exact steps of:
* power down board, fit JP2
* power up board, press and hold RESET for several seconds
* press and hold WAKEUP for at least a second
* download .bin file
* power down board, remove JP2
* wait a few minutes
* power up board, press and hold RESET for a few seconds
* press and hold WAKEUP for at least a second
* board may not start up immediately, it may require several resets and
"time out" sitting powered off
When you try your stub on the EDB, does the "DIAG" LED come on?
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."
next prev parent reply other threads:[~2001-02-08 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 5:54 Olaf Peters
2001-02-07 6:01 ` Lewin A.R.W. Edwards
2001-02-08 3:08 ` Olaf Peters
[not found] ` <JGEEJKHHJODGMOKKPBENOENLCAAA.olaf.peters@technolution.nl>
2001-02-08 6:55 ` Lewin A.R.W. Edwards [this message]
2001-02-07 8:20 ` Wilson Kwan
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=4.3.2.7.2.20010208085256.00aca7d0@larwe.com \
--to=larwe@larwe.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=olaf.peters@technolution.nl \
/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).