OSTC2n locked up

[cparsons]

I have just used the TinyBootLoader to update my OSTC2n and it has died

The update message said completed, I saw the red 'Booting' message and now the screen is blank, won't start up and I have a flashing red light and a steady blue light even with the cable unplugged??

I have tried to update again, even with an older firmware and the PIC is not detected - what do I do now!!???

Heinrich, if you read this, is there anything else I can try or do I send it back for you to look at?

I have done this update a few times with no trouble at all

Regards

Chris (#2516)

[Solodiver]

try a hard reset using a magnet, make sure the USB cable is attached...

[heinrichsweikamp]

Solodiver, please stop posting this magnet "trick" everywhere, thanks! Done wrong you can permanently damage your unit...

Chris: What bootloader did you use (v1 or V2) and what was the output message in the log window?

regards,
Matthias

[cparsons]

I tried the magnet and got a white screen briefly and then back to the flashing red light and steady blue light - although I wish I had seen the later message from Heinrich before trying this...

Heinrich, the log window output is shown below

HeinrichsWeikamp Bootloader v2
www.heinrichsweikamp.com
Support: info@heinrichsweikamp.com
--------------------------------------------------------------------------------------------------

Connected to \\.\COM3 at 115200
HEX: 2 hours old, INHX8M,dsPICcode, total=0 bytes.
Searching for PIC ..., Not found
ERROR!
Not found!

But it looks like the downloaded hex file is empty (O bytes)

I tried a 'web download' and got the following message

HeinrichsWeikamp Bootloader v2
www.heinrichsweikamp.com
Support: info@heinrichsweikamp.com
--------------------------------------------------------------------------------------------------
Looking for http://www.heinrichsweikamp.net/autofir ... latest.hex
Could not access site information

Looks like your .net domain is not accessible?

I have done this automatic update quite a few times with no problems,
the last was 2.21 to the 2.22 beta a few days ago?

Regards

[heinrichsweikamp]

Hi,

Should be fixable at your place:

- Download Bootloader v1 program: http://www.heinrichsweikamp.com/#/de/ostc_2n/
- Download the correct HEX file! The file for the Mk.2 is called "mk2_v221_stable.hex", for example. http://www.heinrichsweikamp.com/#/en/ostc_2n/firmware/
- Choose correct HEX file in the bootloader file dialog: "Browse"
- Choose correct COM-Port in the bootloader (The bootloader searches all COM-Ports automatically)
- Here: Trigger the RESET with a magnet
- Press "write" at the bootloader within 10 seconds
- Wait about 1min.

regards,
Matthias

[Solodiver]

heinrichsweikamp Wrote:
-------------------------------------------------------
> Solodiver, please stop posting this magnet
> "trick" everywhere, thanks! Done wrong you can
> permanently damage your unit...

What exactly is the problem? Do not remember to hear such things in the past...

[cparsons]

You are my hero...

This worked, I was really worried there for a while, I will admit

I now have a working OSTC back again - I also repeated the update with Bootloader 2 and the 221 firmware and this worked also, the log output is shown below - I tried to get the web update and as you can see still get a 'not found' message but I can download the images myself, this is not a problem

Connected to \\.\COM3 at 115200
HEX: 101 days old, INHX32,18Fcode+cfg, total=81212 bytes.
Searching for PIC ...
Found:18F 4685
Reading HEX file... , Writing flash...
WRITE OK at 23:22, time:42.157 sec
Looking for http://www.heinrichsweikamp.net/autofir ... latest.hex
Could not access site information

Thank you so much for the excellent support

Best wishes

[cparsons]

I have been doing a little experimenting and it looks as if using the Bootloader v2 'web update' gives an error message saying 'Could not access site information' but still creates an empty update file 'webfile.hex', which I suspect I managed to upload to my OSTC (not paying attention to what was shown on the log screen!)

The path it is looking for is http://www.heinrichsweikamp.net/autofir ... latest.hex - presumably this will get corrected eventually?

Mind you, perhaps others are not as stupid as me