Anybody know what this is?

[yoda69]

I tried to read this of a Kalmaker memcal, but it doesn't appear to be reading correctly, or I can't identify it anyway.

original5.bin

(16 KiB) Downloaded 379 times

It's running on an 808 and all appears to be OK and the vehicle is running with only DTC 43 set as it is not fitted with a knock sensor, but the memcal is and it's obviously turned on in the bin.
It's a retrofit VN 5.0 Litre in a kingswood, with mild mods, extractors & cam.

In the past I've had no problems reading kalmaker bins straight of the memcal, but in this case doesn't make sense.
I've had a look using TP5 2D viewer and tables and such appear to be there.

Anybody got any ideas what I'm doing wrong or what this file is, I can't find any copyright info in Hex Editor?

Thanks,
yoda69

[Doctor Bob]

it looks like it starts at $200 & is $FB based, although the broadcast code is the same a BDJH, so if you burn this file it runs ok?
other than that i cant see much else useful

Rob

[yoda69]

Didn't have any luck copying it and getting it to run, that's why I though it may have lines crossed somewhere until memcal powered up by ECU, but then thought it strange that when viewing in Hex Editor a lot of stuff looked liked tables.

Tried reading from memcal and then removing chip and reading that, got the same file both times.
Was going to try the Flashtool to read from ECU (using a 16183082 with high speed Baud), but vehicle only has the VN 160 Baud connector so would have had to also wire in an OBDII style connector and hook up to ECU.

Any suggestions welcome.

Thanks,
yoda69

[Doctor Bob]

does it have any other stuff under the eprom?

[antus]

Its a good read, it disassembles OK.. All I could see at a glace is the same as you guys, $FB based 16k rom.

[yoda69]

Has a kalmaker PAL under the EPROM.
Was hoping to just read and do a quick play with the idle settings as the rest of tune is apparently OK.
At this stage comapring to $FB BAAP tune and trying to move stuff around to line up and identify what has changed.
Plan to get a base $FB running, and then when time permits move over to $12P.
Have lined up about 75% at this stage, so will continue on and see how I go.
Thought it may be early Kalmaker or COME but couldn't see any identifiers or hints in the bin text.

Thanks,.
yoda69

[antus]

Our posts crossed paths, I see you have pretty much id'd it as early kalmaker.. but i'll post this anyway:

So I have dug a little deeper. All the factory bins have some data just below the defined reset vectors at the end of the bin. Im not sure what its used for - I suspect nothing in production use, and that extra data is missing (which makes it look like non-factory code). Then I checked the power on code.. Its different, with the first obvious change being this addition:

ROM:D073 clr byte_C113 ; Clear
ROM:D076 ldaa byte_C113 ; Load accumulator from memory
ROM:D079 dec byte_C113 ; Decrement
ROM:D07C cmpa byte_C113 ; Compare accumulator with memory
ROM:D07F beq loc_D084 ; Branch if equal
ROM:D081 bset byte_35 $10 ; Set bit in memory

Which looks like trys to write to address 0xC113 and check if the value was changed, and set a bit in ram at 0x35 if the write was successfull. This is testing to see if its running on nvram.

[antus]

Program code gets a 100% match on Street Pro 2 N00

[yoda69]

Thanks guys,
Spent some of last night and today pulling the data apart and lining up with a standard $FB bin, then went through a $FB XDF and changed all the matching addresses to suit.
So here is a near complete SP2 XDF.

Kalmaker N00 - FB.zip

(11 KiB) Downloaded 378 times

Important things to note:
1. I did not create the $FB file this XDF was created from, so terminology/naming is what was there, along with any carryover errors.
2. Only names starting witn N00- are SP2, all others are standard $FB and not used in SP2 or I couldn't identify them.
3. No checksum is calculated, as such any mod'd SP2 bins won't work. I did this as more of a tool for porting SP2 tunes to $12P

Any questions let me know.

Thanks,
yoda69