Re: Sections and section types

Ron,
Wow, thanks, that was quite an effort on your part. I had missed the
.Sections definition (it is not described in my SwiftX or Forth
handbook); that will be useful.

I read through your examples, and it still seems that my simple
explanation is generally true: the current section always determines
where code is written (with no effect on where data is written), and the
current section type generally determines where data is written (with no
effect on where code is written), except for those definitions such as
Reserve that are restricted to a specific section type. SwiftX
automatically vectors the memory allocation and reporting definitions in
accordance with the selected section type.

Meanwhile I am still trying to figure out why I can't read back data
stored into CDATA in paged memory on an HC12. No one has responded to
this. Can you confirm that this should be possible, and that I must be
doing something wrong? I can see the data stored where I expect it to
be in the S19 file, so the problem seems to be in reading it back. The
SwiftX documentation describes E commands for accessing data in paged
data space, but it is not clear that they should be used for
Data in paged code space, and gives no examples of the format for the
e-addr argument. Nothing I have tried works.

Thanks,
David Graham

----------------------------------------------------------------------
swiftx_at_forth.com The SwiftX programming discussion email list
To unsubscribe, send subject "unsubscribe" to swiftx-request_at_forth.com
For list command help, send subject "help" to swiftx-request_at_forth.com
Message archives are located at http://www.forth.com/archive/swiftx
----------------------------------------------------------------------
This list is a forum for SwiftX users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Sun Jan 11 2004 - 10:28:58 PST