ST67W611M1 Hardware setup

	Back to main page

1. X-NUCLEO-67W61M1 mezzanine board overview

The X-NUCLEO-67W61M1 and the pin mapping between the NUCLEO-U575ZI-Q board and the X-NUCLEO-67W61M1 are shown in the image below.

X-NUCLEO-67W61M1 Arduino^® view

ST67W611M1 pin description:

• CHIP_EN pin is asserted to start the ST67W611M1.
• BOOT pin is asserted when a new binary must be loaded in ST67W611M1
• SPI_SCLK, SPI_MISO, and SPI_MOSI pins are used for data and control communication.
• SPI_RDY pin is asserted by the ST67W611M1 to request SPI clock.
• SPI_CS pin is used by the host to wake up the ST67W611M1.
• UART_Tx and UART_Rx are only used for loading the ST67W611M1 with mission mode (Wi-Fi^® and Bluetooth^® Low Energy) or with manufacturing (for RF testing)

Note

UART_Tx and UART_Rx are only to: flash the ST67W611M1 binaries using the QConn_Flash tool. test RF performances with the ST67W6X-RCT-TOOL

2. How to read OTP information in the ST67W611M1

The chip is preprogrammed with one-time programmable (OTP) data at the factory.

This information can be retrieved by executing the following script: \Projects\ST67W6X_Utilities\Binaries\NCP_get_chip_info.bat

NCP_get_chip_info output

3. How to run mission mode

The mission mode, also known as regular mode, features the Wi-Fi^® and Bluetooth^® Low Energy capability.

Note

Only SPI bus communication bus is used. AT commands are transported over SPI bus

The hardware set-up is shown below

Mission mode hardware setup

There are two types of architecture available (see X-CUBE-ST67W61 Architecture)

1. Legacy LWIP offload where LWIP run on the ST67W611M1. This architecture requires st67w611m_mission_t01_v2.0.89.bin binary
2. LWIP on Host where LWIP run on the Host. This architecture requires st67w611m_mission_t02_v2.0.89.bin binary

Please see How to flash the ST67W611M1 section.

For example, the ST67W6X_CLI project with st67w611m_mission_t01_v2.0.89.bin should look like this:

ST67W6X_CLI TeraTerm Screenshot

4. How to run manufacturing (MFG) mode

The manufacturing mode is used to measure RF performance of the ST67W611M1.
The following figure shows the MFG mode hardware setup.

MFG mode Hardware Setup:

Once thest67w611m_mfg_v2.0.89.bin is loaded (see How to flash the ST67W611M1), The ST67W6X-RCT-TOOL can be used to perform RF test.

ST67W6X-RCT-TOOLmanufacturing tool

5. How to flash the ST67W611M1

The ST67W611M1 network coprocessor must be loaded with a mission or manufacturing binary.

During evaluation and for the first update at the production line, the QConn_Flash tool is intended for loading the coprocessor binary.
For updates during the product's lifetime, it is possible to implement updates using AT commands over SPI interface.

5.1. Flashing the ST67W611M1 using QConn_Flash with an STM32 host

The hardware setup consists of:

• One PC running the QConn_Flash tool
• One X-NUCLEO-67W61M1
• Any host STM32 board

The interface between the boards is shown below:

ST67W611M1 flashing hardware setup:

The programming process is automated using a batch file and is completed in three steps shown in table below:

Step	Manufacturing Mode	Mission 1 Mode (LWIP running in ST67W611M1)	Mission 2 Mode (LWIP running in STM32)
Step 1: Program Bootloader in STM32	Programs Bootloader.bin in STM32	Programs Bootloader.bin in STM32	Programs Bootloader.bin in STM32
Step 2: Program ST67W611M1 Device	Programs st67w611m_mfg_v2.0.89.bin in ST67W611M1 device	Programs st67w611m_mission_t01_v2.0.89.bin in ST67W611M1 device	Programs st67w611m_mission_t02_v2.0.89.bin in ST67W611M1 device
Step 3: Program Host STM32 Application	Programs UART_bypass.bin in STM32	Programs ST67W6X_CLI.bin in STM32	Programs ST67W6X_CLI_LWIP.bin in STM32
Batch Script	NCP_update_mfg.bat	NCP_update_mission_profile_t01.bat	NCP_update_mission_profile_t02.bat

Batch scripts location:\Projects\ST67W6X_Utilities\Binaries\

Note

NUCLEO-U575ZI-Q is used as a host example in this wiki. X-CUBE-ST67W61 package contains Bootloader.bin and UART_bypass.bin for the Nucleo boards included in the package. The associated projects and source code and are located in \Projects\$BOARD_NAME\Utilities\NCP\NCP_Loader If the host board is not included in X-CUBE-ST67W61, the NCP_Loader project must be migrated to generate above mentioned binaries.

5.2. Flashing the ST67W611M1 using QConn_Flash without an STM32 host (standalone mode):

The ST67W611M1 can be flashed in standalone mode. You can typically follow this sequence:

1. Connect BOOT pin to 3.3V
2. Connect the CHIP_EN pin to 3.3V (1&2 ensures the ST67W611M1 boots in flash mode)
3. Connect your PC FTDI cable to drive UART TX and RX.
4. Open a terminal and navigate to the directory \Projects\ST67W6X_Utilities\Binaries.
5. Then, execute the following command: QConn_Flash\QConn_Flash_Cmd.exe --port COMX --config NCP_Binaries\mission_t01_flash_prog_cfg.ini --efuse=NCP_Binaries\efusedata.bin or QConn_Flash\QConn_Flash_Cmd.exe --port COMX --config NCP_Binaries\mission_t02_flash_prog_cfg.ini --efuse=NCP_Binaries\efusedata.bin

5.3. Updating the ST67W611M1 using AT commands:

It is possible to send the new firmware binary to the coprocessor using FW update APIs.
The binary can be sourced from an OTA server or even locally (e.g. from a USB).
For details on FOTA implementation, you can refer to the documentation for the available example (see Wi-Fi_ST67W6X_FOTA_Application).
Local update will use the same OTA commands, without the HTTP interface.

ST67W611M1 update paths