Evo 10 - Ecuflash - 3 tables
Jun 7, 2008, 02:48 AM
#36
http://forums.openecu.org/viewtopic.php?p=18064#18064
Here is the original thread from OpenECU forums.
-It has the EVOX EDM Rom file for download
-Some map/xml? info that is incompatible with ECUFlash directly
-And the offsets we found today for the x and y axis summarized
Without further info I can't really do much anymore, but if someone were to provide me with more leads, I like to help build a complete xml for the EVOX Roms.
Here is the original thread from OpenECU forums.
-It has the EVOX EDM Rom file for download
-Some map/xml? info that is incompatible with ECUFlash directly
-And the offsets we found today for the x and y axis summarized
Without further info I can't really do much anymore, but if someone were to provide me with more leads, I like to help build a complete xml for the EVOX Roms.
Jun 7, 2008, 04:48 AM
#37
The entry point on M32R is 0, other vectors at each &H10 bytes thereafter.
However, there appears to be a complex memory map or offset. It would be nice to identify the exact M32R it is. MH8102 doesn't help much which is the code on the face of some of CPU.
However, there appears to be a complex memory map or offset. It would be nice to identify the exact M32R it is. MH8102 doesn't help much which is the code on the face of some of CPU.
Jun 7, 2008, 05:05 AM
#38
Jun 7, 2008, 05:10 AM
#39
I assume you looked at the Renesas M32R webpage. The road map chart on the main page says there is only one processor that is a 1 MB ROM and is currently available. That would be the 32182. Perhaps that road map is older though and the 32192, 32196, and 32186 are now available?
for you guys figuring out the offsets
. subscribed!
