Initializing EXT-IRAM on the CMD12A4 using SwiftX Pro

Hello all,

First time poster to the list…

I have just upgraded to SwiftX Pro 3.1.7. On my version 2.5 the following
code worked to initialize EXT-IRAM on the CMD12A4 board. Now when I use it
at debug I get:

INCLUDE DEBUG START ?
SYNC-CORE START CR GREET
At line 4 in C:\Projects\ForthInc\Projects\Bus_A4\DEBUG.F

I assume that this means that START bombed at compilation time, never
completing the definition, however I did not get an error message during
build.
The following is the code from the “Initialize Data Space” section of the
START.F file in the 68HC12 folder. I have also included definitions that I
did not modify. Any clues as to what I am doing wrong? Perhaps there is a
better way to do it. It is odd that the CONFIG file for the CMD12A4 defines
an external IDATA section but does not restore it at startup.

Best regards,

Tom Talkington

IRAM
IDATA LIMITS DROP EQU IN-DATA
   HERE IN-DATA - EQU DATA-SIZE

EXT-IRAM
IDATA LIMITS DROP EQU EXT-IN-DATA
   HERE EXT-IN-DATA - EQU EXT-DATA-SIZE

CDATA HERE EQU IN-CODE EXT-DATA-SIZE DATA-SIZE + ALLOT
   HERE 0 , EQU CHECKSUM

IDATA

INTERPRETER

: SAVE-IDATA ( -- )
   DATA-SIZE 0 ?DO IN-DATA I + C@ IN-CODE I + C!C LOOP
   EXT-DATA-SIZE 0 ?DO EXT-IN-DATA I + C@ IN-CODE DATA-SIZE + I + C!C LOOP
;

: SAVE-CHECKSUM 0 CDATA LIMITS SWAP DO I C_at_C + LOOP
   CHECKSUM !C IDATA ;

: SYNC-CORE CONNECT CHECKSUM @C DISCONNECT CHECKSUM @C
   <> ABORT" KERNEL MISMATCH" CONNECT ;

TARGET

: /IDATA ( -- )
   IN-CODE IN-DATA DATA-SIZE CMOVE
   IN-CODE DATA-SIZE + EXT-IN-DATA EXT-DATA-SIZE CMOVE ;

----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe swiftx" to listar_at_forth.com
For help with listar commands, send subject "help" to listar_at_forth.com
Archives are located at http://www.forth.com/swiftx -- check them out!
----------------------------------------------------------------------
THIS LIST IS NOT FOR BUG REPORTS! Send bug reports to support_at_forth.com.
Received on Wed Apr 17 2002 - 22:35:17 PDT