EVAL-ADPDUCZ cannot update FW

HI,

We purchased a EVAL-ADPDUCZ with a ADPD188GG eval (March 2021).  Loaded wavetool fine, was able to connect via USB and have wavetool indicate the FW on the STM32 needed upgrade.  Connected second USB cable and followed instructions with BOOT0 button.  Can't get FW to upgrade.  We tried multiple machines.

I was able to see the STM32 DFU driver load in device manager after restarting the micro with BOOT0 asserted.  But can't get FW to update.

I've read all the forums and can't find anything else to try.

We're using WIN10 PCs that are up to date with drivers/OS updates.  USB connectivity seems fine.  STM32 DFU driver loads correctly.  The STM32 driver appears to be the latest (I tried to upgrade it too).  No info in log files.

 

Please advise so I can evaluate the optical sensor.

Thanks,

David

Parents
  • 0
    •  Analog Employees 
    on Apr 6, 2021 2:57 PM

    Hi David,

    The failure of firmware (FW) update may be due to the battery not fully charged. To charge the battery, make sure the battery is connected (white 3-pin connector with red and black wires on the back) and the EVAL-ADPDUCZ board is connected to PC (or USB power adaptor) via the mini-USB port next to the switch. 

    Please charge the EVAL-ADPDUCZ board for a few hours before the FW update.

    Regards,

    Glen B.

  • Glen, 

    The eval board receives power from the minii-USB connection (FTTD chip USB port), so the battery is not required.  The eval board documentation indicates this is the case.  If connecting the battery and charging it before use is required, ADI needs to update the eval board documentation.

    Clearly this is not related, as Bilal indicates below.  Please refer to the video Bilal showed.  This is the same behavior I experienced on my PC.

    Regards,

    David

  • 0
    •  Analog Employees 
    on Apr 8, 2021 3:30 PM in reply to david1234

    Hi David,

    It is recommended to have the battery fully charged before FW update. It also works if you power the EVAL-ADPDUCZ by the mini-USB cable. 

    The video clip from Bilal suggested that the board failed to be in Boot Mode (0:18), which could be due to the EVAL-ADPDUCZ being in storage for some time. Power up and turn on the EVAL-ADPDUCZ for a few hours before FW update will solve the issue. 

    You can follow the steps of FW update in the EVAL-ADPD188GGZ user guide: 

    https://www.analog.com/media/en/technical-documentation/user-guides/eval-adpd188ggz-ug-1256.pdf

    The FW update is much more user friendly and easier with the latest version of Applications Wavetool. In any case, please make sure that the micro-USB is connected to the PC for the FW update (refer to Figure 6 in the user guide above).

    If you power the EVAL-ADPDUCZ by the mini-USB, both the micro-USB and the mini-USB need to be in place. It doesn't matter if you connect the mini-USB to the PC or a power adaptor. The micro-USB has to be connected to the PC running the Applications Wavetool.

    Regards,

    Glen B.

     

  • HI Glen,

    The battery has nothing to do with this issue.  We've tried both ways without any effect..  Charging for any time or a storage issue IS NOT the problem.

    We received some support from the guys at Arrow Australia for a solution as they've had the same issue in the past.  We now have a workaround.

    It seems that the ADI software is no longer compatible with either WIN10 or the STM32 driver that WIn10 prefers.  

    The way we made this work was to go to a pretty old celeron PC with an ancient OS on it to run the software.  Bilal did the work but after upgrading the FW on this old machine it now works on a WIN10 PC with the current release OS version.

    It appears that Wavetool has a problem to be fixed.  Finding old PCs is getting harder and harder as time goes on!

    Regards,

    David

Reply
  • HI Glen,

    The battery has nothing to do with this issue.  We've tried both ways without any effect..  Charging for any time or a storage issue IS NOT the problem.

    We received some support from the guys at Arrow Australia for a solution as they've had the same issue in the past.  We now have a workaround.

    It seems that the ADI software is no longer compatible with either WIN10 or the STM32 driver that WIn10 prefers.  

    The way we made this work was to go to a pretty old celeron PC with an ancient OS on it to run the software.  Bilal did the work but after upgrading the FW on this old machine it now works on a WIN10 PC with the current release OS version.

    It appears that Wavetool has a problem to be fixed.  Finding old PCs is getting harder and harder as time goes on!

    Regards,

    David

Children
  • 0
    •  Analog Employees 
    on Apr 20, 2021 5:22 PM in reply to david1234

    Hi David,

    It is great that you got a workaround.

    There have been a few cases where charging the battery solved the Boot mode issue. The software Applications Wavetool works fine with Windows 10. To make sure, I installed as administrator the Applications Wavetool 3.6.1 on my home computer with Windows 10 Home (64-bit). The FW update was very smooth.

    Please note that the Applications Wavetool works with USB - STM Device in DFU Mode for FW update. Again please follow the sequence to set the Boot Mode. After Step 4, release the Boot0 pin and the device is in Boot Mode. The Device Manager will update the USB list with “STM Device in DFU Mode” added.

    The issue of failed to be in Boot mode you had may be caused by the older driver STM32 BOOTLOADER on your computer. You can remove your STM32 BOOTLOADER driver and have a fresh installation of the Applications Wavetool either “Run elevated” for power user or “Run as administrator” for administrator to allow proper installation of drivers included in Applications Wavetool.

    Regards,

    Glen B.