FDT continuously fails checking firmware update status (FX30s)

Hi, I use FDT2 on windows to flash my FX30s. It connects, flashes etc OK, but then fails when “checking the update status” continuously. I have tried the latest versions 1.0.1806.0 and the previous version. Both have the same problem.

Below is the log and error I get. What is going on? Any ideas? I’ve also attached the log files created by the tool.
GobiApi-fdt2 2019-08-30_15.31.51.625.txt (58.5 KB)
fdt2 2019-08-30_15.31.51.641.txt (62.0 KB)

C:\FX30-Production>.\switool\windows\fdt2.exe .\mcu-rmfw-boot-yocto-legato_wp85.cwe
FDT version: 1.0.1702.1
Awaiting suitable port or adapter …
Switching to boot & hold mode …
Disabling selective suspend …
Awaiting port removal …
Awaiting download port …
Switching to streaming mode …
Downloading images …
Writing image
Flashing image
Enabling selective suspend …
Awaiting adapter …
Checking update status …
Enabling selective suspend …
Firmware download failed.
Primary error code: 84 - Failed in checking FW update status.
Secondary error code: 84 - Failed in checking FW update status.
Device error code: 0x0 - Unknown device error code.
Final firmware update failure report - Result code: 0x0

Preexisting images information:
Current:
Firmware:
ImageId: 001.033_000
BuildId: 07.12.09.00_GENERIC
Configuration:
ImageId: 001.033_000
BuildId: 07.12.09.00_GENERIC
Final images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:

OEM PRI:

IMEI:

Total time elapsed: 140516 ms.

Time to switch to boot mode: 34250 ms.

Hi Karl,
Is your FX30 still functional? It looks like you’re going from R14 down to R13, is that correct? Are both images the stock FX30 images, or have you modified them?

Can you please provide the output of:
AT+WIOCFG?6

BR,
Chris

Hi @cchenry believe I am trying to upgrade to R14 from the stock R13? It is a stock image. And the units are responsive.

The response to that command is
+WIOCFG: 6,16,0,0,1,0,0

Thanks,

Karl

Hi Karl,
I’m not sure why fdt2 is failing.
Maybe you can try the following, in no particular order:

  1. Make sure you have the current drivers from the source and try fdt2 again if you don’t
  2. If you have a linux machine try swiflash
  3. Do an FX30 factory reset using the pushbutton. See the user guide on how to do this. And then try fdt2 tool
  4. Access the TP1 point an put the FX30 into boot and hold mode first

Let me know how it goes.

BR,
Chris

Instead of trying to fix fdt2 which was taking too much time, I have gone down the route of copying the files over to the device and using fwupdate… Of course this will only work with units that are currently running and are responsive, but that feels OK as this process is to be used on fresh units in production.