I mentioned earlier that the DMR generated DIR might have errors, you have found one.BOOSTEDEVERYTHING wrote: ↑2023 Oct 26, 15:36 I am slightly confused on the HEGO_DATA_BFR areas here.
This goes to being aware of address modes, and then time to check them all.
An immediate value of 0x400 is being loaded here.
It may go on to be used as an address, which would correctly receive HEGO_DATA_BFR as the correct name.
It could be many things.
In this case it is used 2 calls deep at L92CF2, it's added to BG_TMR.
It's a classic example of why the immediate load naming problem still exists with SAD.
Attempts to get SAD to track immediate values later used as an address have proved futile so far.
If it's known to not be an address then it could be unnamed. Catch 22, addresses end up unnamed because the address could not be tracked.
The solution to date has been the user is king, adjust the DIR to suit.
The solution as it stands is to change the DIR using address ranges.
Change this line in the DIR;
Code: Select all
SYM 400 "HEGO_DATA_BFR" #UY
The 2nd line is optional.
I'd place it at the 400 location in DIR.
Code: Select all
SYM 0400 02000 9435B "HEGO_DATA_BFR"
SYM 0400 9435C 9438F "0x400" # # Immediate Load
SYM 0400 94390 9FFFF "HEGO_DATA_BFR"
This works for V4.07.16B and V4.012
Code: Select all
SYM 0400 02000 0FFFF "HEGO_DATA_BFR" #UY
SYM 0400 12000 1FFFF "HEGO_DATA_BFR"
SYM 0400 82000 8FFFF "HEGO_DATA_BFR"
SYM 0400 92000 9435B "HEGO_DATA_BFR"
SYM 0400 9435C 9438F "0x400" # # Immediate Load
SYM 0400 94390 9FFFF "HEGO_DATA_BFR"
I've previously suggested changing to a global name with alternate zones.
Like this;
Code: Select all
SYM 400 "HEGO_DATA_BFR" #UY
SYM 9435C 9438F 400 "0x400" # # Immediate Load
EDIT: Fixed ranged address order and added 4.07.16b version.