Re: [Freemint-discuss] Disassembly of TOS 1.00 with Ghidra

[Thorsten O. <ad...@th...>]

On Dienstag, 7. Januar 2025 21:52:53 CET Eero Tamminen wrote:
> => Could those TOS address & symbol names be provided as Hatari (= nm
> format) symbol files, along with checksums for matching original TOS images?

For TOS 2.x/3.x/1.4 such maps already exist (as for example tos306de.map in 
the glue directory: https://github.com/th-otto/tos3x/blob/master/glue/
tos306de.map) However those were generated automatically, and could need some 
cleanup for Hatari's purpose. So i would like to know how they should look 
like.

- they have some absolute symbols like SELECTED that are used in assemmly 
sources. I guess it is better to remove those?

- they also have absolute symbols for the system variables. Should those be 
retained?

- same for absolute symbols for I/O addresses.

- there are some duplicates that should definitely be removed

- Also note that BSS starts at address 0, unlike normal program layout. Could 
this lead to problems?

- there are some symbols from the VDI overlay area, that appear as absolute, 
but are actually BSS variables. However they overlap with other symbols.

- What about local labels from assembler code? Mostly they are from BIOS + 
VDI. Would it be better to remove them (for the profiler to work), or retain 
them to easier identify exact locations?

- TOS 1.00/1.02 have another difficulty: there are text symbols from BIOS/
GEMDOS/VDI, followed by data symbols, then followed by text symbols from AES/
DESKTOP. Could those data symbols confuse Hatari?