MicroSquirt.com read only forum (Jan.15,2018)

I have been having a lot of trouble with the VR input on my Miata and am trying to convert to the stock cam driven position sensor (CAS) that Miata uses. While trying to get it to work (with help for Matt Cramer and DIYAutoTune) I was jumping between the tachref .s19 and the microsquirt .s19 file. While doing that, I accidentally loaded an MS2/Extra .s19 file into one of the microsquirts I was testing. Now, when I load the microsquirt .s19 file, download v2 says it loaded and verified OK, but neither download or megatune can communicate with it. I assume the extra .s19 file messed up something the microsquirt .s19 file needs. Does anyone know is messed up and how (if?) it can be fixed?

Thanks,
Marty

I did some more checking and the unit is stuck in bootload mode. I can power up the unit with the bootload wire connected to ground, vref, or floating and download can load a .s19 file without error. I can also use the download verify function after a power cycle and the various .s19 code is getting loaded correctly. I have continuity between the bootload wire and pin 48 of the MCU. I also have +5v at pin 48 when the bootload wire is floating. Any suggestions about how to get out of bootload mode other than replacing the microsquirt? This is a Version 1 microsquirt.

I tried to talk to the unit with hyperterm. The unit seems to ignore any ascii characters until a cr. It then responds with 0xE0083E. After that any ascii characters including a cr get a response of 0xE1003E. I assume that is a response from bootload, so maybe that will mean something to someone who knows bootload.

Sounds like the processor is damaged. Not easily fixed, but I'll check if we can warranty it.