public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Uwe Kindler" <ukindler@htwm.de>
To: <ecos-maintainers@sources.redhat.com>
Cc: <jld@ecosentric.com>
Subject: H8/300 and H8S architecture
Date: Mon, 08 Dec 2003 17:05:00 -0000	[thread overview]
Message-ID: <000e01c3bdae$02e50af0$2c79378d@uwepc> (raw)

Hello John,

here are the main differences between H8/300 and H8S CPUs:


Register Architecture
=====================

H8/300:
-------
- Sixteen 8-bit general registers, or
- Eight 16-bit general registers
- PC (16 Bit)
- CCR (Condition Code Register - 8 Bit)

H8S:
-------
- Sixteen 16-bit general registers
- also usable as sixteen 8-bit registers
- or eight 32-bit registers
- PC (24 Bit)
- CCR (Condition Code Register - 8 Bit)
- EXR (Extended Register - 8 Bit)
- MAC (Multiply-Accumulate Rgister -  64 Bit (only H8S/2600))


Address Space
=====================

H8/300:
-------
- Maximum 64K-byte address space (PC is 16 Bit)

H8S:
-------
- 16-Mbyte address space (PC is 24 Bit)


Interrupt Handling
=====================

H8/300:
-------
- normal Interrupt mode
- When "I" bit is set to "1," in CCR register, all interrupts except NMI are
masked.
- 64 Interrupt vectors (2 Bytes long each)

H8S:
-------
- extended Interrupt control mode
- mask control is done in eight levels for interrupt requests except for NMI
by comparing the EXR interrupt mask level (I2 to I0 bits)
- 8 different interrupt priority levels (level 0 - level 7)
- 128 Interrupt vectors (4 Bytes long each)


Because of these differences in register architecture the HAL_SavedRegisters
structure is completely differrent for both architectures. Also the global
interrupt handling, masking and vector table differs in both architectures.
That means large parts af the vectors.S and context.S (which are part of the
eCos architecture HAL) are different for both architectures. In my opinion,
mixing these both architectures in only one H8/300 architecture is possible
but make it a lot more complicated and harder to understand (just have a
look at the current EDOSK-2674 port)

Best Regards, Uwe Kinlder



                 reply	other threads:[~2003-12-08 17:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='000e01c3bdae$02e50af0$2c79378d@uwepc' \
    --to=ukindler@htwm.de \
    --cc=ecos-maintainers@sources.redhat.com \
    --cc=jld@ecosentric.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).