Modifying Motronic 2.3.2 ECU hardware and software.

[-ice-]

Seems that i will receive an Ostrich 2.0 in the next weeks

Does anyone have experience with the address hit feature? Is it possible to log all addresses which were hit and also display the data-bytes?

For example to identify the calling code parts, which will use dptr to read data from a known place. Is it fast enough to trace all eprom accesses? It's called realtime but seems to have serial 1mbps connection.

Am I the only one who works on the motronic code (except prj ). Don't want to write monologs here...


Regards

[prj]

Seems that i will receive an Ostrich 2.0 in the next weeks

Does anyone have experience with the address hit feature? Is it possible to log all addresses which were hit and also display the data-bytes?

For example to identify the calling code parts, which will use dptr to read data from a known place. Is it fast enough to trace all eprom accesses? It's called realtime but seems to have serial 1mbps connection.

Am I the only one who works on the motronic code (except prj ). Don't want to write monologs here...


Regards

I think your wet dreams are strongly exaggerated
Or in other words - forget it, the tracing is pretty useless.

That said, this ecu's microcontroller is so simple it's really easy to see in code what accesses what, the problem is as always putting the big picture together.

[minim]

Keep posting I'm reading this and a lot of other threads on the subject because I'm considering to try this myself. I do fear that I lack knowledge about this and that's what keeping me from ordering what I need to persue this.

I did program a bit low lvl back in school but the last years it's been only high lvl programming of PLC systems. Is it hard to start from scratch again and do this step by step? I've pretty much forgotten all I knew about assembly by now... The thing I want the most is a better log feature than I got today but for a starter I would just be using time on figuring out how things are connected.

[pasbogdan]

The thing I want the most is a better log feature than I got today but for a starter I would just be using time on figuring out how things are connected.

What log feature are you talking about?

[prj]

What log feature are you talking about?

The one you have seen

Maybe I should start selling it to those adventurous enough.

[-ice-]

I just started to develop an own emulator hardware which will be able to filter for opcodes and queue the previous an next instructions in SRAM to be read out.

Basicly a microcontroller with an extern RAM, which emulates the motronic eprom.

Regards

[pasbogdan]

I do not see why not.If jap has interface with "file/open,edit/add more power" why not a 2.3.2 nice log screen and graph?

[prj]

I just started to develop an own emulator hardware which will be able to filter for opcodes and queue the previous an next instructions in SRAM to be read out.

Basicly a microcontroller with an extern RAM, which emulates the motronic eprom.

Regards

Waste of time ... maybe fun for a school project but no practical use whatsoever.
The 8051 is so primitive, you can literally just map out the memory, document the multibyte subroutines, such as multiplication, shifting, division as well as map lookups and then you can just read the code.

There is no guessing as to what reads what, it's right there at the start of each call, and IDA lays it out beautifully.

[-ice-]

In my view the emulation of both eproms is a good practical use. I don't want to buy a second ostrich.

I don't have IDA pro, too expensive...

Bye

[prj]

Ostrich is cheap. It is far cheaper buying a 2nd one rather than making your own project... well depends how much free time you have of course.

As for IDA, there is a free version:

https://www.hex-rays.com/products/ida/support/download.shtml

I have not checked if it supports the 8051 CPU though.

[-ice-]

It's not the price, it's because I don't have low level access to it. I will mainly use it to test modified firmwares.

[prj]

I think you need to spend more time sitting in IDA Pro and understanding code and less time making up gadgets that will leave you none the wiser if you want to get anywhere with this ECU. But hey, it's just my opinion.

[minim]

Really tempted to order willem GQ-4X programmer and ostrich 2.0 to start playing with this

[-ice-]

I have received my Ostrich today

I decided to use TunerPro RT with this emulator but I seem to have a problem with loading the binary files.

I connected the emulator directly to my old eprom programmer (Galep3). I created a bin file with tunerpro (you can see it at the bottom of the screenshot). After loading this to the Ostrich I read it out with the Galep (result is at the top of the screenshot). Basicly the numbers are correct but there seems to be an offset of 1.

Does anybody know where this comes from? I don't know which device i can trust now...

bye

[prj]

There should not be any problems.
Try loading the binary using EmUtility, just to rule out that you have incorrectly configured your TunerPro project.

Load it to the ECU and communicate...

P.S. I notice the buffer length is 7FFF. Are you working with 3B? If it is AAN, loading a 87C257 file will NOT work, the 87C257 has a tri-state latch, which the Ostrich does not have.