cancel
Showing results for 
Search instead for 
Did you mean: 

ST67W611M1 UART Bootloader handshake fail (Error 0050 in QConn_Flash)

Mike66
Associate

Hello,

 

I’m trying to flash the ST67W611 Wi-Fi module directly through UART, without using the NUCLEO host board.

For hardware setup, I soldered simple tactile switches and 0.1 µF capacitors on the CHIP_EN and BOOT pins.
When powering up:

  1. I press both switches to pull CHIP_EN and BOOT low (to GND).

  2. Then I release the BOOT button so that the pin is pulled up to 3.3 V through a 10 kΩ resistor.

  3. Finally, I release the CHIP_EN button, which is also pulled up to 3.3 V through another 10 kΩ resistor.

After this sequence, I run the following command in Windows PowerShell, but the handshake fails:

 

 
PS D:\Backup\STM32_Project\ST67W611M1\Resource\x-cube-st67w61\Projects\ST67W6X_Utilities\Binaries> QConn_Flash\QConn_Flash_Cmd.exe --port COM8 --config NCP_Binaries\mission_t02_flash_prog_cfg.ini --efuse=NCP_Binaries\efusedata.bin
 

Here is the full output log:

 

 
[00:05:40.891] - Serial port is COM8 [00:05:40.891] - ================================================== [00:05:40.891] - FW get address from partition file D:\Backup\STM32_Project\ST67W611M1\Resource\x-cube-st67w61\Projects\ST67W6X_Utilities\Binaries\NCP_Binaries\./partition.bin [00:05:40.891] - Address=0x10000 [00:05:40.891] - FW get size from partition file D:\Backup\STM32_Project\ST67W611M1\Resource\x-cube-st67w61\Projects\ST67W6X_Utilities\Binaries\NCP_Binaries\./partition.bin [00:05:40.891] - Size=1785856 [00:05:40.891] - Program Start [00:05:40.891] - ========= eflash loader cmd arguments ========= [00:05:40.891] - serial port is COM8 [00:05:40.891] - cpu_reset=False [00:05:41.103] - com speed: 2000000 [00:05:41.103] - ========= Interface is uart ========= [00:05:41.103] - Bootrom load [00:05:41.103] - ========= get_boot_info ========= [00:05:41.103] - ========= image get bootinfo ========= [00:05:41.384] - tx rx and power off, press the machine! [00:05:41.384] - cutoff time is 0.05 [00:05:41.447] - power on tx and rx [00:05:42.410] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1 [00:05:42.410] - clean buf [00:05:42.410] - send sync [00:05:42.526] - ack is b'' [00:05:42.526] - retry [00:05:42.809] - tx rx and power off, press the machine! [00:05:42.809] - cutoff time is 0.05 [00:05:42.876] - power on tx and rx [00:05:43.843] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1 [00:05:43.843] - clean buf [00:05:43.845] - send sync [00:05:44.061] - ack is b'7f5555555515142800ff' [00:05:44.061] - reshake [00:05:44.327] - tx rx and power off, press the machine! [00:05:44.328] - cutoff time is 0.05 [00:05:44.392] - power on tx and rx [00:05:45.345] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1 [00:05:45.345] - clean buf [00:05:45.345] - send sync [00:05:45.559] - ack is b'7d55555555541405012000ff' [00:05:45.559] - reshake [00:05:45.560] - shake hand fail [00:05:45.560] - shake hand fail [00:05:45.676] - ========= ChipID: ========= [00:05:45.676] - Get bootinfo time cost(ms:( 4572.20947265625 [00:05:45.678] - {"ErrorCode": "0050","ErrorMsg":"CHIP IMG LOAD SHAKEHAND FAIL"} [00:05:45.678] - Burn Retry [00:05:45.678] - Burn return with retry fail
 

Has anyone experienced the same issue or knows how to handle this handshake failure when flashing ST67W611 directly over UART?
Any suggestions for timing, baud rate, or pin control would be greatly appreciated.

1 REPLY 1
TarikAb
ST Employee

Hi Mike66,

This handshake failure message can occur if the CHIP_EN signal is not set high after the BOOT signal is raised.

In this case, I see that ack is always 'empty' --> ack is b''. But in your case, the first ack is empty but the subsequent ones, corresponding to the two retries, are not but are not correct --> ack is b'7f5555555515142800ff' and ack is b'7d55555555541405012000ff'

Did you observe the CHIP_EN and BOOT signals using an oscilloscope or logic analyzer?

The X-CUBE software sets CHIP_EN high 100 ms after raising BOOT.

Please confirm that your UART interface settings are as follows:

  • Full-duplex asynchronous communication
  • Data bit length: 8 bits
  • Stop bit length: 1 bit
  • Parity: None
  • Hardware flow control (RTS/CTS): None
  • Baud rate: 2,000,000 baud

Best regards,


In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.