This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: More question on GDB Stub for NECVR4373 board.
- To: "Charles Feng" <charles at zh dot t2-design dot com>
- Subject: Re: [ECOS] More question on GDB Stub for NECVR4373 board.
- From: "Ling Su" <lingsu at palmmicro dot com>
- Date: Thu, 3 Aug 2000 19:51:55 -0700
- Cc: <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Palm Microsystems, Inc.
- References: <012a01bffcc4$9afc0360$0201a8c0@raccoon> <00080309021700.00745@charles_linux>
- Reply-To: "Ling Su" <lingsu at palmmicro dot com>
Hi, Chareles,
Thanks a lot for your helpful response for my post on eCos mailing list.
I still met troubles to run the test cases of eCos tools.(Please refer my
last post on the list). I also tried to compile the Hello.c and
simple-alarm.c use mips64vr4300-elf-gcc, I got a lot of warnings and got two
over 1M byte "a.out", of course, when I invoke mips64vr4300-elf-gdb to load
them, both failed.
I carefully following the instructions of "Getting start with eCos", but
failed.
If you have spare time, please kindly point me out some clue. Thanks!
Best Regards,
-Ling
----- Original Message -----
From: "Charles Feng" <charles@zh.t2-design.com>
To: "Ling Su" <lingsu@palmmicro.com>; "Ling Su" <lingsu@palmmicro.com>;
<ecos-discuss@sourceware.cygnus.com>
Sent: Wednesday, August 02, 2000 5:56 PM
Subject: Re: [ECOS] More question on GDB Stub for NECVR4373 board.
> On Thu, 03 Aug 2000, Ling Su wrote:
> > Hello, everyone,
> >
> > Since I met troubles to burn the gdbstub ROM for NECvr4373 board, I'd
like
> > to looking some help from the list. More specifically, I hope someone
can
> > help answer following questions, Thanks in advance!
> >
> > <1>. Has anyone successfully run eCos via the gdbstub on NECvr4373
board? I
> > knew Jifl did it, I'd like to query if anyone else succeed in doing
this?
> We did and we're doing.
>
> >
> > <2>. I observed the PCI bus signal after I mounted the gdbstub EPROM
that I
> > burned, there is no any active signal showing out there. Since the UART
is
> > on South bridge chip, it must be accessed via PCI bus, this mean
something
> > wrong with my gdbstub or my board. I doubt if my board doesn't work, or
at
> > least not fully functional. (But I am pretty sure the PMON comes along
with
> > the board works very well.) This is the reason I'd like to check if
anyone
> > else successd in burning the GDBSTUB except Jifl.
> Please notice the endianess problem. The PMON runs in little endian while
the
> default comipler settings of ecos is big endian (if you don't know what
> endianess is, read any MIPS books). You have to disconnect the jumper JP66
on
> the board to set the endianess to be big. After you have done this, I
guess
> you can connect to the gdb by your stub
>
> > > <3>. Till this step, I have no clue to do further
> observation, but I'd like > to burn a PCI test program in to EPROM to take
a
> test for the hardware. I > found there are two test cases, pci1.exe and
> pci2.exe. Could I apply > "mips64vr4300-elf-objcopy -O binary" on them to
a
> binary file, and burn it > to the EPROM to test it directly without
gdbstub?
> >
> > I think <3> is the most urgent one for me. Could anyone drop me a clue?
> > Jifl, please do me a favor. :)
> >
> > Regards,
> > -Ling
> --
> Regards
> Charles
> mailto:charles@zh.t2-design.com
>