A binutils targeted at H8/500 would be useful because it would give us an assembler for the platform, rather than having to write machine code by hand.

Basically, dasmh85 is a disassembler (like IDA Pro, or objdump from binutils), which turns machine code into assembly, ie. something a lot more readable for you and me. But, it's very useful to be able to go in the other direction as well for large chunks of new code; hex editing with EcuFlash or some other software is fine for small changes, but for large chunks, like a flashing kernel, you really don't want to hand-assemble it. It's tedious, time-consuming, and very error-prone.

But, cart before the horse. I still need to find a minute to pull the ACD ECU out of the car and look at it on the bench. Hmm, I'll have to compare it to the ECU out of my 2g ('99 GSX), see how similar the two are.

 

FYI, for the archives: binutils 2.16.1 still sported H8/500 support. You have to configure it with "--target=h8500-coff", and it built just fine on Fedora 11 x86_64 (I was really expecting that to fail).

Also, for the IDA folks, I've attached an IDC script (just rename it to .idc instead of .txt) that should label all the H8/539F registers for you. I tried stuffing this into cfg/h8500.cfg, but kept getting syntax errors for really basic stuff, so I don't think register configuration is supported for that processor.

 

Thanks logic, I can read ASM and machine code and basic IDAPro stuff, but I never new the detail you have gone to here. thats cool. Maybe one day when I run out of things to do on EvoScan software I will take a look at these AYC in a disassembler.

 

EvoScan has been working for the last 12 months for AYC datalogging using pins 4/7/16 on the OBDII connector. But that is just for my Evo4 AYC, I'm not sure if it was different in the later Evo7/8/9

I have had lots of reports saying that the AYC actuator support in EvoScan works great. Anyone here got a vehicle that does not work with EvoScan Actuator support? what model evo is it?

 

I could never get logging to work on my IX with the updated cable that I purchased.

 

I cant get it to work on an Evo VIII or Ix that I have tested it on

 

same for me - I can not get it to work with my IX (using a modified 1.3U cable as per your instructions) and any Evoscan versions:
- actuators doen't work at all (tries to 'connect' - fail - and retry again and again)
- logging : 'conect sucessfully with the AYC ECU but logged data's never change (always 0xFF)

If it helps I can test new versions / send screenshot ,...

 

I tried today on an EVO 8 to log / bleed the ACD/AYC setup with evo scan 2.6 B14 and OP2 cable and nothing, same issues as everyone else.

 

The EFI actuators worked for me... but not the ACD/AYC ones as far as I can tell.

 

Just tried EvoIX FQ320, connects to AYC but random data and lots of fault codes i know are not really there. EFI side fine but AYC and ABS not work.

I could really do with this, infact its why i purchased Evoscan any help would be much appreciated.

 

same here, works perfectly with efi and not at all on ayc, for my evo 7

 

same problem , also no actuators
2003 evo 8 jdm

 

I think you guys are using an OpenPort 2.0 cable which is only supported in EvoScan v2.6 beta16 or later.

 

I am actually using an old Tactrix cable which I removed pin9 from
So at least I am not using the openport 2.0


Just noticed the pin1 and pin15 stuff on your website ... I not checked that before and I will check that tonight
Sorry about that

 

yes i use op 2.0
evoscan beta 16? or 15?