I get that same error and my boot log file shows the same 0xff from my smec.
84Omni , post up your log file
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
-BootSerial routine-(Called from StdBinWrite)
Using Boot Program MPTune Smec/Sbec Bootloader ver2040
got ecu acknowledgement byte - 0 at 23:00:50.6265181
total bytes returned on switch-on were 1
boot download routine is started.
boot baudrate = 7812
hi speed rate = 62500
sent FF byte
got return byte after sending 0xff of - FF
total bytes returned after sending 0xff were 1
sending boot program. length = 256
Boot send start time 23:00:52.6389217
Boot send finish time 23:00:52.8729221
Boot reread finish time 23:00:53.2161227
done sending boot program. bytes returned = 0
read timeout set to 328
bytes returned were:
everything is done
To me, that looks like its not bootstrapping. Normal DRB coms always echo back the command.
84omni , smec or sbec?
Rob, I assume the ftdi cables have the TTL inverted option set?
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
Its a SMEC and the fuel pump doesn't prime when I turn the key on so I assume its boot straping.
I am on SBEC... on one of Rob's modules I soldered to the board... So don't entirely rule out a screwup on my part... But I did double check with continuity test ect.. and all seems well.. and van will start..
Here is the cable I am using... I bought it some time ago... but out of the package for the first time on this project.
Last edited by ShelGame; 10-06-2013 at 11:11 PM.
Heck I can just buy a new one..... If this one works with a SMEC I can keep it for that... Or send it back if ya want it...... No big deal either way..
(don't see an option to purchase one on your site currently though)
As long as it still registers with the PC when you plug it in, then it should work with the SMEC still.
I took them down because I ran out of boards and had to order more. But, they'll be here on Wed now, so I'll put them back up. Actually, these will be 'Series 3' and I'll probably offer them for sale (optionally) without a cable for those that want to use their own cable.
Last edited by ShelGame; 10-07-2013 at 12:57 PM.
Order up!
So I know this is long over due and 3+years later but life got in the way and I've finally got my car back on the road and would like to make my flashable smec work. I'm have the same issues as the previous posters were having. I'm wondering if any of them have found a fix for it.
Check out the MPTune and MPScan sticky threads, the first posts for setup. Try that and see if it can get you up and running as far as cable communication.
Some have been late to the party, so you could look through the last few pages in those threads to see if you can find the latest help tidbits.
Then let us know what you encounter and we can try to help.
Wayne H.
'91 Dodge Spirit ES 2.5L turbo 5spd
'05 PT GT 2.4T HO autostick (RIP)
'89 Plymouth Acclaim 2.5L turbo auto, "Slugmobile" yes, THE Slugmobile!
'89 Dodge Caravan SE 2.5L turbo auto, "Mean Mini" yes, Gus' Mean Mini! (Current best 11.699 @ 114.43 mph! - Oct 15th, 2022 Cecil County Dragway, MD)
MeanMini dragracing videos: https://www.youtube.com/playlist?lis...URZLB1RxGYF6vw
and other cars, trucks and motorcycles
https://www.youtube.com/user/SlugmobileMeanMini
I went through that process and it looks as though everything checks out. I will check it again and take a screen shot and post the pics and let you all see if I'm missing anything. I also have screen shots of the prompts that come up when it fails to connect that I can post. also the cord I bought from boost button has a red wire that comes from the board that doesn't go anywhere, any idea what that's all about?
If you are using on a smec, disregard that pigtail wire. That is for SBEC.
You said you have a flashable SMEC, right? You do need to add a wire in your ecu harness for the bootstrap signal. Did you see that in the setup instructions.
What operating system on your pc? I've got mine working with Win10, and have used Win7 and XP.
With the proper drivers, it should find your cable.
Wayne H.
'91 Dodge Spirit ES 2.5L turbo 5spd
'05 PT GT 2.4T HO autostick (RIP)
'89 Plymouth Acclaim 2.5L turbo auto, "Slugmobile" yes, THE Slugmobile!
'89 Dodge Caravan SE 2.5L turbo auto, "Mean Mini" yes, Gus' Mean Mini! (Current best 11.699 @ 114.43 mph! - Oct 15th, 2022 Cecil County Dragway, MD)
MeanMini dragracing videos: https://www.youtube.com/playlist?lis...URZLB1RxGYF6vw
and other cars, trucks and motorcycles
https://www.youtube.com/user/SlugmobileMeanMini
-make sure you have followed the directions to make sure the ftdi cable rx/tx signals are set up to be inverted.
-allow mptune to auto update so you know you are working with the latest version
-confirm that your com port is set up correctly and recognized by mptune. it should show the connection on the status bar at the bottom left of the window.
-if you still have problems post up the mpt2coms.txt file located in the mptune directory in your documents folder.
89 Voyager LE, 2.5T2 - rest in peace
87 Charger Shelby T2 (2.4 conversion in process)
So 84omni is my brother and to fix his issue we had to click the LoadVCP box. If you go to the MPtune wiki under the Setup the USB to SCI cable and follow the directions:
http://www.boostbutton.com/turbonato...id=cable_setup
Yes I bought the flashable SMEC and the FTDI cable from Boost Button back in 2012. I have the bootstrap hooked up as per Rob's directions directly to the battery ( I double checked it was in the correct location the other night )
I'm running Window's 10, I just went through the device manager and everything is up to date and it recognizes the cable.
Ok so I went through the instructions and checked everything, I think I have the setting right but I'll post the screen shots just in case I missed anything
these are the prompt messages I'm getting,
This is the log
-BootSerial routine-(Called from LoadBoot)
Using Boot Program Modular BootLoader for MP Tune - BootMainAll
total bytes returned on switch-on were 1 at 19:26:39.4767902
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 1
return byte 1: FF
sending boot program. length = 256
Boot send start time 19:26:41.4924870
Boot send finish time 19:26:41.7268137
Boot reread finish time 19:26:43.3674713
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 write chip because boot program is not running properly
------------------
Last edited by motorhead153; 06-15-2017 at 11:06 PM.