EFIDynoTuning Forum

Please do read those manuals, they answer (almost) all questions, They are pretty big, but stick with it.

I actually printed them out so I could have them next to me while trying to find stuff in the lst file. Made it easier to "flip" back and forth between the two. It took a long time to print both books and I can't recommend that anyone else do it. LOL. But I am still a little old school and like pages sometimes.
I will have to download the a9l bin and try comparing some of that to my lst file as well. I haven't gotten very far yet and anything is a big help.
I think I got the dir file cleaned up pretty well, so hopefully that will help me some as well. most likely still many errors in it, but to err is human.
Thanks for all the tips and I welcome anything you guys can offer me, good or bad. I am learning.

One to two THOUSAND pages, double sided 4 pages per side, find and search works better for me.
I have printed some pages, good on you!

I find the 'handbook' more useful for a quick check of something, but go into the manuals for something specific or detailed...but then you are right - it can be a bugger to find what you want in all those pages, even with a pdf. At least the search works.

Repeat - I added the handbook to OpenEEC in Github yesterday. A scan of the pages, but still really useful.

Yeah, If I don't see what I want in the contents I use the search and then open up the book to work back and forth with the code. It is two 1.5 inch binders completely full for the hardware and software manuals. May not have been the smartest thing to do, but it does help at times to have both pages open side by side, full size to get it through my head what is going on. I downloaded the handbook yesterday and will definitely be using that for sure. Looks much easier for referencing op codes and such. Thanks for uploading it!

Is there an easy way to make a spreadsheet where I can copy al of the subroutines out of the msg file and paste them into the spreadsheet and have another column next to it to manually enter the subroutine from rzasa that matches up with that, and make it so it will not let me put a duplicate entry into the rzasa column? or at least warn me that it is a duplicate? And then have the ability to have a main column for both strategies to enter notes about what the subroutine is doing? And be able to add more columns to it to be able to add more strategies as I go? I know that is kind of a lot, but I am no good at all with excel and have no idea how to implement what I am trying to do.

BOOSTEDEVERYTHING wrote: ↑2023 Dec 06, 11:27 It looks to me to be an Output State Control subroutine? I am looking into the software manual about this one this evening when I get home to see if I can figure out exactly what it is doing.

Yes, OSC code related to value substitution from a diagnostic tool over SCP. Some info in CRAI8 and others.

BOOSTEDEVERYTHING wrote: ↑2023 Dec 08, 14:13 Is there an easy way to make a spreadsheet where I can copy al of the subroutines out of the msg file and paste them into the spreadsheet and have another column next to it to manually enter the subroutine from rzasa that matches up with that, and make it so it will not let me put a duplicate entry into the rzasa column? or at least warn me that it is a duplicate? And then have the ability to have a main column for both strategies to enter notes about what the subroutine is doing? And be able to add more columns to it to be able to add more strategies as I go? I know that is kind of a lot, but I am no good at all with excel and have no idea how to implement what I am trying to do.

It is relatively easy.
Import or insert the msg file into excel.
Either import as space delimited or use text to columns after insert.

Unfortunately colums are not well aligned in MSG, but sym sub entries seem consistent so it's workable. Space delimited should be better than fixed width.

Once you have all the sub names in a column, filter the column for Sub.

Copy the results of the Sub filter to a clean worksheet.
Use conditional formatting on the column to turn cells red for duplicates.

Add whatever you like to adjacent columns.

Bound to be plenty of youtube howto video.

Thank you. I will try that when I get home tonight. I was trying to overcomplicate things, I think. I think that doing this may help me understand better what routines are doing and maybe make them easier for me to spot in other bins as I go. And I can add them to the spreadsheet as I go and maybe make it so I can mark them off as I go through them, mainly so I don't confuse them with other subroutines as I go through the code. Should be searchable as a spreadsheet as well so when I come up to a sub in the code I can go to that sheet and see if I have been there or not. At least all of that is in theory anyways. LOL

Also have a question about this one. Should the R1aa be Rab?

No, you cant read an odd byte as a word. When you do you get the even word from 0x100. Its a shortcut.

Hidden away in the manual or handbook (somewhere) is that later 8065 version had an 'odd word option' as a shortcut. It's equivalent to a REGBANK 1 followed by operation, so R38 = Raa, where Raa is in REGbank 1, = R1aa. It caused quite a bit of WTF as well when first spotted. You cannot have a word operation on an odd address. That lowest bit is stripped off for things like auto increment, so the hardware logic already exists, kind of.

It's another awkward feature of 'nailing on' stuff to an existing CPU core. In 8061, registers must fit in a single byte (0-0xff), and addresses in 16 bits (2 bytes 0-0xffff). To expand this for more registers and more program space, 8065 has a REGISTER bank of 2 bits (0-3) and ROMBANK 4 bits (0-15) for addresses, which have to exist on the side like an 'environment setting' so that all the opcodes remain the same, and these get added in as part of the operation logic. [ It's horrible .....]