forum.heinrichsweikamp.com

hello,
i would like to upgrade my firmware from 1.14 to 1.17 but,with tinybldwin when i press"check pic"i get this message:
Connected to \\.\COM3 at 115200
Searching for PIC ...Not found,
ERROR!
and when i press the writte button i get this one:
Connected to \\.\COM3 at 115200
HEX: 3 days old, INHX32,18Fcode+cfg+eeprom , total=99096 bytes.
Searching for PIC ...Not found,
ERROR!
and after a few seconds i can see the message "md2hash building"on the ostc.

with jdivelog i can t even choose a port and i can t find new port on my computer..

what did i miss ?

thanks

Hello,

Are you using the bootloader from our Download-Page? This program is preconfigured to 19200Baud. It won't work with 115200.

After pressing the Write or Check button the TX LED at the interface must blink for about 10 seconds. If this does not happen probably the driver is not or not properly installed.

Bootloader: http://www.heinrichsweikamp.net/ostc/en/download.htm#4

Driver: http://www.ftdichip.com/Drivers/VCP.htm

regards,
Matthias

hi,

i have erased and downloaded again both the driver and the bootloader..it gave me the same message..and after pressing the buttons there is no led blinking..so it must be a probleme with the driver?
i have dowloaded and installed the one for window xp..is there something else that i can do,apart try on an other computer if it works better?

regards

Hello,

Please try the following:
1: Download, unzip and run the Cleaner Tool from FTDI (Click -> ): http://www.heinrichsweikamp.net/ostc/do ... TClean.zip
This will completely remove the driver from your computer. You can do this manually with the "Device Manager" but it's more comfortable with this tool.

2: Download and unzip the Driver package again: http://www.ftdichip.com/Drivers/CDM/CDM ... tified.zip

3: Connect the Interface to the computer, a Pop-Up will appear asking for the driver.

4: Choose "Have disk..." and select the driver directory which you have created in Step 2

5: Start the bootloader AFTER you have pluged-in the interface (It will automatically search for the Interface)

6: Press "Check PIC" at the Bootloader, the TX LED at the interface must blink for 10 seconds.

With kind regards,
Matthias

In the Wiki "Interface" some details about the upgrade process are described: http://www.heinrichsweikamp.net/ostc/pm ... .Interface

Regards,
Matthias

Hi

Im having exactly the same issues as this

Connected to \\.\COM3 at 115200
Searching for PIC ...Not found,
ERROR!
and when i press the writte button i get this one:
Connected to \\.\COM3 at 115200
HEX: 3 days old, INHX32,18Fcode+cfg+eeprom , total=99096 bytes.
Searching for PIC ...Not found,
ERROR!
and after a few seconds i can see the message "md2hash building"on the ostc.

Im running windows vista my OSTC is firmware 118 v1.18 I have tried to change to 19200 in device manager however it keeps saying connected to com3 at 115200. I unistalled the driver then when I plugged the interface back into my laptop it searched for a driver but did not give me the option of use disk.

Thanks for your help

gareth

I also cannot install jdivelog.

Hi

Im having exactly the same issues as this

Connected to \\.\COM3 at 115200
Searching for PIC ...Not found,
ERROR!
and when i press the writte button i get this one:
Connected to \\.\COM3 at 115200
Searching for PIC ...Not found,
ERROR!
and after a few seconds i can see the message "md2hash building"on the ostc.

Im running windows vista my OSTC is firmware 118 v1.18 I have tried to change to 19200 in device manager however it keeps saying connected to com3 at 115200. I unistalled the driver then when I plugged the interface back into my laptop it searched for a driver but did not give me the option of use disk.

Thanks for your help

gareth

I also cannot install jdivelog.

Hello Gareth,

1.18 is quite old so an update is really recommended.

- Is the TX LED blinking when pressing "check" or "Write" at the Bootloader Software? If not you'll probably have not chosen the correct port.
- Can you download the dives from the OSTC with either JDiveLog or Divinglog (You can download a demo from www.divinglog.de)? If not there may be a problem with the interface. Check the pins in the interface connector, we had problems with pins that are too deep in the connector not making contact with the OSTC.

regards,
Matthias

Hi Matthias,

I have divelog (trial) and can connect to my ostc and download the dives.

When im trying to upgrade the firmware using tinybootloader im getting:

Could not connect to COM3 at 115200
ERROR!!

In device manager then into com ports the usb serial port is shown as com3 the port settings are

bits per second 19200.

The TX led does not flash at all.

The display on the ostc then says :building md2 hash

Thanks for your help

Gareth

Have you downloaded the Bootloader from our page? Because with this version the baud rate setting is preconfigured to 19200. 115200 will not work.

The not-blinking TX led indicates some problems with the COM port settings. I would suggest:
-check Divinlog and Bootloader COM port (Must be the same, of course)
-use the Bootloader from our page, maybe you should re-download the program again

You should get something like:

Connected to \\.\COM3 at 19200
Searching for PIC ... when everything is correct. Also, maybe Vista blocks the access to the port?

regards,
Matthias

Yes I downloaded everything from here. I have also tried to unistall and the install again.

Originally the port settings in device manager were are 115200, I manually changed them to 19200 in device manager, and still recieved the same error message.

I dont know if Vista is blocking access to the port and wouldnt know how to change it if it was, however if i can download to divelog i would not have thought it was blocked?

Hello,

To sum it up, we have:
- Interface is working (You can download dives)
- OSTC is working
- OSTC can be resetted (required for the bootloader)

So this is probably some kind of a Vista issue. Maybe you need to run the bootloader in administrator mode? We've tested it on Vista and it worked just like in XP so I do not have a Vista-specific solution.

Regards,
Matthias

Hi Matthias

This might be not a big help, but I'm running Vista since the first OSTC release and never had a problem with the bootloader, so I'm not sure if it's a Vista issue. It's not required to run the bootloader in admin mode or something like this.

Kind regards,
Sven

I have always the same problems.....
I'm very desapointed...
Great computer but poor interface

heinrichsweikamp Wrote:
-------------------------------------------------------
> Have you downloaded the Bootloader from our page?
> Because with this version the baud rate setting is
> preconfigured to 19200. 115200 will not work.

i had similar problem with bootloader from your
webpage. it always tried to connect with 115200
speed. i am not windows guru and i could not
force your software to use 19200 speed.

therefore, i have tried original bootloader from

http://www.etc.ugal.ro/cchiculita/softw ... loader.htm

it used actually 19200 baud speed and firmware
update went smoothly.

[...]

regards,

w

Hello,

Thanks for your post!

We have tested the bootloader on different VISTA systems (Home and Prof.) and it worked. Maybe the wrong driver was installed? We tried the non-beta 2.04.06 from FTDI and it connected with 19200.

The non-customized, original "Tiny bootloader" works fine, too.

Regards,
Matthias

i forgot to mention that it was windows xp.

i don't remember version of the driver though. i used
friend's computer, but i can check that today or
tomorrow.

I use the 2.04.06 too

I've tried on another PC with XP. Same problem.
The Tx led is blinking but not the Rx.

I'm very interested with this remark : "Check the pins in the interface connector, we had problems with pins that are too deep in the connector not making contact with the OSTC. "

The last time I had the same problem and you changed the interface.
How can I open the device containing the pins ?
Or do I have to send it back again ?

Regards

version of driver i used was 2.04.14.

anyway, imho, the problem is that bootloader does not
connect with speed 19200 and it is not possible
to change that.

it was written 19200

Just the same problem here. Did someone find a solution ?

Tried it on Vista or Xp, restarted several times, tried the original tiny or the "hw powered", standard 9600 baud or 19200 ...

In jdivelog 2.10 I have no port displayed at all ?

Install the RX/TX Packet during the installation of JDiveLog.

Regards,
Matthias

Indeed, I found that out it's busy in the meanwhile ...

So, Jdivelog with rx/tx on WinXP did work, I hope this helps for others ?

Do you recommand the use of jdivelog to upgrade, or still the tiny ? Of course the most important is it just works ...

Thanks for the quick answer !
Thierry.

Hello,

There are no known issues with Jdivelog and the upgrade process: The result will be the same. When using JDivelog I would recommend to close any other program before starting the upgrade.

regards,
Matthias