MS2/Extra beta 18,19 slow download firmware

[jsmcortina]

EDIT: Split this topic from the Miata 99-00 one as this is a general question.

Any idea on how to get faster downloads? 45 minutes to transfer it seems slow.

Transfer what from where to where?

James

[md95]

Any idea on how to get faster downloads? 45 minutes to transfer it seems slow.

Transfer what from where to where?

James

If he is talking about the actual downloading of firmware to the chip, i noticed this as well..it took 30-45 minutes to download beta18 to my MS2 chip..i wondered what was up with that..i thought it was my laptop or something..I never did check into yet though..I thought it may be because i'm using a Mac running windows xp through bootcamp..but i dont think so..maybe a setting got messed up..I havent tried downloading new firmware since. If thats how long the new betas are supposed to take, then fine, but if not, then i need to figure out what the deal is.

[jsmcortina]

45 MINUTES ? What ?!?!??

37 seconds here.

James

[AbeFM]

More carefully timing it put it in the 35-40 minute range. Not pleseant doing it 4 times in one night trying to test what makes this take a dive.

It's running pretty well, but very rich in the midrange, still working at it. Even my press-in-input circuits are working.


BTW, James, do you want anything else for looking at these files? I'll try to generate it for you.

[md95]

45 MINUTES ? What ?!?!??

37 seconds here.

James

Haha, yep, it took that long..it burned fine and everything, just took forever..never had a problem before. This was a brand new MS2 chip, loaded the bootloader, then beta 18. Something wasnt right, just dont know what would cause it.. It all works fine though..strange..only thing i can think of is if my COM port settings got messed up and set back to MS1 standards..I use a USB port replicator, and i have 2 USB ports on my laptop side by side..maybe i used the wrong one..

[jsmcortina]

Shame nobody mentioned this with beta18.

I changed download-ms2-firmware.bat to add the debug/verbosity option.

What debug option do you choose ?

I tested here with option 1 and it is as fast as normal. With option 3 it takes a few minutes.

James

[md95]

Shame nobody mentioned this with beta18.

I changed download-ms2-firmware.bat to add the debug/verbosity option.

What debug option do you choose ?

I tested here with option 1 and it is as fast as normal. With option 3 it takes a few minutes.

James

4 posts down in the beta18 thread..i mentioned it, but nobody said anything about it? I just thought it was me, and my setup/computer or something..Now that abe had the same isssue, makes me wonder what it was. At least i know this isnt right

[jsmcortina]

Ah yes, I see your post now.

What commandline is the batch file using to make the download happen? It will print this as it starts downloading.

James

[AbeFM]

I'd seen it a couple times in various threads, so I just figured it was an ignored issue. Too bad, since my computer ate itself again.

[AbeFM]

ms2dl.exe -d 0 -v 0 -r ms2dl.exe -j -c1 ms2extra.s19

My ini was writblocks off, delay 5, changed it to on, delay 1, it's been five minutes and it's not done and I'm leaving.

[jsmcortina]

Writeblocks is a directive to Megatune. It has nothing to do with the firmware download process.

What happens if you choose one of the debug options in the download batch file?

James

[AbeFM]

They all seem to work.

The first time I did it, I was excited like I found a problem since it said voltage too low for a reliable burn in MT, and then it said it couldn't connect in the downloader. Then I plugged in the serial cable.

Everything seemed fine (not that I know what to look for), just a long series of data sent, data returned, at about the same candance (just over 1-2hz). It said it was successful, and it seemed to be.

I've done it with the serial buffers on, off, high, and low... No difference.

[jsmcortina]

Try copying the download-MS2-firmware.bat from beta17 and overwriting the one in beta19 and let use know the outcome.

I tested the revised batch file numerous times when I re-wrote it and a number of times last night to confirm.

I've never had a download take long. Seeing as I download code 10+ times in a typical development evening, long downloads would cause a major slowdown in work.

James

[AbeFM]

For me, it's ALWAYS been slow. I've installed b15,16,17 and 18. And maybe 14?

So I wouldn't expect it to go faster then. But it could be my USB dongle thing?

[jsmcortina]

Please try regular MS2 using the graphical downloader.

If that is super-slow as well then something is seriously wrong with your serial comms and could be the cause of many other problems as well.

James

[AbeFM]

Pardon my ignorance, but what graphical downloader? And, can I get this to work for the MS-2x stuff?

[offtrack]

"i'm using a Mac running windows xp through bootcamp." wow !


if you have comm problems,
try using a PC ATX Desktop. with a real RS232 port.
running 98SE, w2k,or xp directly , bootcamp is translator and is slow.
Windows emulation is very slow. ( and problematic by nature)

then after that works , try something stranger like a laptop.

many lap tops have non compliant RS232 ports.
levels wrong, and clock accuracy compromised ( cost savings)
many Laptops are rated at 20k baud max ! ( look it up)

on any platform:
make sure there are no serial mouse code running on the Com ports in device manager.
then make sure the IRDA , port is turned off in the BIOS.
and that the COM1 port is enabled in the BIOS page, not disabled.

having a dual boot setup with a clean load of XP will help too.
call the second XP boot, XP MS2. ( easy to do)


to get my Laptop DELL CPX running I had to buy a 15mbps PCMCIA/Cardbus fast RS232 port. (fleebay)
with this port I never get errors or delays.

you can also download a free comm port loop back program .
you short pins 2 to 3 and set the baud real high and test the port
if it doesnt work, then it is bad, fix the port or the offending programs loaded in memory of the PC. (look FOR interrupt conflicts in INT.3 AND 4)

if you can't find this program , just contact me. Happy to help.
the Old semtel site had these for 20 years now. before the NET.


run a com port test is the best advice, you will ever get.
trust me. been doing this since 76' on CAI naked mini's.
History: the orginal IBM PC XT came with the loop back plug and prog.
1981


best wishes.

[offtrack]

http://interface.centraltreasure.com/fr ... tware.html

try this with the special plug.

note the mention of hiserial.sys file.
this will allow perfect coms on certain rs232 chips sets.

as you can see , it always does not work at 115.2k baud.

depend on the hardware.

start here and you will get results.

[muythaibxr]

I'm actually occasionally run a mac with bootcamp running windows XP, and have never had a problem with serial comms.

Ken

[md95]

I'm actually occasionally run a mac with bootcamp running windows XP, and have never had a problem with serial comms.

Ken

Yeah this macbook is new, but i did use it before this last beta18 to upload code to the MS2, and it worked fine. I think it was beta 17, or the test code for the 420a when James reworked it for single edge only. I've never had a problem using the mac through windows xp to burn data, or anything like that. It's worked perfectly. I use a Targus USB Port Replicator, and that has served me well too. Never an issue. I really think what happened was that i used the wrong USB port, but i dont know for sure. I'll have to try to upload code again and see what happens. Maybe i'll just upload beta18 again to the chip for a test.