Skip to main content ↑ ↓
Topic: Update mode is not activated (Read 4236 times) previous topic - next topic

Update mode is not activated

I'm trying to do firmware upgrade for OBLS. When I press UPDATE and RESET buttons ACT led does not turn on like it is said in the manuals.  What are my options ? Is the device hardware damaged ? Will I get refund ?

Re: Update mode is not activated

Reply #1 –
Ok, so I jumpered PGC and PGD pins and press reset. Nothing happens.

Port status from Usbtreeview program:


    =========================== USB Port3 ===========================

Connection Status        : Device failed enumeration
Port Chain              : 1-3

      ======================== USB Device ========================

        ---------------- Connection Information ---------------
Connection Index        : 0x03
Connection Status        : 0x02 (DeviceFailedEnumeration)
Current Config Value    : 0x00
Device Address          : 0x00
Is Hub                  : 0x00 (no)
Number Of Open Pipes    : 0x00 (0)
Device Bus Speed        : 0x00 (Low-Speed)

        ------------- Device Qualifier Descriptor -------------
bLength                  : 0x00 (0 bytes)


Where can I get the latest .hex to update the bootloader? I seem to be having v 1.04 board

Re: Update mode is not activated

Reply #2 –
I was able to update the bootloader with Bus Pirate from BP-OLS-bootloaderrescue-v1.zip according to these instructions:
http://dangerousprototypes.com/2010/06/ ... er-rescue/

I checked before and after programming that PIC is read correctly in the program. Programming really should have some verification function even it is slow.

Still no go: I then tried to update firmware with fw_update:

D:UserslainemiDownloadsOLSBP-OLS-bootloaderrescue-v1Firmware-0506update>fw
_update -e -w -m flash -vid 0x04D8 -pid 0xFC90 -ix OLSv1-firmware-v05-20MHz.hex

U2IO flash erasing: FAILED.
Device is not found.
Operation aborted.

D:UserslainemiDownloadsOLSBP-OLS-bootloaderrescue-v1Firmware-0506update>pa
use
Press any key to continue . . .

Again usbtreeview does not identify OBLS bootloader:


    =========================== USB Port1 ===========================

Connection Status        : Device failed enumeration
Port Chain              : 3-1-5-1

      ======================== USB Device ========================

        +++++++++++++++++ Device Information ++++++++++++++++++
Device Description      : Unknown Device
Device ID                : USBVID_0000&PID_00007&34A5C852&0&1
Driver KeyName          : {36fc9e60-c465-11cf-8056-444553540000}033
Legacy BusType          : PNPBus
Class                    : USB
Service                  :
Enumerator              : USB
Location Info            : Port_#0001.Hub_#0005
Manufacturer Info        : (Standard USB Host Controller)
Capabilities            : Removable, RawDeviceOK
Address                  : 1
Problem Code            : 43 (CM_PROB_FAILED_POST_START)
Power State              : D3 (supported: D0, D2, D3, wake from D0, wake from D2)

        ---------------- Connection Information ---------------
Connection Index        : 0x01
Connection Status        : 0x02 (DeviceFailedEnumeration)
Current Config Value    : 0x00
Device Address          : 0x00
Is Hub                  : 0x00 (no)
Number Of Open Pipes    : 0x00 (0)
Device Bus Speed        : 0x00 (Low-Speed)

        ------------- Device Qualifier Descriptor -------------
bLength                  : 0x00 (0 bytes)

Re: Update mode is not activated

Reply #3 –
Ok. Finally got the bootloader to run.
Turns out my OBLS has 16MHZ and NOT 20MHZ crystal !! I was flashing 20MHZ bootloader with BP like it says in the rescue information.

I highly suggest to add note there to first check what crystal is in OBLS and then choose the correct bootloader!

Re: Update mode is not activated

Reply #4 –
Hi Knockerd,

Glad you worked it out! :)

You generally do not start reflashing bootloaders without a good reason and from the initial problem you have mentioned in viewtopic.php?f=23&t=5613
it looked like you had a software problem more than a hw one as you were actually able to have the device enumerated before you started updating the bootloader.

The recovery guide you read was for OLS v1.01 while you have v1.04.
Obviously if the crystal is the wrong freq, that can affect all usb communication as well. I have been in a similar situation as you as I soldered myself my OLS and the first time I tried to flash it was with bootloader v2 for 16 MHz but I had a 20Mhz crystal (as stated in the v1.04 partlist so maybe that needs updating) so basically I had the same problem but just the other way around. :)

Anyway, the important part is to have the matching bootloader AND configuration bits for the crystal you have if the hex file you want to use does not have them exported from mplab.

Have you updated the firmware to v3 and bitstreams to v3.07?
And if you did, do  you still have problems connecting from the OLS client as you mentioned in the other thread?

I did a test on a Win64 bit machine in realterm and after connecting,  sending 0x02 (type it as that using the textbox from the Send tab and press send numbers) should return 1ALS if the OLS device was in normal mode.

Regards,
tkg

Re: Update mode is not activated

Reply #5 –
Thanks! I'm going to do some tests today and record a video.

Quote
Anyway, the important part is to have the matching bootloader AND configuration bits for the crystal you have if the hex file you want to use does not have them exported from mplab.

I believe I now have the correct bootloader because I was able to flash new firmware. OLSv1-bootloader-v2-16MHz

But what are the configuration bits ?

Also could you check from Device Manager - communications port - driver details. What files it is using ? Mine is using:

hhdspmc62.sys
usbser.sys

Re: Update mode is not activated

Reply #6 –
Hi Knockerd,

For my Win7 64bit pc, I only have usbser.sys. That is really what is needed as the OLS presents itself as a Serial CDC and widows already has drivers for it, but it still needs the proper OLS inf file to match the PID/VID.

I have no idea what hhdspmc62.sys is (or more exactly from where) but it might be a filter driver that could end up filtering/blocking your communication. It might be part of your antivirus  or maybe  even part of a virus. I don't want to be alarmist but it is possible there is a good chance for it to be your main problem.

The configuration bits are described in section 27.1 from http://ww1.microchip.com/downloads/en/D ... 39931d.pdf
The short story is that they describe how your PIC is configured and if they are not set up consistently you can also have problems from there, but again I still think your current problem is more software.

Regards,
tkg