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??
Search found 276 matches
- 2024 May 07, 15:45
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 364
- Views: 60146
- 2024 May 07, 05:09
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 364
- Views: 60146
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: 401
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: 15661
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: 401
- 2024 Apr 13, 17:01
- Forum: Hardware, Programming & Disassembly
- Topic: SAD Version 5 (alpha)
- Replies: 143
- Views: 15661
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
- 2024 Apr 13, 16:53
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 364
- Views: 60146
Re: EEC V file conversion
By coincidence (or intentional obfuscation lol) scalar value happens to be 2280 at address 943a9 and function address happens to be bank 1 2280.
Both are valid with nothing to do with each other than the number 2280.
The example above gives me the scalar name and function name where expected. Post example code it you get something different.
I have put forward the idea, to tvrfan, of SYN as in single symbol.
To generate a definition from dir, the address is needed.
That might look like;
SYN 943A9 "1RATCH_MIN"
SYN 943AF "2RATCH_MIN"
SYM 12280 "Fn0x12280......"
FUN 12280 .......
For now use range for the scalar and function as needed.
What scalars and what files are you referring too?
Both are valid with nothing to do with each other than the number 2280.
The example above gives me the scalar name and function name where expected. Post example code it you get something different.
I have put forward the idea, to tvrfan, of SYN as in single symbol.
To generate a definition from dir, the address is needed.
That might look like;
SYN 943A9 "1RATCH_MIN"
SYN 943AF "2RATCH_MIN"
SYM 12280 "Fn0x12280......"
FUN 12280 .......
For now use range for the scalar and function as needed.
What scalars and what files are you referring too?
- 2024 Apr 12, 23:19
- Forum: Hardware, Programming & Disassembly
- Topic: SAD Version 5 (alpha)
- Replies: 143
- Views: 15661
Re: SAD Version 5 (alpha)
Thank you for your continued effort.
4.07.16b 11 Apr 2022 includes support word size tables.
Yes, 4.012 sym addresses can have issues with inline scalars.
4.07.16b 11 Apr 2022 includes support word size tables.
Yes, 4.012 sym addresses can have issues with inline scalars.
- 2024 Apr 12, 05:41
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 364
- Views: 60146
Re: EEC V file conversion
Originally 2280 was for V4.07.16B and 12280 was for 4.012.
The repeats can be deleted.
Put a bank prefix in, though it is technically incorrect it will name the scalars with V4.012.
The repeats can be deleted.
Put a bank prefix in, though it is technically incorrect it will name the scalars with V4.012.
Code: Select all
SYM 12280 943A8 943B1 "RATCH_MIN" #W via SADx
- 2024 Apr 10, 17:10
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 364
- Views: 60146
Re: EEC V file conversion
Ah yes, sorry, it is commented out because it's not giving desired results. Out of order too. Something I've been testing with. It needs to have a range applied before un-commenting.BOOSTEDEVERYTHING wrote: ↑2024 Apr 09, 16:03 I do have another question that I can not figure out. In RZASAMY.dir I have below...Code: Select all
#SYM 12280 "RATCH_MIN" #W via SADx #SYM 12280 "RATCH_MIN" #W via SADx SYM 144C0 "RATIV" #SYM 144C0 "RATIV" #UW Via SADx
Opcodes a1 and 89 are immediate address modes, they could be addresses or inline scalars, in this case they are inline scalars. SAD is unable to distinguish where to apply SYM's when a scalar value coincides with an 2address. The catch 22 previously discussed. It is something on the fix wish list with @TVRfanThat puts RATCH_MINCode: Select all
9439b: a0,37,36 ldw R36,R136 TMP2L = RATCH; 9439e: a0,23,38 ldw R38,R122 TMP3L = TP; 943a1: a1,00,3c,3a ldw R3a,3c00 TMP4L = 3c00; 943a5: ef,04,e9 call 92cac Sub_92cac (); 943a8: 89,80,22,42 cmpw R42,2280 943ac: db,06 jc 943b4 if (TMP8L < 2280) { 943ae: a1,80,22,42 ldw R42,2280 TMP8L = Func_12280; 943b2: 20,0a sjmp 943be goto 943be; }
For the purpose of converting DIR to DEF, value 2280 at both addresses 943a9 & 943af need to be captured.
Try
Code: Select all
SYM 2280 943a8 943b1 "RATCH_MIN" #W via SADx
Depending on which version of SAD is used, SAD may complain about a bank number.
You can apply range/s to the function so that it does not name the scalar value 2280 at L943ae.