-
MPTune issue, using flashable SBEC
I've been working on this for more hours than I would like to admit... hoping I could resolve it without having to post. I have also spent quite a bit of time talking and messaging with my brother, who has experience flashing SMECs often, and no luck. So on with the posting-
Hoping to not overwrite this, I'm going to start by throwing out the ingredients I've been working with:
-Flashable SBEC#1 (done by Rob a long time ago, has his cal pre-loaded, runs when installed)
-Flashable SBEC#2 (one of the last done by Rob, no cal pre-loaded)
-BoostButton cable (older version- has the 2010 board)
-BoostButton cable (also one of the last, 2013 board Rev.3)
Two functioning SBEC Turbo harnesses:
- 1991 that doesn't have any known issues, runs a 2.2 8 valve, manual
- 1991 2.5TI, hasn't been thoroughly tested, runs a 2.5 8 valve/manual
Windows 10 laptop
Windows xp laptop
Me: less hair and higher blood pressure than when I started
Both cables pass the com test. Both cables can trigger actuator tests through MPScan.
I have attempted flashing to SBEC#2 in both vehicles. I'm have a jumper wire to send 12V to the bootstrap wire of the cables and I release the contact after a second. I get a variety of errors: "unable to download entire boot program for serial coms", some messages showing bytes received, sometimes something like "bootstrap program corrupted".
I try to read the cal on SBEC#1 with the same communication errors.
I'm starting to think more that there is something wrong with the program itself. There are times after a few errors, I will click on the flash button and it goes directly to a "write error" message without even showing the prompt to prepare to boot power the chip. It is doing this on both laptops. So far I have only tested the XP laptop on the 2.2 vehicle.
This is driving me nuts! Any help will be greatly appreciated.
Here is that last com log I had from the Windows 10 laptop
*****************
-Comport analysis for mptune version 2.0.6.2
-Locating ports on computer-
name:USB Serial Port (COM3) deviceid:FTDIBUS\VID_0403+PID_6001+BB1NSB9AA\0000
number of ftdi devices found - 1
ftdi port num:COM3 serial num:BB1NSB9A
Inverted tx:True Inverted rx:True
Vcp driver loaded:True
Latency is set to:16
checking to see if usb port number COM3 is a moates device
Moates device not located on this port
default com port set to:COM3
*********************
It sets the latency itself at 16. I have also attempted setting it at 2 with the same results.
-
Re: MPTune issue, using flashable SBEC
I forgot to add- When working with SBEC#1 (that has a cal) the fuel pump isn't coming on when I'm attempting to bootstrap, which should mean I'm doing it right.
-
Re: MPTune issue, using flashable SBEC
Sounds to me like you're just holding the button too long. Release the boot button as you key-on; like in one motion. Don't hold it for a second after key-on. If you do, it will interrupt the communications.
-
Re: MPTune issue, using flashable SBEC
Thanks for the suggestion, Rob. I have tried to vary the time that I kept the 12V signal on. I had finally located a momentary push button to use before posting and had the same results. It might be a few days before I have time to try it more. I'll work on my timing.
-
Re: MPTune issue, using flashable SBEC
Last night I made more attempts, trying to be quicker with the 12v signal button. Same results. I feel that I'm thoroughly living the definition of "insanity", yet I keep trying.
I don't think and issue with the program can be ruled out, even though I realize that I can't rule out my laptop setup. The reason I'm curious on the program is due to what seems to be inconsistent behavior. Like- I make an attempt to write the chip. I get the prompt to confirm the flashable module, I get the bootstrap prompt, then I get a write error after the attempt followed by the verification error. When I go right back to "write chip" MPTune goes direct to the write error without even showing the flash module confirmation or the bootstrap prompt. I took a video of an example last night. I starts out of focus as I'm trying to my phone under my chin. I click enter at the bootstrap prompt, work the button and key, then get the write error.
https://youtu.be/G_VgsSOG01Q
Similar bypass of the bootstrap prompt also happen after trying other functions like "read chip" or "chip ID"
I also heard from someone else who had issues trying to flash with their laptop on battery power and it ended up working correctly when plugging it in on full power. I have only used my Windows 10 laptop on battery power so far for these attempts. The XP one I tried was on the AC adapter.
-
Re: MPTune issue, using flashable SBEC
in setup/program settings, set the "log ftdi port activity" to true and save the settings. then try it again and post up the mpt2boot.txt and mpt2coms.txt files that are created in the mptune directory under your "Documents" folder.
-
Re: MPTune issue, using flashable SBEC
Quote:
Originally Posted by
wowzer
in setup/program settings, set the "log ftdi port activity" to true and save the settings. then try it again and post up the mpt2boot.txt and mpt2coms.txt files that are created in the mptune directory under your "Documents" folder.
Thanks, will do as soon as I can!
-
Re: MPTune issue, using flashable SBEC
The following are logs from trying to read the flashable SBEC that has a cal installed that can run the vehicle
**********
-BootSerial routine-(Called from LoadBoot)
Using Boot Program Modular BootLoader for MP Tune - BootMainAll
total bytes returned on switch-on were 1 at 03:59:12.3804996
return byte 1: 0
boot download routine is started.
boot baudrate = 7812
hi speed rate = 62500
sent FF byte
total bytes returned after sending 0xff were 2
return byte 1: 0
return byte 2: FF
sending boot program. length = 256
Boot send start time 03:59:14.4016007
Boot send finish time 03:59:14.6292557
Boot reread finish time 03:59:16.2698793
done sending boot program. bytes returned = 0
read timeout set to 1640
bytes returned were:
baud:7812 bytes received:0
Boot downloaded failed due to not all bytes being echoed back for confirmation
------------------
Can't read chip because boot program is not running properly
------------------
-Comport analysis for mptune version 2.0.6.2
-Locating ports on computer-
name:USB Serial Port (COM3) deviceid:FTDIBUS\VID_0403+PID_6001+BB1NSB9AA\0000
number of ftdi devices found - 1
ftdi port num:COM3 serial num:BB1NSB9A
Inverted tx:True Inverted rx:True
Vcp driver loaded:True
Latency is set to:2
checking to see if usb port number COM3 is a moates device
Moates device not located on this port
default com port set to:COM3
-
Re: MPTune issue, using flashable SBEC
The following are logs from attempting to flash the SBEC that doesn't have a cal loaded. The resulted in a chip write failure prompt:
********
-BootSerial routine-(Called from LoadBoot)
Using Boot Program Modular BootLoader for MP Tune - BootMainAll
total bytes returned on switch-on were 1 at 04:11:30.2399671
return byte 1: 0
boot download routine is started.
boot baudrate = 7812
hi speed rate = 62500
sent FF byte
total bytes returned after sending 0xff were 2
return byte 1: 0
return byte 2: FF
sending boot program. length = 256
Boot send start time 04:11:32.2514476
Boot send finish time 04:11:32.4923919
Boot reread finish time 04:11:32.5705405
done sending boot program. bytes returned = 255
read timeout set to 1640
bytes returned were:
8E 00 FF CE 10 00 CC 01 0C A7 2B E7 2D 0F CC 60 01 A7 3C E7 3F 8D 1F 17 8D 1C DD EE 8F 8D 17 17 8D 14 E7 00 F6 10 2E 2A FB E6 00 F7 10 2F 08 4A 26 EE DE EE 6E 00 36 FC 10 2E 85 20 27 F9 32 39 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
boot program loaded and baud rate is now set to 62500
opening file smec_flash_bb.lst
Program byte count = 104. Actual count = 108
Bytes sent were:
00 80 6C CE 80 00 3C CE 00 40 FC 10 2E 85 20 27 F9 E7 00 08 8C 00 80 26 F1 17 8D 38 C6 C8 8D 3D 18 CE 00 40 38 8D 3A 18 A6 00 A7 00 18 08 08 18 8C 00 80 26 F2 09 8D 11 08 8C B6 00 26 03 CE B8 00 8C 00 00 26 C0 7E 00 00 E6 00 36 84 80 C4 80 11 32 26 F5 36 FC 10 2E 32 B7 10 2F 39 5A 26 FD 39 CC AA A0 B7 D5 55 44 B7 AA AA F7 D5 55 39
Program smec_flash_bb.lst successfully sent to master program (0)
waited up to 1050 milliseconds.
Program smec_flash_bb.lst was not downloaded correctly. Only 90 were returned (1051)
-Comport analysis for mptune version 2.0.6.2
-Locating ports on computer-
name:USB Serial Port (COM3) deviceid:FTDIBUS\VID_0403+PID_6001+BB1NSB9AA\0000
number of ftdi devices found - 1
ftdi port num:COM3 serial num:BB1NSB9A
Inverted tx:True Inverted rx:True
Vcp driver loaded:True
Latency is set to:2
checking to see if usb port number COM3 is a moates device
Moates device not located on this port
default com port set to:COM3
-
Re: MPTune issue, using flashable SBEC
This is after trying to burn again, a few times, getting the BB flash module confirmation prompt, then going straight to a write error without the bootstrap prompt:
*******
-BootSerial routine-(Called from LoadBoot)
Using Boot Program Modular BootLoader for MP Tune - BootMainAll
total bytes returned on switch-on were 1 at 04:11:30.2399671
return byte 1: 0
boot download routine is started.
boot baudrate = 7812
hi speed rate = 62500
sent FF byte
total bytes returned after sending 0xff were 2
return byte 1: 0
return byte 2: FF
sending boot program. length = 256
Boot send start time 04:11:32.2514476
Boot send finish time 04:11:32.4923919
Boot reread finish time 04:11:32.5705405
done sending boot program. bytes returned = 255
read timeout set to 1640
bytes returned were:
8E 00 FF CE 10 00 CC 01 0C A7 2B E7 2D 0F CC 60 01 A7 3C E7 3F 8D 1F 17 8D 1C DD EE 8F 8D 17 17 8D 14 E7 00 F6 10 2E 2A FB E6 00 F7 10 2F 08 4A 26 EE DE EE 6E 00 36 FC 10 2E 85 20 27 F9 32 39 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
boot program loaded and baud rate is now set to 62500
opening file smec_flash_bb.lst
Program byte count = 104. Actual count = 108
Bytes sent were:
00 80 6C CE 80 00 3C CE 00 40 FC 10 2E 85 20 27 F9 E7 00 08 8C 00 80 26 F1 17 8D 38 C6 C8 8D 3D 18 CE 00 40 38 8D 3A 18 A6 00 A7 00 18 08 08 18 8C 00 80 26 F2 09 8D 11 08 8C B6 00 26 03 CE B8 00 8C 00 00 26 C0 7E 00 00 E6 00 36 84 80 C4 80 11 32 26 F5 36 FC 10 2E 32 B7 10 2F 39 5A 26 FD 39 CC AA A0 B7 D5 55 44 B7 AA AA F7 D5 55 39
Program smec_flash_bb.lst successfully sent to master program (0)
waited up to 1050 milliseconds.
Program smec_flash_bb.lst was not downloaded correctly. Only 90 were returned (1051)
------------------
opening file smec_flash_bb.lst
Program byte count = 104. Actual count = 108
Bytes sent were:
00 80 6C CE 80 00 3C CE 00 40 FC 10 2E 85 20 27 F9 E7 00 08 8C 00 80 26 F1 17 8D 38 C6 C8 8D 3D 18 CE 00 40 38 8D 3A 18 A6 00 A7 00 18 08 08 18 8C 00 80 26 F2 09 8D 11 08 8C B6 00 26 03 CE B8 00 8C 00 00 26 C0 7E 00 00 E6 00 36 84 80 C4 80 11 32 26 F5 36 FC 10 2E 32 B7 10 2F 39 5A 26 FD 39 CC AA A0 B7 D5 55 44 B7 AA AA F7 D5 55 39
Program smec_flash_bb.lst successfully sent to master program (1)
waited up to 1051 milliseconds.
Program smec_flash_bb.lst was not downloaded correctly. Only 91 were returned (1052)
------------------
opening file smec_flash_bb.lst
Program byte count = 104. Actual count = 108
Bytes sent were:
00 80 6C CE 80 00 3C CE 00 40 FC 10 2E 85 20 27 F9 E7 00 08 8C 00 80 26 F1 17 8D 38 C6 C8 8D 3D 18 CE 00 40 38 8D 3A 18 A6 00 A7 00 18 08 08 18 8C 00 80 26 F2 09 8D 11 08 8C B6 00 26 03 CE B8 00 8C 00 00 26 C0 7E 00 00 E6 00 36 84 80 C4 80 11 32 26 F5 36 FC 10 2E 32 B7 10 2F 39 5A 26 FD 39 CC AA A0 B7 D5 55 44 B7 AA AA F7 D5 55 39
Program smec_flash_bb.lst successfully sent to master program (0)
waited up to 1050 milliseconds.
Program smec_flash_bb.lst was not downloaded correctly. Only 91 were returned (1051)
------------------
opening file smec_flash_bb.lst
Program byte count = 104. Actual count = 108
Bytes sent were:
00 80 6C CE 80 00 3C CE 00 40 FC 10 2E 85 20 27 F9 E7 00 08 8C 00 80 26 F1 17 8D 38 C6 C8 8D 3D 18 CE 00 40 38 8D 3A 18 A6 00 A7 00 18 08 08 18 8C 00 80 26 F2 09 8D 11 08 8C B6 00 26 03 CE B8 00 8C 00 00 26 C0 7E 00 00 E6 00 36 84 80 C4 80 11 32 26 F5 36 FC 10 2E 32 B7 10 2F 39 5A 26 FD 39 CC AA A0 B7 D5 55 44 B7 AA AA F7 D5 55 39
Program smec_flash_bb.lst successfully sent to master program (0)
waited up to 1050 milliseconds.
Program smec_flash_bb.lst was not downloaded correctly. Only 91 were returned (1051)
------------------
opening file smec_flash_bb.lst
Program byte count = 104. Actual count = 108
Bytes sent were:
00 80 6C CE 80 00 3C CE 00 40 FC 10 2E 85 20 27 F9 E7 00 08 8C 00 80 26 F1 17 8D 38 C6 C8 8D 3D 18 CE 00 40 38 8D 3A 18 A6 00 A7 00 18 08 08 18 8C 00 80 26 F2 09 8D 11 08 8C B6 00 26 03 CE B8 00 8C 00 00 26 C0 7E 00 00 E6 00 36 84 80 C4 80 11 32 26 F5 36 FC 10 2E 32 B7 10 2F 39 5A 26 FD 39 CC AA A0 B7 D5 55 44 B7 AA AA F7 D5 55 39
Program smec_flash_bb.lst successfully sent to master program (0)
waited up to 1050 milliseconds.
Program smec_flash_bb.lst was not downloaded correctly. Only 91 were returned (1051)
------------------
- - - Updated - - -
another burn attempt after unplugging and plugging in the usb cable:
******
-BootSerial routine-(Called from LoadBoot)
Using Boot Program Modular BootLoader for MP Tune - BootMainAll
total bytes returned on switch-on were 1 at 04:20:57.2508782
return byte 1: 0
boot download routine is started.
boot baudrate = 7812
hi speed rate = 62500
sent FF byte
total bytes returned after sending 0xff were 2
return byte 1: 0
return byte 2: FF
sending boot program. length = 256
Boot send start time 04:20:59.2634793
Boot send finish time 04:20:59.4910588
Boot reread finish time 04:20:59.5848337
done sending boot program. bytes returned = 256
read timeout set to 1640
bytes returned were:
8E 00 FF CE 10 00 CC 01 0C A7 2B E7 2D 0F CC 60 01 A7 3C E7 3F 8D 1F 17 8D 1C DD EE 8F 8D 17 17 8D 14 E7 00 F6 10 2E 2A FB E6 00 F7 10 2F 08 4A 26 EE DE EE 6E 00 36 FC 10 2E 85 20 27 F9 32 39 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF
boot program loaded and baud rate is now set to 62500
opening file smec_flash_bb.lst
Program byte count = 104. Actual count = 108
Bytes sent were:
00 80 6C CE 80 00 3C CE 00 40 FC 10 2E 85 20 27 F9 E7 00 08 8C 00 80 26 F1 17 8D 38 C6 C8 8D 3D 18 CE 00 40 38 8D 3A 18 A6 00 A7 00 18 08 08 18 8C 00 80 26 F2 09 8D 11 08 8C B6 00 26 03 CE B8 00 8C 00 00 26 C0 7E 00 00 E6 00 36 84 80 C4 80 11 32 26 F5 36 FC 10 2E 32 B7 10 2F 39 5A 26 FD 39 CC AA A0 B7 D5 55 44 B7 AA AA F7 D5 55 39
Program smec_flash_bb.lst successfully sent to master program (0)
waited up to 1050 milliseconds.
Program smec_flash_bb.lst was not downloaded correctly. Only 90 were returned (1051)
-
Re: MPTune issue, using flashable SBEC
Those were with the AC adapter hooked up. Tried after them on battery power and it didn't look much different.
-
Re: MPTune issue, using flashable SBEC
That's interesting.
I'm sure Morris will have some suggestions.
-
Re: MPTune issue, using flashable SBEC
I found mine would error if I released the power too quick (momentary button also). I get it set up so that I can hit the enter button to enter flash mode, push the button, turn the key on, count to 2 and release the button. Works pretty much every time.
-
Re: MPTune issue, using flashable SBEC
Currently traveling but it looks like the boot loader program download ok but the flashing definitely bombs. Weird. Have you tried scanning with mpscan. This would confirm the cable connection works.
-
Re: MPTune issue, using flashable SBEC
Quote:
Originally Posted by
wowzer
Currently traveling but it looks like the boot loader program download ok but the flashing definitely bombs. Weird. Have you tried scanning with mpscan. This would confirm the cable connection works.
I've previously tried actuator tests in MP SCAN with both cables and it worked... can't think now if I've done it with all the SBECs. I know they definitely triggered with a stock 91 2.5T1 SBEC.
Last night (well, early morning) I tried MPScan with the flashable SBEC that runs the vehicle and actuator tests didn't work.
I previously tried MPScan with the same SBEC and didn't see live data on my dashboard gauge layout.
Are there logs in MPScan that I should post? I won't be able to run the vehicle for testing until normal people hours tomorrow and I'm away from my laptop right now.
If it is any kind of helpful clue, my OTC 4000E works on both vehicles.
-
Re: MPTune issue, using flashable SBEC
Just set up a simple layout with rpm and tps and see if that works.
-
Re: MPTune issue, using flashable SBEC
So think maybe I can add some info to this. Today I spent all day at a friends trying to flash his 89 CSX. Rob LLoyd this might sound familiar because they've been talking to you. So they have a used BB flashable SBEC. We wired up a pushbutton setup. Loading up the bin files that Rob L sent or opening a turbonator cal and compiling it and then trying to upload the created bin file resulted in a fail to upload.
I did that correctly right? mod the TPL file, then compile and upload the bin??? Been a few years since I've messed with any of this stuff.
So we then thought since the car runs on the 91 2.5 cal that the OTC 4000E scanner was saying was on the flashable SBEC we wondered if we could read the cal off the ECU. BAM! MPtune reads and saves the cal just fine. We could then upload that Bin file back to the ECU without any issues. But modifed bins or the bins than rob sent us where a no go.
So not sure what's going on but that's what is happening here with our MP tune. Would like to get it figured out.
Thanks and hope it maybe helps.
-
Re: MPTune issue, using flashable SBEC
Something is different there Jay.
Dan mentioned he can't read the bin off the sbec that does run the car.
But, your situation is weird. And you are set for SBEC, and the cal you are trying to flash is for sbec?
-
Re: MPTune issue, using flashable SBEC
Wayne when you say set for SBEC Where is that? Is under Setup/program settings/ECU???? We have it set to the BB Flash Module now as I thought that "SBEC2" would be the later SBEC's.
I think this is right as if it wasn't would it not be able to read a cal off the ECU then flash that cal back to the ECU???
We were more successful turning the key to on and releasing the push button then hitting "Ok" on the screen. Well more like one person would turn the key to on and release the button and I would hit Ok as I heard the key click into the On position from outside the car.
-
Re: MPTune issue, using flashable SBEC
Under Setup/Com Port/Settings
I don't have my cable with me, so i can't open that window since it gives me a popup alert for no valid ports.
Maybe that is just in MPScan where you define the module in that settings tab.
If the timing of all that with the key and letting go of the momentary button is that narrow, that is kind of crappy. I wonder if Morris could program another prompt to let go of the momentary switch before it proceeds.
You are at least in a little better situation than Dan, as you were at least able to read the one bin.
Can you post up your same com logs and error txt?