From: "Ling Su" <lingsu@palmmicro.com>
To: "Pengyu Xue" <pyxue@zh.t2-design.com>,
<ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Re: Little Endian GDB stub for VRC4373
Date: Tue, 16 Jan 2001 17:33:00 -0000 [thread overview]
Message-ID: <004501c08025$41fc8f70$0201a8c0@raccoon> (raw)
In-Reply-To: <001301c07c4d$06f7c100$1002a8c0@t2design>
Hi, Dear Pengyu and others,
With the enlightment of Penyu's email, I decided to go ahead to bring up the
Little Endian GDB stub. I also take a look at the platform dependent code, I
didn't find any specific part to be modified. The LSBFIRST and MSBFIRST
macro definiation guards all the related type definition and address
mapping. I changed the ecos.ecc for the CFLAG after I generate it by apply
the "stubs" Template. Then I go ahead change the
./install/include/pkgconf/hal_mips_vr4300.h make the LSBFIRST become default
setting. Then I execute make for the gdb_module.bin, it generated
successfully. Unfortnately, it doesn't work after I replace it with my only
stub on board. I trace the PCI bus by using LA, no signal pin is active, so
it doesn't execute at all. I am wondering what happened, so I think it would
be better to make a Big Endian stub first before I jump for the little
endian one. In my memory, I have never make a good stubs before by using my
own configuration. I tried "ecosconfig new vrc4373 stubs" on the new CVS
repository and some old ones which I am working on. To my surprise, no one
works. (I did remember to change the JP66 for the endian issue).
Now, I am quite confused on how to make my own GDBstubs work. Since looks to
me, even the default big endian version doesn't work at all. I am using the
binary one provided in ecos-1.3.1 release till now due to my failure on
building it. Have anyone experienced the same problem? or how to resolve it?
Pengyu, could you please do me a favor to send a little endian stub to my
private mailbox? I hope I could get a working one and take a try.
Thanks for everyone prvoiding valuable hints!
Regards,
-Ling
----- Original Message -----
From: "Pengyu Xue" <pyxue@zh.t2-design.com>
To: <ecos-discuss@sourceware.cygnus.com>
Sent: Thursday, January 11, 2001 8:06 PM
Subject: [ECOS] Re: Little Endian GDB stub for VRC4373
> Yes, we are working on little-endian mode in the platform
> vr4300-vrc4373 for a long time, it really works.
> You can compile a little-endian mode gdb stub using -EL in your compile
> flag, and also you must modify the CYGPKG_HAL_MIPS_MSBFIRST to
> CYGPKG_HAL_MIPS_LSBFIRST, and -O2 is necessary for compiling gdb stub.
> If you still have some problems, maybe I can help you, because we have
> almost our eCos project in this platform. ^_^
>
>
>
>
> pyxue
>
>
next prev parent reply other threads:[~2001-01-16 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 20:07 Pengyu Xue
2001-01-16 17:33 ` Ling Su [this message]
2001-01-17 1:54 ` Jesper Skov
2001-01-17 10:46 ` Ling Su
2001-01-18 0:50 ` Jesper Skov
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='004501c08025$41fc8f70$0201a8c0@raccoon' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=pyxue@zh.t2-design.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).