Locate where the base value is set for REE, then set an Rbase accordingly.
Hint, search LST for REE.
Search found 284 matches
- 2024 May 16, 00:03
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 379
- Views: 66258
- 2024 May 14, 20:10
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 379
- Views: 66258
Re: EEC V file conversion
You can add stuff yourself. Just post up the changes or the updated DIR. There is still some stuff to be found and lots of stuff to be identified.
The format is arranged with making it easier to convert from DIR to a definition in mind. That's a moving target.
When you look at definitions from BE and TP, they both follow
Once V5 is more usable changes will be made to suit such as :UW becomes [UW] or [UW flo=x*42] or whatever.
Could well change it all again. Time will tell.
Symbols, tables and function are parameters that go into a definition, the rest of it is stuff to make SAD work that does not go in a definition.
Special function registers are not editable and of little logging value.
RAM is not editable but holds logging targets.
ROM is editable.
The earlier RZASA dir's I've posted have been a bit disorganised as they were basically DMR conversion with stuff thrown in for testing, so better organised now.
Yes you should keep it organised.
The format is arranged with making it easier to convert from DIR to a definition in mind. That's a moving target.
When you look at definitions from BE and TP, they both follow
Once V5 is more usable changes will be made to suit such as :UW becomes [UW] or [UW flo=x*42] or whatever.
Could well change it all again. Time will tell.
Symbols, tables and function are parameters that go into a definition, the rest of it is stuff to make SAD work that does not go in a definition.
Special function registers are not editable and of little logging value.
RAM is not editable but holds logging targets.
ROM is editable.
The earlier RZASA dir's I've posted have been a bit disorganised as they were basically DMR conversion with stuff thrown in for testing, so better organised now.
Yes you should keep it organised.
- 2024 May 14, 05:52
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 379
- Views: 66258
Re: EEC V file conversion
Most of what you added matches up with parameters in Decipha's XDF, so that is good.BOOSTEDEVERYTHING wrote: ↑2024 May 13, 10:42 I attached another with my updated dir and comparison spreadsheet.
I see you have some additional parameters, so I've added those to the consolidated DIR attached below.
Continue on with the consolidated DIR below.
- 2024 May 13, 05:55
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 379
- Views: 66258
Re: EEC V file conversion
No DIR in the RZASA zip you attached.BOOSTEDEVERYTHING wrote: ↑2024 May 06, 08:57
Also, I am posting my updated OMAE2 and RZASA dir files that I have added to
LST alone is not much use for review.
DIR (and CMT if changed) is all that is required. No need for a copy of SAD to be included.
Looking through the LST you posted, your changes look like stuff that is covered by the RZASA XDF.
The consolidated DIR includes all the XDF stuff, so I'd suggest continuing with the consolidates DIR from here on.
Note what you change with a {7}. Give credit to the source of info or reason for changes, such as strategy name and page.
It would be best to comment out existing lines and add another line for changes you prefer.
I note a couple of immediate inline parameters have names added. That may be intentional or accidental. Without the DIR I can't see if a range was replied. You will see in the consolidated DIR I've elected to comment out Bank 0, 8 & 9 SYM's, with so many of them being immediate values, roughly 1000. SAD won't apply the names in the immediate location usually and may misname other identical values as you have noted yourself. Hopefully a future SAD update will resolve this.
I see you have elected not to use the CMT, you are missing all the info against the Timer structure in LST for starters.
- 2024 May 12, 01:17
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 379
- Views: 66258
Re: EEC V file conversion
V4.012 DIR for RZASA consolidated from various sources.
Details in header of DIR file.
Details in header of DIR file.
- 2024 May 10, 01:35
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 379
- Views: 66258
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: 379
- Views: 66258
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: 379
- Views: 66258
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: 379
- Views: 66258
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: 379
- Views: 66258
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.