Flashable SMEC procedure and settings

[player1up]

Bear with me for a sec as I'm a bit of a newb.
I've recently picked up a flashable SMEC with RS232 cable ( not USB ).

I'm getting the ECU bootstrapped ( no fuel pump kick ) but the error I'm getting on the PC is:

Unable to download entire boot program from serial coms.

I've tried every which way that I can think of more than once..
Here are the processes I've tried to read it.

Click read, click ok, switch pin 11 on, turn key on, switch pin 11 off.
Click read, click ok, switch pin 11 on, turn key on

I'm running a jumper wire straight from the battery with an inline switch.

I've tried almost all combinations of baud rates and com port settings know to man.

MP tune knows when the ECU isn't in boostrap mode, it just wont talk to it the rest of the way.
I've checked continuity on the RS232 cable and its fine as well.

What am I missing?

[84omni]

http://www.turbo-mopar.com/forums/sh...Tune&highlight=
That's the link to a thread I started on when I was having a similar problem

[player1up]

I've read through that post about 5 times lol I don't see where the definitive fix for you was. Vipernbox's problem was problematic cable.
I did, at one point have some hex in the log file but that was earlier today and I'm super frustrated right now.
I'm using an older serial ( rs232 ) cable not the usb to serial cable so I get a little different message.

[ShelGame]

Bear with me for a sec as I'm a bit of a newb.
I've recently picked up a flashable SMEC with RS232 cable ( not USB ).

I'm getting the ECU bootstrapped ( no fuel pump kick ) but the error I'm getting on the PC is:

Unable to download entire boot program from serial coms.

I've tried every which way that I can think of more than once..
Here are the processes I've tried to read it.

Click read, click ok, switch pin 11 on, turn key on, switch pin 11 off.
Click read, click ok, switch pin 11 on, turn key on

I'm running a jumper wire straight from the battery with an inline switch.

I've tried almost all combinations of baud rates and com port settings know to man.

MP tune knows when the ECU isn't in boostrap mode, it just wont talk to it the rest of the way.
I've checked continuity on the RS232 cable and its fine as well.

What am I missing?

A standard com port on a PC can't communicate at the baud rates a SMEC uses. You can force it to use 9600 baud for flashing (actually 9608 on the SMEC side), but it won't be able to use that for datalogging. Once it's running the Chrysler code, it only uses 7812 and 62500 baud rates.

Use 9600 for both the boot and ECU baud rates in MP Tune and it should work.

[player1up]

There is a little circuit board that adapts it from serial to sci port and has some transistors on it.
Would the usb ftdi cable work if I were to find one?

[ShelGame]

There is a little circuit board that adapts it from serial to sci port and has some transistors on it.
Would the usb ftdi cable work if I were to find one?

Those transistors just change the voltage levels form TTL logic (0-5V) to RS232 logic (-12v to +12v). They don't affect the baud rate at all. You should be able to get that cable working for flashing. But, as I mentioned, it won't work for logging.

Long-term, you'd be better off getting a USB cable.

[wowzer]

are you using just a straight rs232 cable? i'm thinking you'll also need a ttl to rs232 line leveler/inverter to get the signals from the 0-5 with ttl to the -12 to 12 for rs232. an ftdi cable is SOOOOOO much simpler........

[player1up]

Wowzer, it does have some sort of ttl chip at the end basically serial on one end, circuit board in the middle and sci plug on the other. Problem is that I can't get it to read the chip. The thing that freaking kills me is that it did work exactly once last night. I was able to read the flash chip...BUT I left the laptop in the garage and when I came back this morning it had powered off and apparently doesn't want to talk today.

But do I have the key / switch dance correct ? and do I leave pin 11 energized or off ?

[ShelGame]

Wowzer, it does have some sort of ttl chip at the end basically serial on one end, circuit board in the middle and sci plug on the other. Problem is that I can't get it to read the chip. The thing that freaking kills me is that it did work exactly once last night. I was able to read the flash chip...BUT I left the laptop in the garage and when I came back this morning it had powered off and apparently doesn't want to talk today.

But do I have the key / switch dance correct ? and do I leave pin 11 energized or off ?

For the SMEC, leave the boot pin energized. It's flaky if you switch it off.

Try this - switch pin 11 on, click read, click ok, turn key on

[player1up]

For the SMEC, leave the boot pin energized. It's flaky if you switch it off.

Try this - switch pin 11 on, click read, click ok, turn key on

ok, any specific settings for the com port in windows and in MPtune?...I went to radioshack at lunch and picked up a usb to serial cable ( has a box in line )

I'll do a search for the pinouts

[ShelGame]

ok, any specific settings for the com port in windows and in MPtune?...I went to radioshack at lunch and picked up a usb to serial cable ( has a box in line )

I'll do a search for the pinouts

Set all of the baud rates in MP Tune to 9600; bin size to whatever you're trying to flash (should be 32k, I think). Make sure it's set to the COM port that the adapter is plugged into

[wowzer]

there should be a file called mpt2boot.txt created when you try to connect. post that info up the next time you try to connect.

[wowzer]

For the SMEC, leave the boot pin energized. It's flaky if you switch it off.

Try this - switch pin 11 on, click read, click ok, turn key on

make sure you get it keyed on within the timeframe indicated. when you power up the smec in bootmode it sends an acknowledgement byte that mptune needs to see before continuing.

[player1up]

So as far as bootstrap mode is concerned as long as MPTune says something other than no boot ack received I should be good to go.

ok, well at least 'm getting somewhere... I went and picked up a USB to rs232 cable ( adapter, gigaware brand ) from radiosmack...and apparently not all cables are created equally. I managed to get the pinouts to at least read, but it's like it times out before it gets all of the data.
Something like baud:7812 1:239 and it has some data in the file, but not all of it. Depending on baud rate of the port it may return anywhere from 220 to 240 bytes.

This shouldn't be this difficult. I guess I'll go get a real FTDI cable tomorrow at tiger direct. In case you couldn't tell I'm a little impatient especially when I have almost everything....


-BootSerial routine-(Called from StdBinRead)
Using Boot Program MPTune Smec/Sbec Bootloader ver2040
got ecu acknowledgement byte - 0 at 16:42:44.9531250
total bytes returned on switch-on were 1
pausing for 2000 mSecs before continuing
boot download routine is started.
boot baudrate = 7812
hi speed rate = 62500
sent FF byte
sending boot program. length = 256
Boot send start time 16:42:46.9687500
Boot send finish time 16:42:47.2187500
Boot reread finish time 16:42:47.5468750
done sending boot program. bytes returned = 222
read timeout set to 328
bytes returned were:
CE 5C 66 90 80 CC C0 D8 77 36 AD 8F CC 81 E7 37 BF F6 DC 99 A0 A7 FE 23 20 97 F6 DC 59 ED 9E A0 A7 CD 88 CF CD 85 97 CD 60 1C 56 86 A7 F6 DC 19 A6 90 AE C5 8A A6 07 A0 B9 B7 F6 DC 59 A9 B3 F7 DC 19 0A EE A6 8A CD D3 E6 CD EB 88 A6 FE 8E EE A6 B5 CD C5 97 CD CC CD 9D 13 CD 8D E7 8A A6 60 63 22 98 DA DA 89 B9 B6 97 89 E7 88 CD F9 A7 B2 C3 A7 26 03 B7 C4 C4 91 B3 A6 F5 E6 B2 B9 F0 DE 66 66 F6 C6 86 F7 5C 36 80 FC 90 BB CE 8D 86 89 A6 FF 2F 5C FA 90 BB CE F6 E6 C1 FF A6 86 88 CC 03 A6 F4 CD B9 B6 C6 EA F7 D5 95 C6 95 F7 EA EA C6 B7 97 95 B2 B9 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 FE
Unable to download entire boot program for serial coms. -- baud:7812 bytes1:222
everything is done

[player1up]

welp, it's bricked.
d-cal was able to read it and flash it, but now it wont send a bootstrap acknowledgement...apparently that was a bad idea

[ShelGame]

welp, it's bricked.
d-cal was able to read it and flash it, but now it wont send a bootstrap acknowledgement...apparently that was a bad idea

Impossible to permanently brick a SMEC.

[player1up]

ok...how do I fix it? or is it something that's fixed with magic and a trip to the boostbutton shop? lol

[ShelGame]

ok...how do I fix it? or is it something that's fixed with magic and a trip to the boostbutton shop? lol

No, if you can bootstrap it, you can reprogram it. All of the code for flashing is loaded when you bootstrap the ECU.

Unless something failed in the module. But, that's not likely to be caused by a bad flash.

[player1up]

Ecu did not send a bootstrap startup acknowledgement....

[wowzer]

rob L - when using a regular usb to serial cable (not ftdi) - don't you still need to invert the tx/rx signals? i.e. will a regular usb to serial cable work?

player1up - the bytes that came back from the ecu are nowhere close to the bytes that were sent........ somethings whacky somewhere.