V1.8 to 2.01 problems

Legacy OSTC's
Post Reply
Lee Hatton

V1.8 to 2.01 problems

Post by Lee Hatton »

Hi All,

Trying to upgrade from V1.9 to V2.01 using bootloader 1 am and getting the following error:
Could not connect to at 19200

Any ideas ?

(Windows 7 by the way)

Thanks

Lee
heinrichsweikamp
Posts: 4469
Joined: 13 May 2007, 18:07

Re: V1.8 to 2.01 problems

Post by heinrichsweikamp »

Lee Hatton Wrote:
> Could not connect to at 19200

Port not set. Check the Windows-Device manager for the correct COM port number. Enter this number, e.g. "COM3" into the "Comm" field.

Make sure to follow these instructions step-by-step: http://www.heinrichsweikamp.com/read.php?2,4071

Regards,
Matthias
Lee Hatton

Re: V1.8 to 2.01 problems

Post by Lee Hatton »

Hi Matthias.

I have Coms 1,2, & 4 available for selection, but all give me a:

Connected to \\.\COM1 at 115200
Searching for PIC ..., Not found
ERROR!

Any ideas ?

Thanks

Lee
heinrichsweikamp
Posts: 4469
Joined: 13 May 2007, 18:07

Re: V1.8 to 2.01 problems

Post by heinrichsweikamp »

Most likely three issues here:

1. You need to find out which port is the right one:
- Unplug OSTC
- Open the device manager, expand COM port section.
- Connect OSTC -> A new port should be visible. THIS port is the right one.

2. Now you have "115200" - which means you're using the v2 bootloader. This will only work if you have 1.90 or later.

3. If you have v1 -> you need to follow the instructions correctly. Most likely you're missing the "Reboot OSTC" section here...

regards,
Matthias
Lee Hatton

Re: V1.8 to 2.01 problems

Post by Lee Hatton »

Hi Matthias,

Again, thanks for your reply.

With bootloader V1 I am getting somewhere in that the process appeared to be working. But I have been stuck on an orange 'please wait' screen with both blue and red blinking LED's for about 15 minutes.

Is it safe to unplug or have I frozen ?

Lee
Lee Hatton

Re: V1.8 to 2.01 problems

Post by Lee Hatton »

Panic over. The 'please wait' lasted about 17 mins.

Matthias, thank you for your help and assistance.

Lee
heinrichsweikamp
Posts: 4469
Joined: 13 May 2007, 18:07

Re: V1.8 to 2.01 problems

Post by heinrichsweikamp »

The logbook conversion - With the "Please Wait" - always causes some panic ;) Btw., it is safe to disconnect USB when "Bootloader" disappears.

Regards,
Matthias
Jan_Arild
Posts: 27
Joined: 30 May 2010, 19:53

Re: V1.8 to 2.01 problems

Post by Jan_Arild »

I will need to opgrade from ver 1.7

From what I understand I need to first upgrade to ver1.8, where is this avelible for download?

Second, I will be able to upgrade directly from ver 1.8 to ver2.01 by using Botloader V2.

Jan
tiefunten
Posts: 284
Joined: 18 May 2011, 23:58

Re: V1.8 to 2.01 problems

Post by tiefunten »

No, upgrade using Bootloader V2 is only possible from V1.9 upwards. Bootloader V1 should work directly from V1.7 to V2.01.
heinrichsweikamp
Posts: 4469
Joined: 13 May 2007, 18:07

Re: V1.8 to 2.01 problems

Post by heinrichsweikamp »

Correct, you can go in one step to the 2.01 with the v1 bootloader.

Regards,
Matthias
Jan_Arild
Posts: 27
Joined: 30 May 2010, 19:53

Re: V1.8 to 2.01 problems

Post by Jan_Arild »

Great, I will give it a go :-)
Jan_Arild
Posts: 27
Joined: 30 May 2010, 19:53

Re: V1.8 to 2.01 problems

Post by Jan_Arild »

I did the following:
-Installed bootloader V1
-Downloaded HEX file ver 2.01 to lockal directory
-Choose HEX file ver 2.01 in the bootloader file dialog: "Browse"
-Choose COM-Port 3 in the bootloader
-OSTC Mk.2 Reset Menu, choose "Reboot OSTC"
-Pressed "write" at the bootloader

OSTC returned to surface screen within 3 sec. and the following error apared in the Bootloader.

"Connected to \\.\COM3 at 115200
could not understand HEX file
ERROR!"

Please advice :-)
heinrichsweikamp
Posts: 4469
Joined: 13 May 2007, 18:07

Re: V1.8 to 2.01 problems

Post by heinrichsweikamp »

Are you sure you selected the HEX file - and not the .zip archive?

Regards,
Matthias
Jan_Arild
Posts: 27
Joined: 30 May 2010, 19:53

Re: V1.8 to 2.01 problems

Post by Jan_Arild »

Hi Matthias, you are correct.
Now new error

Connected to \\.\COM3 at 115200
HEX: 0 min old, INHX32,18Fcode+cfg, total=81556 bytes.
Searching for PIC ...Not found,
ERROR!
Jan_Arild
Posts: 27
Joined: 30 May 2010, 19:53

Re: V1.8 to 2.01 problems

Post by Jan_Arild »

Nope, still no go.. the OSTC screen says

Buliding MD2 harse
Please wait....

Then black screen and orange led blinking only
heinrichsweikamp
Posts: 4469
Joined: 13 May 2007, 18:07

Re: V1.8 to 2.01 problems

Post by heinrichsweikamp »

Jan_Arild Wrote:
-------------------------------------------------------
> Nope, still no go.. the OSTC screen says
>
> Buliding MD2 harse
> Please wait....


-> Normal after every reboot - no matter if a new firmware was installed or not.

> Then black screen and orange led blinking only

-> Normal sleep mode (Charging)

The "115200" indicates your using the v2 bootloader. You need the v1 (Screenshot attached)!

Regards,
Matthias
Jan_Arild
Posts: 27
Joined: 30 May 2010, 19:53

Re: V1.8 to 2.01 problems

Post by Jan_Arild »

Hi Matthias
From what I'm understand I use Bootloader V1.9.5
But when checking PIC I got error, see attach
Jan_Arild
Posts: 27
Joined: 30 May 2010, 19:53

Re: V1.8 to 2.01 problems

Post by Jan_Arild »

When checking my PC for correct com, OSTC is com9, in the Bootloader I can only choose form com1-4.

Is there a way around this?
Post Reply