Bootloader with USB cable

[The_Elusive_Pickle]

Good evening,
I am having trouble getting my bootloader code on my MS-II. I don't have access to true serial port. I have a USB cable that plugs into the MS-II daughter board and a usb to serial that plugs into the DB-9 port. Both pass the loopback test just fine and tunerstudio can see both just fine. I have set the settings as mentioned in the manual (115200 baud and buffers as low as possible). I can't get it load the code though. When I use the USB to USB cable the comm port has a bunch more settings but I couldn't mind the magical combo that works. Has anyone managed to get theirs to bootload with a similar setup?
Thanks in advance,
Joe

[trakkies]

USB to serial adaptors are notorious for varying. Did you buy yours from an MS dealer, so guaranteed to work with MS?

[Matt Cramer]

Can you post a screen shot of what happens when you try loading firmware? There may be important clues in the wording of the error message.

[The_Elusive_Pickle]

USB to serial adaptors are notorious for varying. Did you buy yours from an MS dealer, so guaranteed to work with MS?

Unfortunately I did not though my understanding was that if it passed the loopback test then it was good to go. Is that not the case?

[The_Elusive_Pickle]

Can you post a screen shot of what happens when you try loading firmware? There may be important clues in the wording of the error message.

I will when I get home, I should have done that last night. Sorry

[The_Elusive_Pickle]

This is what I am getting from MS Downloader:
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3db3e0
File read successfully.

Opened comm port 3 at 115200.
Erasing main FLASH:
ERROR: Timed out reading response, 0xE0
Elapsed time: 2.03 seconds

That is with a usb to db9 cable and the serial cable mentioned below.

I got a DB9 cable but my laptop docking station doesn't seem to recognize it at all so I may just have to pick up a cheap computer with the port.

This is starting to drive me crazy.

I have gone through the connection trouble shooting guide. Could it be my crystal at this point? or the MS2 daughterboard?

[tony4790]

Hi and I would just like to say that I feel your pain as I spent many hours trying to get my laptop to communicate with my MS2 V3.0 ! I even purchased the Trendnet TU-S9 usb to db9 converter cable which is confirmed to work with the MS .

What I eventually did to get the whole thing to work together was not use the MS uploader programme v 2.00 !!

When you download the latest firmware , within the files is an uploader file which I tried (clutching at straws at this stage ) which opened up into a black screen which flashed all the data up in a matrix style and embedded the firmware and then asked me to disconnect the bootloader jumper and embedded more code .

I now have the latest firmware and no problem communicating between the MS and the tuner studio .

I hope this helps .

[The_Elusive_Pickle]

OK, I officially am out of ideas. I have a confirmed pass-through cable connected straight to a 9-pin serial port on my tower. I am still getting the below error:
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3db3e0
File read successfully.

Opened comm port 2 at 115200.
Erasing main FLASH:
ERROR: Timed out reading response, 0xE0
Elapsed time: 1.81 seconds

I get good loopback in TunerStudio's mini-term.
I have gone through all the of Connection Troubleshooting Guide.
One thing I have noticed is that the LEDs on my MS board don't light up at all when I turn it on with BL jumped. The FP light on the stim does but that is it.
My question at this point is could my problem be the crystal or do I need to replace the MS-2 daughter board?
Any help is appreciated.

[The_Elusive_Pickle]

Hi and I would just like to say that I feel your pain as I spent many hours trying to get my laptop to communicate with my MS2 V3.0 ! I even purchased the Trendnet TU-S9 usb to db9 converter cable which is confirmed to work with the MS .

What I eventually did to get the whole thing to work together was not use the MS uploader programme v 2.00 !!

When you download the latest firmware , within the files is an uploader file which I tried (clutching at straws at this stage ) which opened up into a black screen which flashed all the data up in a matrix style and embedded the firmware and then asked me to disconnect the bootloader jumper and embedded more code .

I now have the latest firmware and no problem communicating between the MS and the tuner studio .

I hope this helps .

I'm not sure what files you are talking about. Could I get a download link or something?

[trakkies]

If you mean the crystal on the main PCB, it's not needed for MS2. Thing that caused a problem loading code here once was a too low powered PS. Which seemed OK on first test with a Stim. Needs to be at least 500mA. A quick check would be to use a fully charged car battery - but do fit a fuse to the supply if trying this.

[The_Elusive_Pickle]

If you mean the crystal on the main PCB, it's not needed for MS2. Thing that caused a problem loading code here once was a too low powered PS. Which seemed OK on first test with a Stim. Needs to be at least 500mA. A quick check would be to use a fully charged car battery - but do fit a fuse to the supply if trying this.

I have the DIYAutoTune power supply so I don't think that is the problem.

[Bernard Fife]

Which code are you trying to load?

[The_Elusive_Pickle]

Which code are you trying to load?

The latest s19, 2.920.

[Bernard Fife]

T_E_P

You should see:

MegaSquirt Download 2.00

Reading C:/Users/Lance/Documents/Websites/megamanual.com/files/code/Monitor_v2.920.abs.s19:
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3db3e0
File read successfully.

Opened comm port 1 at 115200.
Erasing main FLASH:
Erased.
Writing:
Setting page register 0x3c:
Page set.
Erasing page 0x3c:
Erased.
Setting page register 0x3d:
Page set.
Erasing page 0x3d:
Erased.
Write complete, 1472 records, 47022 bytes.
Verifying:
Setting page register 0x00:
Page set.
Setting page register 0x3c:
Page set.
Setting page register 0x3d:
Page set.
Verification succeeded, 1472 records total (4 skipped).
Elapsed time: 12.49 seconds
MegaSquirt Download 2.00

Reading C:/Users/Lance/Documents/Websites/megamanual.com/files/code/Monitor_v2.920.abs.s19:
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3db3e0
File read successfully.

Opened comm port 1 at 115200.
Monitor mode failed.
Erasing main FLASH:
ERROR: Command not recognized, e=0xE1
Elapsed time: 0.40 seconds

Make sure you are using the V2.00 downloader (not 1.04): http://www.megamanual.com/files/software/

Make sure you are using a V2 MS2 and not an MS1 or a very early MS2 (pre-CANbus).

I have a USB cable that plugs into the MS-II daughter board and a usb to serial that plugs into the DB-9 port.

A USB cable that plugs into the daughtercard is likely a background debug module (BDM) cable (with 6 pins). You don't use this for loading code, you use it for loading the bootloader. To load code, use the serial port, ground the bootloader while powering up, and run the downloader.

It is very possible to corrupt the bootloader with a BDM cable if you don't use it correctly, so that might have happened to yours.

the LEDs on my MS board don't light up at all when I turn it on with BL jumped.

Do the LEDs turn on at all when the bootloader isn't jumpered? If not, then I suspect the power supply (these are quite prone to failure, and should be tested with a multi-meter anytime you have unexpected issues). If the LEDs do flash when you turn it on, then again the bootloader code might be corrupt.

Lance.

[The_Elusive_Pickle]

Lance,

Thanks for the reply. I am still getting the error I posted above when I run the MS Downloader. I do have V2.00 and am using the most current code I could find. I have never gotten past the "Erasing main FLASH:" stage as it always errors out. I now have a 9-pin DB9 pass through serial cable that I plug directly into a matching serial port on my tower (I bought this adapter over the weekend: http://www.microcenter.com/product/4170 ... _Host_Card) and I still get the same error. I will try redownloading the S19 file and uploading a clean version over my serial cable when I get home from work to see if I have indeed corrupted my S19 file. The LEDs on my MS board have never lit up. The ones on the stim do. The FP light flashes when I have the BL jumped. I have done all the voltage and such checking the connection troubleshooting guide so I don't think it is the power supply but I will triple check it too.

Thanks again.

Joe

[The_Elusive_Pickle]

So I just found http://www.msextra.com/downloads/ and I think I may be not so smart sometimes. Good god, at least I hope so. I'll update later hopefully.

[The_Elusive_Pickle]

It appears I am a complete confused person. I ordered a MS3 and have been trying to load code for a MS2. While the MS3 does come with a V3.0 board and the setup instructions are very similar in the MegaManual, they are also very different and not located on the MegaManual website. Thanks to everyone for trying to help me sort it out. I will update this when I have gotten through all the proper instructions and hopefully I won't have to bug you all again.

Thanks,
Joe

[trakkies]

Yes - it can be confusing. MS3 is extra code only. You'll find a link to the correct forum at the top of this page, and a link to the correct manuals from that.

[The_Elusive_Pickle]

Yep, it was just me. I am glad I don't appear to have ruined anything important. Got firmware loaded and connected to TunerStudio without a glitch. Thanks again to all and sorry for wasting your time.