.ALLOCATION Verbosity

For philosophical discussion: Given an example FLASH chip, 64k size, 8
uniform sectors, to contain 3 types of information (application boot
images--2 sectors, app. configuration data--2 banks, and app. event logs--2
banks), to what extent would you define the details with SECTION to appear
in .ALLOCATION ? Terse, compromise, and verbose ideas are presented below.

Start End Size Type Name
0000 FFFF 65536 UDATA FLASH

Start End Size Type Name
0000 3FFF 16384 UDATA FLASH-APP-BANKS
4000 7FFF 16384 UDATA FLASH-CFG-BANKS
8000 BFFF 16384 UDATA FLASH-LOG-BANKS
C000 FFFF 16384 UDATA FLASH-UNUSED

Start End Size Type Name
0000 1FFF 8192 UDATA FLASH-APP-1
2000 3FFF 8192 UDATA FLASH-APP-2
4000 5FFF 8192 UDATA FLASH-CFG-1
6000 7FFF 8192 UDATA FLASH-CFG-2
8000 9FFF 8192 UDATA FLASH-LOG-1
A000 BFFF 8192 UDATA FLASH-LOG-2
C000 FFFF 16384 UDATA FLASH-UNUSED

What are the PROS and CONS you see? The verbose PRO is single source for
the memory map documentation/definition and, because it is part of code,
which is more likely to be kept up to date; its CON is that the .ALLOCATION
output is very long on each compile (the actual case would have 14 banks in
FLASH in addition to other sections).
----------------------------------------------------------------------
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 Mon May 09 2005 - 11:31:19 PDT