diff options
author | Joel Sherrill <joel.sherrill@OARcorp.com> | 2000-06-29 23:00:48 +0000 |
---|---|---|
committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 2000-06-29 23:00:48 +0000 |
commit | 5532553209555c0a5a3c11206ff16192dd465160 (patch) | |
tree | 82b8bea30e32fb1928cb4e26f5d5415ff84ea42a /cpukit/score/cpu/h8300/README | |
parent | Using RPM names for versions now. (diff) | |
download | rtems-5532553209555c0a5a3c11206ff16192dd465160.tar.bz2 |
This is the initial addition of the port of RTEMS to the
Hitachi H8 family. This port was done by Philip Quaife
<philip@qs.co.nz> of Q Solutions and sponsored by
Comnet Technologies Ltd. The port was done based on RTEMS 3.5.1
to a Hitach H8300H. The port was updated to RTEMS 4.5 style
Makefiles/configure by Joel Sherrill <joel@OARcorp.com>.
While doing this Joel added support for the h8300-rtems to
binutils, gcc, newlib, and gdb.
NOTE: Philip submitted a BSP for a Hitachi evaluation board
which is being merged as a separate entity.
Diffstat (limited to '')
-rw-r--r-- | cpukit/score/cpu/h8300/README | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/cpukit/score/cpu/h8300/README b/cpukit/score/cpu/h8300/README new file mode 100644 index 0000000000..a55c61c662 --- /dev/null +++ b/cpukit/score/cpu/h8300/README @@ -0,0 +1,31 @@ +# +# $Id$ +# + + +This port was done by Philip Quaife <philip@qs.co.nz> of Q Solutions +using RTEMS 3.5.1 under DOS and Hiview. Philip used an H8300H +to develop and test this port. + +It was updated to 4.5 and merged into the main development trunk +by Joel Sherrill <joel@OARcorp.com>. As part of the merger, the +port was made to conditionally compile for the H8, H8300H, and H8300S +series. + +The status of each CPU subfamily is as follows. + +H8 - Although RTEMS compiles with for these CPUs, it does not + truly support them. All code that will not work on these + CPUs is conditionally disabled. These CPUs have a 16-bit + address space. Thus although a port is technically + feasible, some work will to be performed on RTEMS to + further minimize its footprint and address pointer + manipulation issues. + +H8H - Port was developed on this class of H8 so there should be + no problems. + +H8S - Port should work on this class of H8 but it is untested. + +--joel +28 June 2000 |