V4.012 DIR for RZASA consolidated from various sources.
Details in header of DIR file.
Search found 280 matches
- 2024 May 12, 01:17
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 370
- Views: 63932
- 2024 May 10, 01:35
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 370
- Views: 63932
Re: EEC V file conversion
Apply a range to 0x708 so the flags are not displayed where 0x708 is the base value.
- 2024 May 09, 16:40
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 370
- Views: 63932
Re: EEC V file conversion
SAD picks up the first SYM it finds at an address but comment one of them out for now with V4 and see if it helps.
V5 will allow size to be specified so Y and W names will be applied for byte and word oprations respectively.
Everything after a # is a comment, so it is not processed by SAD.
V5 will allow size to be specified so Y and W names will be applied for byte and word oprations respectively.
Everything after a # is a comment, so it is not processed by SAD.
- 2024 May 08, 17:45
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 370
- Views: 63932
Re: EEC V file conversion
Interesting that it prints flag for an immediate load. Smells like a bug.
- 2024 May 07, 15:45
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 370
- Views: 63932
Re: EEC V file conversion
If you used an rbase of 0 for temp1l over a range, the address would resolve and display the name.
Is temp1l actually holding the value 0 though??
Is temp1l actually holding the value 0 though??
- 2024 May 07, 05:09
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 370
- Views: 63932
Re: EEC V file conversion
Thanks for posting the updates. I have been consolidating the various RZASA data sources I have access to into a more comprehensive DIR. It includes math information with the intention of testing further SAD releases. I'll get that done before I look at your updates.
Cross eyed, yeah, sounds about right!
My consolidated RZASA DIR matches what you have above.
I'll look at your OMAE2 example after I finish messing with consolidation.
0be6 should be working equally as 10be6.
What do you get for V5.07 or V5.08?
Could well be a bug in V4.012.
Post an example DIR line and LST line where its not working.
Cross eyed, yeah, sounds about right!
My consolidated RZASA DIR matches what you have above.
Code: Select all
# Call from L9F19D Sub_9f157
# Call from L9F317 Sub_9f157
# SCall from L9F8A7 Sub_9f7e0
Sub_9f8be:
9f8be: a1,a6,06,46 ldw R46,6a6 TMP0L = KFEGO1_CT1;
9f8c2: a1,be,06,34 ldw R34,6be TMP1L = KFEGO2_CT1;
9f8c6: c3,d8,50,00 stw R0,[Rd8+50] KFEGO1_CT_TL = ZERO;
9f8ca: c3,01,08,07,00 stw R0,[R0+708] KCAT11_SUM_T = ZERO;
9f8cf: c3,01,0c,07,00 stw R0,[R0+70c] KCAT12_SUM_T = ZERO;
9f8d4: c3,01,06,07,00 stw R0,[R0+706] KCATIF_SUM_T = ZERO;
9f8d9: 20,16 sjmp 9f8f1 goto 9f8f1;
# Call from L9F1D7 Sub_9f157
# Call from L9F31A Sub_9f157
# SCall from L9F8A3 Sub_9f7e0
Sub_9f8db:
9f8db: a1,be,06,46 ldw R46,6be TMP0L = KFEGO2_CT1;
9f8df: a1,d0,06,34 ldw R34,6d0 TMP1L = KFEGO1_CT_TL;
9f8e3: c3,d8,52,00 stw R0,[Rd8+52] KFEGO2_CT_TL = ZERO;
9f8e7: c3,01,0a,07,00 stw R0,[R0+70a] KCAT21_SUM_T = ZERO;
9f8ec: c3,01,0e,07,00 stw R0,[R0+70e] KCAT22_SUM_T = ZERO;
0be6 should be working equally as 10be6.
What do you get for V5.07 or V5.08?
Could well be a bug in V4.012.
Post an example DIR line and LST line where its not working.
- 2024 Apr 17, 06:28
- Forum: Hardware, Programming & Disassembly
- Topic: EESucka - found on ebay
- Replies: 9
- Views: 989
Re: EESucka - found on ebay
Any info in the notes over and above the github link above?
- 2024 Apr 17, 06:24
- Forum: Hardware, Programming & Disassembly
- Topic: SAD Version 5 (alpha)
- Replies: 143
- Views: 17521
Re: SAD Version 5 (alpha)
At the moment the scan command takes a start address and scans until it hits a return.
Scan over a range would take a start address and an end address.
If a scan reaches a return before the end address, scan would start at the next address after the return and scan again. Repeat until the start to end address range is scanned entirely.
Yes, some bins require an excessive number of scan commands, that could be alleviated with scan range.
Scan over a range would take a start address and an end address.
If a scan reaches a return before the end address, scan would start at the next address after the return and scan again. Repeat until the start to end address range is scanned entirely.
Yes, some bins require an excessive number of scan commands, that could be alleviated with scan range.
- 2024 Apr 16, 06:20
- Forum: Hardware, Programming & Disassembly
- Topic: EESucka - found on ebay
- Replies: 9
- Views: 989
- 2024 Apr 13, 17:01
- Forum: Hardware, Programming & Disassembly
- Topic: SAD Version 5 (alpha)
- Replies: 143
- Views: 17521
Re: SAD Version 5 (alpha)
The address / inline scalar issue...
http://www.efidynotuning.com/forum/view ... 678#p14506
http://www.efidynotuning.com/forum/view ... 678#p14506