[tvrfan]

I've added the old 80C196 user manual into a docs repository in Github/openEEC for info anyone wanting to know 8061 or 8065 CPU core basics, along with Tom Cloud's original doc which explains the more specialist Input/Output mechanisms and extra/different opcodes.

Enjoy !!

I will add the basic EEC guide when I finish it.............


(thanks motorhead1991)

[motorhead1991]

It's the whole premise behind the project

[Chucko]

Bringing this thread back from the dead...

This Github site is a tremendous resource! Thank you.

Signed, a former assembly language programmer.

[motorhead1991]

Bringing this thread back from the dead...

This Github site is a tremendous resource! Thank you.

Signed, a former assembly language programmer.

Easy to back up, easy to track, easy to share :thumbup:

[ironmanisanemic]

I have a ton of files i have came across and accumulated over the years. Its all on my google drive and is publicly view able with the following link. The biggest addition i think that i can offer is the ford EEC-IV/V programming pocket book.

https://drive.google.com/open?id=0B3c0I ... 2pyU2VnRnc

[Chucko]

Thanks, ironmanisanemic!

[tvrfan]

Just a note here - I had a look too, some of those docs are now superceded, and the bank swop one (written by me) is WRONG at the detail level (but the analysis of how the code works is still correct). This was before I saw the Ford Handbook, which gives the true answer.

For Techies/Advanced/IT geeks, by FAR the best doc to get is the Ford handbook. Although it's a series of snapshot page pics, (some fuzzy) it gives the TOTAL summary of the 8061 and 8065, and several of the 'add on' special I/O chips, even some memory maps. But it's exactly what it says, a handbook, so some of the detail explanations are missing.

As backup and detail info the Intel 8096 (or later 80C196) full user guide gives all that extra detail for the opcodes and PSW status flags, but stick to the core parts, as the addressing and some opcodes don't exist or are different in the 806x versions.

The two of these together should give enough info for any disassembler or emulator to be written from scratch.

If you are tuning, the the strategy docs are the ones to read to understand the code design aims, and then look at the code itself.
But it's ALL useful for learning as much as you can, just be aware some of it is quite old, and the details might be wrong here and there.

[ironmanisanemic]

If you have any updated docs to what I have saved, I would love to get a copy to add to the collection. Over the last few years I've been collecting anything I can find related to eec-iv and eec-v and the 8061/65 series processors. I'm always looking for more things to add. I have an old sales/service vhs from ford describing the operation of the "new" fuel management system. It's not going to teach us anything that we don't already know, but is cool for preservation purposes. I just need to find a easy way to convert it to a digital format from the original vhs. If anyone ever stumbles across anything on auction sites or anywhere please let me know so I can see about adding it to the collection. I leave this open to everyone to add to so it can become a museum of sorts.

[motorhead1991]

Among the collective, we could inform new tuners/disassemblers (me....)

Someday, I'll be at the level you guys are, but until then brute force hacking will do.

[tvrfan]

Another just in case - please don't think I'm 'knocking' anything there - I just want to help stop any misunderstandings and confusion.
It's already hard enough to look at low level machine code, especially some of the multibank tricks.
(ooh - an unintended pun there...)

I'm lucky as I've done this kind of stuff as a career, although not a lot of low level (=assembler) coding, enough to be useful to write SAD.

Ironman - I'll double check my file archive in case I've got something that's not in your collection - It looks like a great archive already.

Motorhead - I reckon you porting my C code to android is a damn good achievement already......

[motorhead1991]

Motorhead - I reckon you porting my C code to android is a damn good achievement already......

There really wasn't much porting involved in that, I just added a couple flags and cross compiled it...

[tvrfan]

In that case I hereby claim ALL THE KUDOS for writing good clean 'C' code, which isn't easy !!!
(Joking !! - - for some weird reason, smilies don't seem to work for me in this BB. Linux/Firefox issue ? Hmmm....No, smilies not disabled.)

Seriously, I'm truly glad it DID compile and run, as it does help prove code is pretty clean and memory management is OK.
(C code is notorious for dodgy memory handling and 'loose' pointer issues which tend to cause crashes)

[motorhead1991]

In that case I hereby claim ALL THE KUDOS for writing good clean 'C' code, which isn't easy !!!
(Joking !! - - for some weird reason, smilies don't seem to work for me in this BB. Linux/Firefox issue ? Hmmm....No, smilies not disabled.)

Seriously, I'm truly glad it DID compile and run, as it does help prove code is pretty clean and memory management is OK.
(C code is notorious for dodgy memory handling and 'loose' pointer issues which tend to cause crashes)

I did also compile it as a Linux library as well, and it worked still