I want to know the program flow through the ecu code. I think it would help a TON with code development. Maybe this is a really dumb idea but how could we monitor the program counter?
I thought of using some mechanism in the rom code (serial interrupt or something we could call often) but when it got executed to send me the PC word, it would be the PC word for the serial sending code. Even with a serial interrupt, we would not be getting every instruction executed. And if the ecu was streaming this info, the serial port probably couldnt keep up.
Does anyone have any ideas? I suppose I could take some snapshots of memory (the entire memory space) and go through the program flow like that, but I want the PC data.
Ben
Could this be done externally? I remember from my days of using Borland Turbo Pascal and others that they had a step through feature where it would go to the next instruction each time you hit the F8 key (I think). It would also allow you to keep track of Variable values for each step. Of course, implementing this would be taxing, as you'd need to essentially write a 66xxx emulator from scratch. It would definitely be worth it though. It would allow those of us who are not gifted coders to follow everything more easily.
We know what each command is... we should be able to create a software application that simulates the processor.
Is it possible that Oki already has this?

It would make sense for them to have written it at some point...
I don't know S*-t about what you guys are talking but I think that you could use the trace function of the Romulator sotware to see the processor working.
peluca wrote:
I don't know S*-t about what you guys are talking but I think that you could use the trace function of the Romulator sotware to see the processor working.

Yeah, probably...
Re: ECU Debugger
I know this is an old thread but does anybody have a program that logs address hits from an ostrich? I would write one, but dont really have time at the minute?
Re: ECU Debugger
Not publicly, you'd have to write one.
Re: ECU Debugger
was wondering what the hell that trace function was for...
/pgmfi/forum/media/a8/a89e4a0276735b7534873bd10cf56704cd41af62cefe99738fda5c9462364ae6.zipif your looking to see if specific sections of code are used, it might be easier to create a datalogging variable and poll that...
Re: ECU Debugger
I've started writing an address tracer for the ostrich V2. it record rom access location within a given range and outputs the code at that rom location from a dasm'd rom.
I'll upload the program once its finished (not long now

)
More info here ->
http://www.hondamod.co.uk/free-stuff/moates-ostrich-v2-rom-tracer
Re: ECU Debugger
Neat program!
Re: ECU Debugger
ya cant wait till its done
Re: ECU Debugger
man. you guys must be NEO bloodline ...
Re: ECU Debugger
RicardoNC wrote:
man. you guys must be NEO bloodline ...

Or common sense and the ability to read directions. It's all documented pretty well.
Re: ECU Debugger
Qemu can do it but it would be a shit-ton of work to implement all the virtual hardware.