This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
notes:comporg:spring2024:projects:dapx [2024/03/24 23:43] – [Debug Registers] wgates1 | notes:comporg:spring2024:projects:dapx [2024/03/24 23:49] (current) – [Debug Registers] wgates1 | ||
---|---|---|---|
Line 435: | Line 435: | ||
===Printing registers=== | ===Printing registers=== | ||
+ | |||
+ | ===Debugging our debugregs Subroutine=== | ||
+ | Trying to get your debugregs to have the correct output is challenging, | ||
+ | |||
+ | <code asm> | ||
+ | mov R0, 0x00000000 | ||
+ | mov R1, 0x00000001 | ||
+ | mov R2, 0x00000002 | ||
+ | mov R3, 0x00000003 | ||
+ | mov R4, 0x00000004 | ||
+ | mov R5, 0x00000005 | ||
+ | </ | ||
+ | |||
+ | You repeat this above process for registers from 0 to 13. It is important to note that you do this right before you call the subroutine so the values that you just put in don't get wiped out from your previous ASM code. | ||
+ | |||
+ | |||
+ | |||
===Calling debugregs=== | ===Calling debugregs=== | ||
As we have worked on these dap projects, the process of calling such debug subroutines has become simpler. With dap0, we had to have the following in our program: | As we have worked on these dap projects, the process of calling such debug subroutines has become simpler. With dap0, we had to have the following in our program: |