Yes. There are examples of tables in RZASA defined without a known purpose. Row and column count needs to be known. Have a look at the RZASA lst with cmt file and check out the table lookup subs.
LEDS, yeah why not.
Search found 290 matches
- 2024 May 29, 08:21
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 387
- Views: 73041
- 2024 May 29, 05:01
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 387
- Views: 73041
Re: EEC V file conversion
Needs some time spent on it to work out the contents of various temporary registers and the purpose of the sub.
RZASA
OMAE2 L1a1fe does look like the start of the equivalent structure.
OMAE2
Solve one...both solved.
Yes these are tables.
1873E
18806
188CE
From the comments in DIR for LU Subs, tells you what the registers hold for table lookups.
swTb34EPPH is a table.
RZASA
Code: Select all
0803b: b3,41,99,9c,40 ldb R40,[R40+9c99] TMP7L = [TMP7L+19c99];
0807d: b3,45,99,9c,44 ldb R44,[R44+9c99] TMP9L = [TMP9L+19c99];
080d3: b3,3d,99,9c,3c ldb R3c,[R3c+9c99] TMP5L = [TMP5L+19c99];
OMAE2
Code: Select all
0b8fd: b3,41,fe,a1,40 ldb R40,[R40+a1fe] R40 = [R40+1a1fe];
0b93f: b3,45,fe,a1,44 ldb R44,[R44+a1fe] R44 = [R44+1a1fe];
0b995: b3,3d,fe,a1,3c ldb R3c,[R3c+a1fe] R3c = [R3c+1a1fe];
Yes these are tables.
1873E
18806
188CE
From the comments in DIR for LU Subs, tells you what the registers hold for table lookups.
The table address is loaded into R3C before a table lookup sub call.###### Word Table Lookup Subroutines: R3C Tb_Addr Reg, R34 Column Input Reg, R36 Row Input Reg
###### R38 Column Quantity Input Reg, R3E Output Reg
swTb34EPPH is a table.
Code: Select all
09756: a1,1c,5d,36 ldw R36,5d1c TMP2L = uuyFn.0x15d1c;
0975a: b3,01,93,f3,38 ldb R38,[R0+f393] TMP3L = VS_U4_DELTA;
0975f: 10,09 rombk 9
09761: ef,84,93 call 92ae8 SLU92AE8_UUYFn ();
09764: ac,3c,34 ldzbw R34,R3c TMP1L = TMP5L;
09767: a1,2c,5d,36 ldw R36,5d2c TMP2L = uuyFn.0x15d2c;
0976b: b3,e4,fd,38 ldb R38,[Re4+fd] TMP3L = VSBART_RT;
0976f: 10,09 rombk 9
09771: ef,74,93 call 92ae8 SLU92AE8_UUYFn ();
09774: ac,3c,36 ldzbw R36,R3c TMP2L = TMP5L;
09777: ad,08,38 ldzbw R38,8 TMP3L = 8;
0977a: a1,3c,5d,3c ldw R3c,5d3c TMP5L = swTb34EPPH; <<<<<<<<<<<<<<<<<<<<<<<<
0977e: 10,09 rombk 9
09780: ef,b0,96 call 92e33 SLU92E33_Y16SWTb (); <<<<<<<<<<<<<<<<<<<<<<<<
09783: a0,3e,3c ldw R3c,R3e TMP5L = TMP6L;
- 2024 May 28, 15:44
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 387
- Views: 73041
Re: EEC V file conversion
For RZASA L19C99 I've given it a structure command and ?? in its comment because it's wasn't clear at the time.
What code have you got from LST that accesses L19C99?
What code have you got from LST that accesses L19C99?
- 2024 May 24, 14:02
- Forum: A1C - 80/90s EFI-SD4x Speed Density
- Topic: A1C XDF Additions
- Replies: 16
- Views: 2127
Re: A1C XDF Additions
106 bytes used of 128 leaves some possible spare for 128kb kam hardware.Hardware Manual wrote: ^ Electronics Division PECE DepartmentINTRODUCTION TABLE 1-4. REFERENCE PUBLICATIONS
*Functional and Electrical Specification for a 128-Byte Custom Keep-Alive Read/Write Memory (KAM) ES-N7700010FBCADA
* Functional and Electrical Engineering Specification for a 2K-Byte Keep-Alive RAM with parallel I/O (RAM1/0) ES-N7500030FSCAGA
*Functional and Electrical Engineering Specification for a 2K-Byte Keep-Alive RAM with Serial and Parallel I/O (RAM/CART) ES-N7500120FSCAGA
...
MEMORY (on-board 81C61, 81C62, 81C65, & 81C66)
The 81061, 81062, 81065, and 81066 all have the same memory size and type, and memory addressing circuits. Memory on-board these devices consists of 2,048 bytes of read/write static RAM. This RAM was specifically designed to provide keep-alive storage for user data in battery powered systems. The RAM can store data while consuming less than 100 microamps of current under a wide input voltage operating range (+2.0 VDO to +5.5 VDO) when non-active. The 81065 and the 81066 provide a special keep-alive power input for their RAM.
Later chips apparently keep RAM alive as well according to the above snips.
- 2024 May 23, 06:32
- Forum: A1C - 80/90s EFI-SD4x Speed Density
- Topic: A1C XDF Additions
- Replies: 16
- Views: 2127
Re: A1C XDF Additions
IIRC the EEC hardware manual gives address ranges that are KAM, that's not to say there's a spare in the range.
- 2024 May 16, 17:20
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 387
- Views: 73041
- 2024 May 16, 00:03
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 387
- Views: 73041
Re: EEC V file conversion
Locate where the base value is set for REE, then set an Rbase accordingly.
Hint, search LST for REE.
Hint, search LST for REE.
- 2024 May 14, 20:10
- Forum: Hardware, Programming & Disassembly
- Topic: EEC V file conversion
- Replies: 387
- Views: 73041
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: 387
- Views: 73041
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: 387
- Views: 73041
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.