Here4 UBLOX firmware update fail

Hey everyone,

I have a Here4 GPS and I tried to update the NEO F9P Firmware. I used the serial passthrough to connect to U-Center and everything seemed fine but once I started uploading the firmware it crashed and now it seems to be locked. Here is the log output from U-Center firmware update:

Setup pipes

Firmware update tool launched

 -p STDIO -b 9600:9600:230400 --no-fis 1 -C 1 -s 0 -t 1 -v 1 "Z:\home\jacob\Downloads\UBX_F9_100_HPGL1L5_140_F9P.a953bd2d71061ed21cc6fdc431ab39a5.bin"



----------CMD line arguments-----------

Image file:        Z:\home\jacob\Downloads\UBX_F9_100_HPGL1L5_140_F9P.a953bd2d71061ed21cc6fdc431ab39a5.bin
Flash:             <compiled-in>
Fis:               flash.xml
Port:              STDIO

Baudrates:         9600/9600/230400
Safeboot:          0

Reset:             1
AutoBaud:          0
Verbose:           1
Erase all:         1

Erase only:        0

Training sequence: 1

Chip erase:        1

Merging FIS:       1

Update RAM:        0

Use USB alt:       0

---------------------------------------

  0.0 u-blox Firmware Update Tool version 23.04

  0.0 Updating Firmware 'Z:\home\jacob\Downloads\UBX_F9_100_HPGL1L5_140_F9P.a953bd2d71061ed21cc6fdc431ab39a5.bin' of receiver over 'STDIO'

  0.0   - Opening and buffering image file

  0.0   - Verifying image

  0.0   - Got an encrypted image with footer info

  0.0   - CRC Value         	:    B8629764

  0.0   - Footer Version    	:    0
  0.0   - Number of Images  	:    2

  0.0   - Footer Size       	:    28

  0.0   - Image Config Size 	:    0
  0.0   - Image 0 Size     	:    752372

  0.0   - Image 1 Size     	:    539844

  0.0   - Trying to open port STDIO

  0.0   - Setting baudrate to 9600

  0.2   - Sending training sequence

  0.2   - Received Version information

  0.2   - Receiver currently running SW 'ROM BOOT 1.02 (a11814)'
  0.2   - Receiver HW '00190000', Generation 9.0

  0.2   - Sending ROM CRC Poll

  0.3 ROM CRC: 0x118B2060

  0.3 u-blox9 ROM1.02 hardware detected (0x118B2060)
  0.3  Getting Port connection to receiver

  0.4   - Connected port is: UART1

  0.4  Starting LDR TSK

  0.4   - LDR TSK started successfully

  0.4  Identify flash loader

  0.5   - Uploader version 5.1 detected

  0.5  Stop GPS operation

  0.5  Detecting Flash manufacturer and device IDs

  0.6   - Flash ManId: 0x009D DevId: 0x6015

  0.6   - Not merging anything

  0.6   - Flash size:   2097152

  0.6   -  Flash block:  512 x 4096

  0.8   - Setting baudrate to 230400

  2.0   - Retry poll

  2.1 Chip erase started

  2.1  Receiver info collected, downloading to flash...

Writing packet 1/2524
Writing packet 2/2524
Writing packet 3/2524
Writing packet 4/2524
Writing packet 5/2524
Writing packet 6/2524
Writing packet 7/2524
Writing packet 8/2524
Writing packet 9/2524
Writing packet 10/2524
Writing again packet 0
Writing again packet 1
Writing again packet 2
Writing again packet 3
Writing again packet 4
Writing again packet 5
Writing again packet 6
Writing again packet 7
Writing again packet 8
Writing again packet 9
Writing again packet 0
Writing again packet 1
Writing again packet 2
Writing again packet 3
Writing again packet 4
Writing again packet 5
Writing again packet 6
Writing again packet 7
Writing again packet 8
Writing again packet 9
Writing again packet 0
Writing again packet 1
Writing again packet 2
Writing again packet 3
Writing again packet 4
Writing again packet 5
Writing again packet 6
Writing again packet 7
Writing again packet 8
Writing again packet 9
Writing again packet 0
Writing again packet 1
Writing again packet 2
Writing again packet 3
Writing again packet 4
Writing again packet 5
Writing again packet 6
Writing again packet 7
Writing again packet 8
Writing again packet 9
227.2 ERROR: Write retries for packet 0 exceeded.

227.2 Firmware Update FAILED


Firmware Update Utility has unexpectedly terminated

Exit code (2)

The main issue now is that I cannot ever restore it to it’s previous settings.

Any ideas?

Thanks in advance.

@AlexPapadimitriou the UBlox unit will now be stuck in safeboot and stuck at 9600 baudrate. To recover it, connect with baudrate 9600 in mission planner instead of 230400, and then start the update. This will fail as well, but baudrate will be 230400.

Now without power cycle, stop serial forward and connect with 230400 as the baudrate for serial passthrough.

Thanks for getting back!

Should I connect via UART 1 or CAN and serial passthrough? For the first try I used DroneCAN GUI serial passthrough.

@AlexPapadimitriou above suggestion can be done with Serial Passthrough