Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!willett!ForthNet
From: ForthNet@willett.pgh.pa.us (ForthNet articles from GEnie)
Newsgroups: comp.lang.forth
Subject: Metacompilation
Message-ID: <2280.UUL1.3#5129@willett.pgh.pa.us>
Date: 27 Jan 91 22:36:05 GMT
Organization: (n.) to be organized.  But that's not important right now.
Lines: 43


 Date: 01-25-91 (10:10)              Number: 975 of 976 (Echo)
   To: JOSEPH IMMEL                  Refer#: NONE
 From: RAY DUNCAN                      Read: NO
 Subj: COMMENT                       Status: PUBLIC MESSAGE
 Conf: FORTH (58)                 Read Type: GENERAL (+)

 The proper serial port initialization for your board will depend on the
 CPU clock speed and other factors (e.g. the model of 80x96 you are
 using).  We test the code with our board but customization of the
 startup code for your hardware environment is your responsibility ---
 this includes serial port initialization, memory map, and so on.

 The directives ROM and RAM are clearly described in the manual.  ROM
 controls the starting address and length of the ROM memory space.  RAM
 controls the starting address and length of the RAM memory space, which
 contains the variables, stacks, and any code that is compiled
 interactively *when the target is running.*

 For testing purposes we often set ROM and RAM up so that both use memory
 that actually lies within RAM on the evaluation board.  This allows you
 to use the on-board monitor on the board to download the executable
 image into RAM and then run it immediately, without the hassle of
 burning new EPROMs each time.  In any event, whatever memory you declare
 as ROM (even if it is physically, actually, RAM memory) is memory that
 is viewed as read-only by the metacompiler.  The address ranges for ROM
 and RAM directives should *never* overlap.  The compiler sees them as
 two different address spaces -- the ROM space is writable at
 metacompilation time and read-only at execution time, and the RAM space
 is not accessable at metacompilation time (only allocatable) and is
 read-write at execution time.

 I have authorized you for conference #5.  This is the metacompiler
 support conference, and you can download free updates to your compiler
 from that conference as they are released.

 NET/Mail : LMI Forth Board, Los Angeles, CA (213) 306-3530
 <<<>>>
-----
This message came from GEnie via willett.  You cannot Reply to the author
using email.  Please post a follow-up article, or use any instructions
the author may have included (USMail addresses, telephone #, whatever).
Report problems to: dwp@willett.pgh.pa.us or uunet!willett!dwp