Nistune Forums

by the way the STK11C88s dont do AUTOSTORE on powerdown so the above issue shouldn't be a problem, however i have noticed there has been corruption sometimes on powerup, which the resistor modifications will fix

ahah that explains why my willem wasn't working properly. its because when you load a 16K image it thinks when it programs to do 16K even when you do a copy/paste although in the buffer and it looks like 32K.... its still internally 16K and burns that size. its a bug with the programmer. not suprisi...

spent just about the whole day doing protection code for the NVRAM seems to work fine now

also updated nistune messages. should have something out soon

need to get that innovate working still also

usb-serial chips and their drivers are notorious for not working as expected. this is a manufactuer driver issue which doesn't support this windows function properly cheap nasty serial converters from ebay may not even stream consult properly. a belkin one i got previously was returned becuase it lo...

also DIP versions (what you currently have) are being phased out by Simtek. All future boards will use SMD based 11C88 chips. I have three tubes of these devices now, just waiting for boards to arrive in a few weeks

try programming the chip blank and then readback. it should be blank. then you can try the 32K rom image afterwards. i currently use 1000uf but i think it was something like 470uf or greater the STK11C88s do not keep any corruption at all. will not be using STK15C88s in the future because of these c...

well this one is getting fun. i made a FTDI RS232-USB adaptor today. works good with consult and romulator from nistune... and i thought this is what blazt was using but nope.... they use the CP2101 USB-UART chip which has different drivers again. and these drivers have some kind of bug since even t...

i will be doing some updates tonight to prevent writing to wrong areas of NVRAM to avoid corruption

i will also need to update the Romulator upload sequence to prevent the ECU from running when powered during an upload by clearing the interrupt vector tables first

the NVRAM Programming guide on the website details that you need to program 4000-7FFF

this means using

copy /b image.bin + image.bin image_32k.bin

to make a double size image which then you load into the NVRAM. the bottom half is not used by the NIStune board for rev2 hardware versions

hi dino At my first shutdown it was not possible any more to connect to nistune for consult mode, checksum error, if i remember correctly. The car was not starting any more. When i turned ign on, fuel pump was going permanently. Engine was not starting. AFM was damaged. checksum error generally mean...

on another note i can cause some pretty nasty corruption by writing to the vector table in the hex editor (7ff0-7fff). this seems to make the ecu run nuts as expected, but the problem is that the STK15C88 is also autostoring the corrupted details i dont know if this problem is related but the existi...

this is the pre-release rev3 witihout address bounds checking file i am using. i will start adding the bounds checking soon

will only work with the innovate test releases of nistune (0.96)

I have the Nistune board installed in my car permanently and have been running data logging etc a daily basis with no problems but noting this, I am using the NVRAM configuration which makes things slightly different. I also have the board hotglued to the ECU to prevent vibration issues. Any vibrati...

I've started looking at this issue last night. I swear cos of winter over hear its like zero degrees in my shed whilst trying to debug this issue! both of you have said that it keeps changing address 0x2000 to 00 but i can't seem to get this repeated here yet :cry: I cant get 79h(the correct value) ...

i'll see if i can work around this one in the meantime. only appears to be the blatz units so far, i am using a homebuilt unit and other people using the serial PLMS unit with several types of ecus