If you use m32176F4 .. you get only a partial decode .. if it's m32196 .. then probably that's the reason we can't get a full decoding ..

&h50000 seems to be the start of the data code ..
&h55000 seems to be the start of the 2D and 3D tables ..

It is very similar to the SH2 processor code .. problem is if we need to continue further .. the processor must be known and if the current disassembler can support the chipset ..

 

Yep, jcsbanks and I both did that. I went in and searched out some sections of code that were not auto-disassembled when starting at the entry point, and found that there are occasional word-length hex values that cannot be auto-disassembled using any of the available M32R processor variants. The m32196 product description suggests it uses an expanded M32R language. I think that is the problem we are having, but I also cannot find a software manual for the m32196 to confirm. There is no listing on the m32196 product pages.

 

can someone give me a quick explanation of the difference from a 2D table to 3D? i mean i know the literal difference but im saying in conjunction with ecuflash?...i never messed with assembly language ive only ever programmed in C++ and VB (highschool lol) so i understand whats going on but not completely...sorry for off topic question

 

2D = data vs one independent variable, e.g., baseline WGDC vs RPM.

3D = data vs two independent variables, e.g., fuel or timing tables.

 

so in your example fuel for instance the variables are rpm, load, and target AFR in the table? im sorry im just trying to understand this a little better

the data would be where in-between those 2 variables the car is actually at?

 

In a fuel table, RPM and load are the independent variables. AFR is the dependent variable that gets adjusted.

The axes' values (in this example, the RPM and load values) are stored in a different location in the ROM than where the AFR values are stored. Not sure if that answers your question. I'm a bit confused as to what you are asking.

 

Why oh why did I look into this thread. Looking at X prices now

Awesome work guys.

 

nope you answered it perfect MRFred thank you i completely understand it now

 

just read the whole thread.... GOOD JOB GUYS! this is friggin awesome.

If i could understand hex and binary... id be trying to help dissasemble. Ill stick to what i know...tuning cars with available tables .

definately getting the 2.0 cable when it comes out.

subscribed.

 

how we doin?

 

We have the code disasssembling without errors.

I've not had any time to do any more on it, too busy with house renovation.

 

Have any volunteers wanting to take a trip to the UK to help Banks finish his renovations?

 

We've got the same disassembly base code, but I'm in a similar situation (baby instead of house). I probably won't do much with the X stuff until I get flex fuel working on the IX. Colby has the same disassembly base code, so hopefully he will take some time to seek out the main tables.

 

Funny because i'm in the middle of doing renovations AND we just had a baby 5 days ago! But i'm no help anyway with this code disassembling. I'd do better with an etch a sketch

 

Congratulations, and you have your hands full!