I’m struggling to update the firmware on this module.
BG770AGLAAR01A05_01.205.01.205 ← current firmware BG770AGLAAR01A05_01.300.01.300 ← Trying to update to
Using QFlash and debug_uart, click start, shows ‘Please Reset’
I reset module and it changes to ‘Check module mode pass’
After 30s or so changes to ‘FAIL, Check chip info time out’.
In the past I was able to successfully update the firmware on this module, using the same process. But I think that was when I was updating from an older firmware possibly: BG770AGLAAR01A03_01.007.01.007
Have tried without flow control (how I managed to do it before) and with, but same result. Is there any reason I should not be able to update from this version? Any ideas what else I should try. Thanks.
Think I have got closer, I changed some settings in windows device manager → ports → serial port.
Set the baud rate to match QFlash.
Now I get:
Please Reset
Check module mode pass
DL Start ...
FAIL, error:there were errors while executing the burning process... see log file for additional
Log shows:
2026-02-20 11:23:01:237 <--> ChipType = D0_TG
2026-02-20 11:23:01:237 <--> Check chip info pass
2026-02-20 11:23:01:237 <--> Checkchip info pass
2026-02-20 11:23:01:237 <--> Check module success
2026-02-20 11:23:01:237 <--> Check module success
2026-02-20 11:23:01:440 <--> DL start ......
2026-02-20 11:23:01:440 <--> C:\flash\ModemFirmware\QFlash_V7.7\Altair\1\powershell.exe /c "C:\flash\ModemFirmware\QFlash_V7.7\Altair\1\ImageBurnTool1.exe -v "C:\flash\ModemFirmware\BG770AGLAAR01A05_01\RK_03_00" D0_TG /0 /1 /2 /3 /4 /7 /11 /12 /18 /19 -uartparams 0 1 921600 0 -s 1 -n 1"
2026-02-20 11:23:05:309 <--> Can't verify Uboot state
2026-02-20 11:23:05:309 <--> Can't verify Uboot state
2026-02-20 11:23:05:309 <--> The device is not in Uboot state
2026-02-20 11:23:05:309 <--> The device is not in Uboot state
2026-02-20 11:23:05:309 <--> Could not find or connect to device on port: COM1
2026-02-20 11:23:05:309 <--> Could not find or connect to device on port: COM1
2026-02-20 11:23:05:309 <--> Aborting ...
2026-02-20 11:23:05:309 <--> Aborting ...
2026-02-20 11:23:05:309 <--> ERROR:
2026-02-20 11:23:05:309 <--> ERROR:
2026-02-20 11:23:05:309 <--> There were errors while executing the burning process ...
2026-02-20 11:23:05:309 <--> There were errors while executing the burning process ...
2026-02-20 11:23:05:309 <--> See log file for additional information
2026-02-20 11:23:05:309 <--> See log file for additional information
2026-02-20 11:23:05:309 <--> error:there were errors while executing the burning process ... see log file for additional information
2026-02-20 11:23:05:309 <--> FAIL, error:there were errors while executing the burning process ... see log file for additional information
I have also tried recovery mode (short debug_uart) and it looks like it gets further.
It seems to download the U-Boot, but then hangs on Can't verify Boot state. Here is the log for that:
ok, so I have managed to update the module. Leaving this here in case it is useful for anyone else.
Setting the config below seemed to allow it to work. Not sure if it is 0 by default or I changed it before. Also not sure if this is definitely a required thing, but either way I managed to update a module.
AT+QCFGEXT="setbdelay",1 ← Set U-Boot delay to 3 seconds