[ASM & Hex✓] IWRAM location of the DMA pointers to non-temporary variables?

[hjk321]

I have ASM code that needs to access a certain variable in the DMA, namely 0x4011, but as you probably know the actual location of this variable in the RAM changes all the time. I could (probably) get around this by using copyvar to 0x8005 or something before callasm-ing (as XSE script is evidently able to bypass this BS), but as this might not be an option in the future I wanted to know how seasoned ASM coders got around this, and the location of the IWRAM DMA cache (which contains pointers to each variable protected by DMA).

Thanks for any help in this matter.

 

[Skeli]

I have ASM code that needs to access a certain variable in the DMA, namely 0x4011, but as you probably know the actual location of this variable in the RAM changes all the time. I could (probably) get around this by using copyvar to 0x8005 or something before callasm-ing (as XSE script is evidently able to bypass this BS), but as this might not be an option in the future I wanted to know how seasoned ASM coders got around this, and the location of the IWRAM DMA cache (which contains pointers to each variable protected by DMA).

Thanks for any help in this matter.

Loads the value of the var into r0.

ldr r0, .Var
bl Var_Load
...

Var_Load:
ldr r1, =0x806E569
bx r1

.align 2
.Var: .word 0x4011

 

[hjk321]

Loads the value of the var into r0.

ldr r0, .Var
bl Var_Load
...

Var_Load:
ldr r1, =0x806E569
bx r1

.align 2
.Var: .word 0x4011

Cool, but how does it work?

 

[Skeli]

It calls the function at 0x806E568 which reads the value of the var. if you're asking how the specific function works, then get yourself a copy of Knizz's Fire Red IDB and take a look at the function.