public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: Ling Su <lingsu@palmmicro.com>
Cc: eCos discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Help needed:  eCos on NEC vr4300 board.
Date: Tue, 18 Jul 2000 07:42:00 -0000	[thread overview]
Message-ID: <39746CBE.630A7AC6@redhat.co.uk> (raw)
In-Reply-To: <018901bff026$87286c20$0201a8c0@raccoon>

[ Please remember to CC the ecos-discuss list, I can't always give personal
replies, and at least if its on the list, someone else has a chance ]

Ling Su wrote:
> 
> Thanks.
> 
> I tried using HyperTerminal in WinNT, I didn't get any output from the
> gdbstub. I will try to figure out if there is anything wrong with my own
> operation. In the meantime, could you please answer me some following dump
> questions, thanks a lot.
> 
> <1>. I should burn the 'stubrom.bin' instead of 'stubrom.img', is that
> correct?

Yes.

> <2>. There are two serial port on the board J1 and J2, I connected to J1, is
> that correct?

Yes.
 
> <3>. NEC provide me a PMON and it works fine, can I use it to download ecos
> program? It work in 9600 bitrate instead of 38400, and could the gdbstub.bin
> works in 9600B?

Yes - when configuring eCos for your application, there is a HAL
configuration option to choose ROM monitors. Choose PMON there.

To allow the program to be debugged in GDB, you would probably also need to
include GDB stubs in your application (this configuration option is under
the HAL debugging section). I haven't tried to see how this works with PMON
though.
 
> <4>. Everytime when I use the PMON by NEC, I must reset several times and
> wait for a while to see the light on board blinking, this is the way to make
> sure the PMON is running, how could I check this with the gbdstub.bin to
> make sure it is running?

Sorry but the GDB stub has no equivalent other than to attach something to
the serial port and look for output. If there was no output, perhaps the
ROM was not programmed correctly, in which case, perhaps it is an issue
with the ROM programmer? Perhaps your programmer needs to be told to
byteswap the ROM - this sometimes happens.

For what it's worth, we have verified that the prebuilt stubrom.bin file
does definitely work with our boards here.

> I'd like to check if the NEC board support 38400 UART, but I did get a
> VR4373 from NEC, why not it is so difficult to work. Sorry for the bothering
> and appreciate your answer very much.

We use the DDB-VRC4373 board here. If yours is the same, then I'm sure it
should support 38400.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

      parent reply	other threads:[~2000-07-18  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-14 22:14 Ling Su
2000-07-17  7:26 ` Jonathan Larmour
2000-07-17  7:29   ` Jonathan Larmour
     [not found]     ` <018901bff026$87286c20$0201a8c0@raccoon>
2000-07-18  7:42       ` Jonathan Larmour [this message]

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=39746CBE.630A7AC6@redhat.co.uk \
    --to=jlarmour@redhat.co.uk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=lingsu@palmmicro.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).