EECTuning.org

tvrfan

Just a clarify after all this time. 22CA is not a short bank in the .bin I have, but it does have some weird values in .bin bank 1 after 0x1dfff. So it could be a short bank bin with RAM at 1e000 to 0x1ffff, with maybe some kind of bug in the read process. .bin also has a 'dummy' bank 9. Could be ha...

tvrfan

What jsa said .... Welcome to coding. Have a look at the Ford software programming manual (in OpenEEC) . What you described is right, the short jump uses the lowest three bits of the jump instruction and adds it to the TOP of the 8 bit following value to give a *SIGNED* offset. By default the top (m...

tvrfan

further... My copy of 22CA however DOES have the filler blocks in front of each bank, so the 'map' of banks to file addresses is - <bank no>, <file address>, <rom start>, <rom end> # bank 0 2000 02000 0ffff # bank 1 12000 12000 1ffff # bank 8 22000 82000 8ffff # bank 9 32000 92000 9ffff so no fiddli...

tvrfan

.bin file layout This is one of those things which takes a bit of work to get the hang of, until you know what to look for - The layout of the .bin file depends on which EEC reader was used. There is no official standard layout, as all the readers were written as someone's project. A single bank EEC...

tvrfan

Just a clarification on checksum. In all bins there is a start and an end address stored, and this defines what range the checksum uses. in A9L this is at 0x786a and 786c (two words, 0x2000 and 0x9ffe). in AA bin, it's at 0x2050 and 0x205e. (0x2000 and 0x3fff). Older bins like AA use a byte based ad...

tvrfan

later on, chips were made by other companies, and I don't know what numbers or options they had. There were 8065 CPU ones made by Toshiba, which had all sorts of extras on the same physical chip, and it was called an 'EPIC' I think. Oh, and some of the boards had chips on both sides as well. AA - Oo...

tvrfan

For learning about how the code works, I recommend you look at my 'AA' listing. Not 'cos it's mine, but because it's the smallest code found to exist (only 0x2000 to 0x3fff) and has no feedback sensors, no saved RAM, and was pretty much the first UK EEC IV to be released. So it's a simple, small sta...

tvrfan

Yeah, if you think about the address ranges in binary, they will typically be only 1 bit difference, which in real life could be an external pin (maybe 2) on the chip which will be grounded or +5 volts, so again a kind of 'shortcut'. Or may have been a built in option. Alpha - Who knows ? there have...

tvrfan

More background info which might be useful. As a IT geek, know that hardware-wise you can put any memory (or chip) at any address you like, within reason. The 8061 was a descendant of the original 8096, but with lots of changes for a 'real time' setup. The 8061 starts from its 'boot' at 0x2000, whic...

tvrfan

A couple of thoughts on this. Even in the older EECs you can actually have as many dimensions as you want, fairly cheaply. How ? A lot of the funcs were already actually lookups to scale a value to a table row or column number for a table lookup. I think there are a few RPM x TEMP ones in almost eve...

tvrfan

Yep, there's a few more things screwed up than I thought. Thanks to jsa for his testing - excellent stuff as always. For all of you, report anything that looks wrong, and I will check, although I have quite a list already so it may not be immediate... Some stuff in V5 is also kind of experimental (f...

tvrfan

Guys, have just released latest SAD, version 5.0.1 to github/EEC-IV-disassembler. Have added a some new features and done a big tidy up. Most likely still some bugs, but I want you guys to play with it and give me feedback. This version has new syntax with math calculations and multi bit fields are ...

tvrfan

I don't think it's been covered so far, so I am adding this nugget. As I remember - The early EECSucka circuits did not work on EEC-V (8065 CPU). This wasn't just about the bank. The memory chips/MBUS in earlier 8061 EEC would allow just 'read', 'read', 'read' on the MBUS as the read address would b...

tvrfan

Yes, Wine has come a long way. Emulating Windows is no easy task. Wine was just an idea/question, and you are right in that if the various tuner software products expect services which are no longer allowed (e.g. direct COM port access) then wine will not help either. But how to keep those tuner pro...

tvrfan

Couple of notes which might help. Virtualisation can be switched off in the BIOS on most motherboards. It will stop things like Virtualbox running. That may be another way to go. I think it may be called "AM-V" or "AMX" or something like that. Windows vs. Linux. I'm staying away from any recommendat...

tvrfan

A note about interpolation... The lookup code in ALL bins for both 1D (function) and 2D (table) already does linear interpolation between the cell values. 'Linear interpolation' simply means that if you feed in a value which is half way between two values in the lookup columns, it will output a valu...

tvrfan

Not only that, but there's no duct tape, so it's not a PROPER repair...

Good pic though....

tvrfan

At the risk of horrifying everyone - A serious question... how common are those old GM EEC boxes in US ?? I ask because from what I see on the web, they do at least use a totally standard CPU and a standard pluggable/erasable ROM chip. (I don't know if they are still available though) This means tha...

tvrfan

On a more general note - in my long history of rebuilding and fixing cars, I can say that it's not at all unusual to have poor grounding affecting all sorts of stuff, lights, sensors, instruments, even misfires. It's bad enough on steel body cars, but a LOT worse on GRP body cars. All it needs is so...

tvrfan

Acronyms covered in links from Jsa, but a bit extra here for info. Cars are noisy environments, so the EEC has more than one power in, for injectors, separate for CPU and so on, so big power pulses (injectors) don't mess up sensor signals. Same for ground, so more than one power return. Sensors actu...

tvrfan

Well having been fooled (but only on the surface as I didn't look) by a duplicate post of mine, I can only agree. When it comes to ANY link ANYWHERE I am always suspicious of what is there. We get regular spam and phishing emails, many look totally genuine, and here in New Zealand, the scammers even...

tvrfan

Duh !! I was being dumb, I didn't even check the html link....
Thanks

tvrfan

I assume the last post by ismailkho is an error somewhere, as it's a copy of my previous post further up...

tvrfan

For 8061 and 8065, the top bit (bit 7 for byte, bit 15 for word, bit 31 for double word) marks the value as negative *IF* the value is being treated as SIGNED...

Added this as it's not just bytes.

tvrfan

OK. Careful here.... I don't want anybody confused, so will try to give a quick overview. 1. 'Data' can be signed or unsigned, anywhere. It's not linked with size. As Cgrey says it's up to the reader of that data, even if the reader happens to be for a CPU instruction. 2. When anyone starts with a n...

tvrfan

xd41 .., Yep, The offset part is SIGNED, in a short (=byte) indexed address, so 0xde as a signed value is -(0x22) in effect, so as calculated 0x27e - 22 = 25c. And 0x9e = -(0x62). You are most definitely NOT the first person here to be caught out by this ! I wrote that '-( )' in that odd way because...

tvrfan

Oh, yes I forgot, in later bins there are also TABLES which are scalers for further table lookups. This makes last table lookup a result of FOUR inputs (or a 4D table in other words). I'm not entirely sure, but I think all the scaler values are x*256 to give whole number in top byte and fraction par...

tvrfan

That looks like A9L.... The loop that loads those 'base' registers is here. 84ed: a1,22,20,14 ldw R14,2022 R14 = 2022; # calibration Table pointers 84f1: 3c,24,01 jb B4,R24,84f5 if (Console_flag = 0) { # enable ints if console enabled 84f4: fb ei interrupts ON; } 84f5: a1,f0,00,18 ldw R18,f0 R18 = f...

tvrfan

Shortened story of AA bin.... I never did actually tune it. That was my plan, but it didn't happen. Originally my idea was to buy a Cologne engine (2.8L V6) with Bosch 'K' injection for a swap into a kit car. (In UK at the time. There were carb, Bosch 'K', and EEC-IV versions around.) I went to see ...

tvrfan

I've never used BE or similar, as it turned out. I do keep up with the disassembly part as it's interesting to me. I can say that scalers and scaled values are used all over the place in all the bins, and most are fixed point values. This is all to minimise the calcs and make them faster. It's a com...

Search found 590 matches

Re: 22CA bin - anyone analyzing this one ??

Re: Understanding how Checksum range is figured out

Re: Understanding how Checksum range is figured out

Re: Understanding how Checksum range is figured out

Re: FORD Custom EPROMs and Address range information

Re: FORD Custom EPROMs and Address range information

Re: FORD Custom EPROMs and Address range information

Re: FORD Custom EPROMs and Address range information

Re: FORD Custom EPROMs Address ranges

Re: Knock sensor and ignition advance logic

Re: SAD version 5 (alpha)

SAD version 5 (alpha)

Re: Historic EEC-V info request

Re: Windows 11 with LM-2, Tweecer R/T and BE 5.365

Re: Windows 11 with LM-2, Tweecer R/T and BE 5.365

Re: Retarding spark cells, best practice?

Re: HELP MAF curve needed urgently

Re: Moates Out of Business

Bad earths

Re: 1995 F150 EEC-IV questions

Re: F'n spammers!

Re: first steps - Disassembly - walkthrough

Re: first steps - Disassembly - walkthrough

Re: CMPB question.

Re: CMPB question.

Re: CMPB question.

Re: first steps - Disassembly - walkthrough

Re: CMPB question.

Re: first steps - Disassembly - walkthrough

Re: first steps - Disassembly - walkthrough