pcmhacking.net

Yeah, figures I'd be the first, I usually come up with things like this. LOL

I would appreciate the addition of bin support to the flash tool, as long as it's not too much work.

Otherwise I can do as suggested and copy the cal into the bin in a hex editor.

these questions are my fault LOL.i thought you couldnt seup flex tables in the bin without an nvram and the ecu plugged into flashtool my bad LOL

Six_Shooter wrote: Any idea if the NVSRAM from Moates would work the same as an NVRAM module?
https://www.moates.net/nvsram-module-ki ... l?cPath=64

I dont think so, because I think montecarslow took a different approach. Its been a while since I looked at his, but I think he mapped a small chunk of nvram (3k?) in to unused memory space, and then modified a bin to checksum the nvram, and on failure to copy the orignal tables back in to nvram as a backup option. Thus when you use that hardware the bin needs the code patches for his non-standard memory mapping. It is incompatible with our method where the whole memcal is nvram and the same xdf is used rom/nvram/emulator.

Six_Shooter wrote:I would appreciate the addition of bin support to the flash tool, as long as it's not too much work.

In terms of work its not much at all, it was only done to make future support easier for other custom bins that can use flex tables. But as its unlikely other bins will be released that can use flex outputs it can be changed to use both bin and cal and be left as a 12P only feature.

antus wrote:

Six_Shooter wrote: Any idea if the NVSRAM from Moates would work the same as an NVRAM module?
https://www.moates.net/nvsram-module-ki ... l?cPath=64

I dont think so, because I think montecarslow took a different approach. Its been a while since I looked at his, but I think he mapped a small chunk of nvram (3k?) in to unused memory space, and then modified a bin to checksum the nvram, and on failure to copy the orignal tables back in to nvram as a backup option. Thus when you use that hardware the bin needs the code patches for his non-standard memory mapping. It is incompatible with our method where the whole memcal is nvram and the same xdf is used rom/nvram/emulator.

Ok. I knew there was something he did differently that requires a patch to the bin to enable the NVSRAM upload to work, just wasn't aware that it would be different from how yours works.

Thanks

VL400 wrote:

Six_Shooter wrote:I would appreciate the addition of bin support to the flash tool, as long as it's not too much work.

In terms of work its not much at all, it was only done to make future support easier for other custom bins that can use flex tables. But as its unlikely other bins will be released that can use flex outputs it can be changed to use both bin and cal and be left as a 12P only feature.

Sweet.

Coding is not one of my strong points, though I do NEED to get better at it, since I am in school currently to go into the electronics industry. It's all of the subtle nuances that get me. I am always appreciative of when someone can add or modify code to do something new, or change function, since it's a whole different language and way of thinking.

antus wrote:

Six_Shooter wrote: Any idea if the NVSRAM from Moates would work the same as an NVRAM module?
https://www.moates.net/nvsram-module-ki ... l?cPath=64

I dont think so, because I think montecarslow took a different approach. Its been a while since I looked at his, but I think he mapped a small chunk of nvram (3k?) in to unused memory space, and then modified a bin to checksum the nvram, and on failure to copy the orignal tables back in to nvram as a backup option. Thus when you use that hardware the bin needs the code patches for his non-standard memory mapping. It is incompatible with our method where the whole memcal is nvram and the same xdf is used rom/nvram/emulator.

It doesn't work with the Autoprom either, I was so disappointed that I couldn't run the wideband VE learn...

I've never used the Flashtool since I have the Autoprom and the hardware is directly supported by Tunerpro, you just upload it straight into the Autoprom memory (and real time emulate if you like). Doesn't this work for the Ostrich?

I don't care about the VE learn or any auto tuning for that matter.

Yes, the bin themselves will work with the Ostrich, it is just a bin afterall. I was see if the NVSRAM would work with $12P, more out of curiosity than anything else.

I want to be able to set up the flex tables easily, it sounds like the flashtool will be modified to make this easy for other people without an NVRAM.

Ah sorry brain fade, I'm mixing up two different things. For some reason I had the idea you were referring to the emulation memory in the Ostrich... disregard

Have sent six shooter an updated flashtool to test, so providing no issues will be available soon