public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alex Lennon" <ajlennon@arcom.co.uk>
To: "Jonathan Larmour" <jlarmour@redhat.com>
Cc: "Gary Thomas" <gthomas@redhat.com>, <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Re: Romboot in i386 (continued) - comms. problems
Date: Tue, 14 Aug 2001 05:06:00 -0000	[thread overview]
Message-ID: <NEBBKJHOALKOLCFPGELEEEOJCPAA.ajlennon@arcom.co.uk> (raw)
In-Reply-To: <3B781241.61389C3C@redhat.com>

>>Why? Just enable the FIFOs and leave it at that. If interrupts are
>>disabled, the HAL code won't notice any difference.

Right. Thanks - the 16550 I'm using for test downloads fine at 38400
with FIFOs on (after a couple of initial packet timeouts ?)

I'd like to get the debug link going as quickly as possible eventually
and I can't see 115200 working with this setup. I'd still like to put the
ISR code together.

Also, as I'm using a 386EX I have two 16450's which I'd like the option
to use for debugging purposes - again, I'd need interrupt driven comms.

I'm still trying to understand what the problem is here with an interrupt
driven implementation. Is polled mode for Redboot a design decision? 
If so is there somewhere I can look for the background ?

Further down the line we're looking to put together an Ethernet driver
for the RTL8019, to eliminate all of the serial comms bottlenecking.
I take it that there is some level of interrupt support in Redboot for
this purpose ?

On a slightly different note, after the successful download of the
'hello' example the target seems to lock (I'm using Insight). I'd
like to see where this happens but I can't see a way to make
Insight/GDB breakpoint prior to execution of the first instruction.
Is there an obvious way of doing this which I'm just missing ?

Thanks,

 Alex



_____________________________________________________________________
The message in this transmission is sent in confidence for the attention of the addressee only and should not be disclosed to any other party. Unauthorised recipients are requested to preserve this confidentiality. Please advise the sender if the addressee is not resident at the receiving end.

All reasonable precautions have been taken to ensure no viruses are present in this e-mail by using MessageLabs Virus Control Centre. Arcom Control Systems Ltd cannot accept responsibility for loss or damage arising from the use of this e-mail.

Company registered in England No. 1608562.
Registered Office: Unit 8, Clifton Road, Cambridge, UK  CB1 7EA. Tel No. 01223 411200.

  reply	other threads:[~2001-08-14  5:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  3:21 Alex Lennon
2001-08-13  3:39 ` Gary Thomas
2001-08-13  3:52   ` Alex Lennon
2001-08-13  4:11     ` Gary Thomas
2001-08-13  4:23       ` Alex Lennon
2001-08-13 10:45         ` Jonathan Larmour
2001-08-14  5:06           ` Alex Lennon [this message]
2001-08-14  5:32             ` Jonathan Larmour
2001-08-13  4:30     ` Nick Garnett
2001-08-13  4:30   ` Nick Garnett

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=NEBBKJHOALKOLCFPGELEEEOJCPAA.ajlennon@arcom.co.uk \
    --to=ajlennon@arcom.co.uk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gthomas@redhat.com \
    --cc=jlarmour@redhat.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).