Jobro

iTrader: (2)

Hello all,

I've recently upgraded my V3.0 Board from an MSI running high res msns-extra.

I just put the MSII chip in today and I can't get it to program the processor.

I get this error message

"ERROR: Could not read monitor prompt, 0x00 0x3E 0x00"

I get this message when I try to use either the batch file installer inside the latest release package. I also get the message when trying to use the MS Download 2.0 installer when trying to install base MSII code.

I'm not sure what to do, the ECU still boots if I put the MSI processor in.

If anyone could help that would be awsome. I'm using a real rs232 port with baud rate set to 115200 when I try to use the MSII processor.

2Lucky2tha7

iTrader: (3)

I'm kinda curious as well because I will soon be upgrading to the MS-II processor as well. I don't know exactly when, but as soon as the funds and time will allow it.

Jobro

iTrader: (2)

I spent all morning reading info before I even powered it up. I also moved two circuits built in the protoarea because they clashed with the larger size of the ms2 processor. So its not like I threw it in. Damn it doesn't work. This is stupid. lol

Maybe don't worry about the upgrade :P You lose LOTS of outputs!

Jobro

iTrader: (2)

OK I know the problem.

I accidentally programmed the extra s19 file straight onto the processor using the ms2dl.exe program included in the ms2extra1.02.zip file. I used the ms2dl.exe program with commands -filename etc to put the wrong s19 file in the ram.

How do you reset this? I guess I should get reading the HC12 datasheet. I might even have access to an in circuit programmer at uni fingers crossed.

muythaibxr

Just use the jumper and the standard downloader to reprogram whatever s19 you want.

There's no need to get any kind of programmer because there's no way without a BDM for you to have messed up the bootloader that is triggered by the boot jumper.

Ken

Jobro

iTrader: (2)

I created these threads because that is not working. I get the monitor error


"ERROR: Could not read monitor prompt, 0x00 0x3E 0x00"

When I try to do that.

Jobro

iTrader: (2)

I did all this stuffing around. It is no exageration that I have tried to program this chip maybe 50 times. I then decided to try my usb to rs232 adaptor instead of using my real serial port. This resolved the issue almost instantly.

Its funny because everyone always complains about usb adaptors and this time it solved the problem for whatever reason.

muythaibxr

Ahh, what kind of laptop or desktop are you trying to do this with?

I've heard of some older dell's having problems with their real serial ports.

Ken

Jobro

iTrader: (2)

Its an ex-institution (bank, uni etc for 3 to 3.5 years) Dell Latitude D600. The communications worked perfectly with my MSI chip tho. Its in pretty good condition overall, no bad sectors, dints scratches or memory errors.

I just tried to use the real serial port again, its like it can get communications but it crashes as soon as it connects so you see meaningful readings for about 0.5 seconds.

I'll bring home another rs232 cable from uni today, I have another one sitting on my desk, if that fails we have an asus machine I might be able to test to prove it is definately the laptops fault.

I will also try and do a test at 9600baud using the MSII to confirm if it is a baudrate dependant limitation.