Questions Regarding X-NUCLEO-67W61M1 interface testing with STM32F7

[JamesLee]

Dear ST Support Team,

I attempted to test the interfacing of X-NUCLEO-67W61M1 using 32F746GDISCOVERY, but unfortunately, it did not work as expected. In order to resolve this issue, I have several questions:

I am trying to test X-NUCLEO-67W61M1 using STM32F7 instead of the sample products list(H7S3L8, H563ZI,N657X0-Q ...). From what I understand, the listed boards are simply examples for which you provide ready-made code samples, but the X-NUCLEO-67W61M1 should be interfaceable with STM32F7 as well. Is that correct?

I implemented an NCP Loader for 32F746GDISCOVERY based on the sample code for NUCLEO-H7S3L8 you provided . I also modified the batch file in an attempt to retrieve the chip info from X-NUCLEO-67W61M1, but the operation failed. Below are the batch file I used and the error message I encountered:

---------------------- execute result of batch file -----------------------------------------

[18:09:54.152] - Chipname: qcc743
[18:09:54.152] - Version: eflash_loader_v2.5.1
[18:09:54.152] - Program Start
[18:09:54.152] - ========= eflash loader cmd arguments =========
[18:09:54.152] - Config file: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeMX\local\en.x-cube-st67w61-v1.0.0\Projects\ST67W6X_Utilities\Binaries\NCP_info\chips\qcc743\eflash_loader\eflash_loader_cfg.ini
[18:09:54.157] - serial port is COM8
[18:09:54.157] - cpu_reset=False
[18:09:54.157] - chiptype: qcc743
[18:09:54.157] - ========= Interface is uart =========
[18:09:54.157] - com speed: 2000000
[18:09:54.157] - Bootrom load
[18:09:54.157] - ========= get_boot_info =========
[18:09:54.157] - ========= image get bootinfo =========
[18:09:54.174] - Not ack OK
[18:09:54.175] - result:
[18:09:54.447] - tx rx and power off, press the machine!
[18:09:54.447] - cutoff time is 0.05
[18:09:54.501] - power on tx and rx
[18:09:55.448] - reset cnt: 0, reset hold: 0.05, shake hand delay: 0.1
[18:09:55.448] - clean buf
[18:09:55.448] - send sync
[18:09:55.863] - ack is 23c33e7d2a3552bb5ef5c46980ecaa6e0ac0d2ee5363c3c3bf625fcc6d98daab0a1715cd396321f36f8b60104e72b6851db6b6775ca21460722ccc82c1ac3858b0725363834ef2d11126510fdcd67e35bdf8d8ebf2cd021d8d367ff71e948427525df3aeb4ccd353b4e56e0ae0e212c7c35103d1032644e299daab4a34134ad14bac526316da1d035072fcea74a0bc3858b0725363c3c30308b0725313d7c53798da2e0ac0f20b5351c3ebebef836beeb4ccd306511ddeb4b4ccd3dd681cf3c1c06b5ea4e39920d1e3860fafb89c7b9d63458626514cd5c1bc3858b0721c0c2644e2531df1c6d111267f2c9ceaae3e08beee5363837bc0c0801e6d4c6dae27043bdde1d1035fd309828637b8f6a0b362dd53274ee2d1112637b56037d5f220723fbc16f27253695859d10326f2c0e208eea0e212eae2e0e8e2e2e06b1a3e9ee202c6121cac72e2e37e1eb3e06b74e0ec0fab3283c4e40f83c474e07ce0fee2e20cee2d0faf338fb8e40f8bb874e0fc3c3b0f8bb81a3c9eb81a3c9eb81a3cfe12ea0ceea0e208eea0e2e2121ebca0e212ea0ceea0e208eea0e208eec7470cbd2195e2e20cee2e0f830ff00f8fb8e40f83c4e40f8bb8e40f8fb874e074e01eea121ebc21ea2ae0fee2e20ce00c6eac6fcf893c863afd0effbbd6863e1eb7e0e2e0c4e06be40f8fb8e40f3f3ce26f6fcfe2e212e9e2e2126f075baca0e208ee876fcfe20c6ef67f2e0f3f3ee26f6f4f6fcbe20c6eec6fcb893affb366de1800548b668ee09a367b63b79da0713367f6540265fb84c48e990e668ee0798404a55906679e7e489fdc6ffe84c48e9c0e668ee0798404a55906671984b089ebe073e284e44d9e8e242c01798404a55906671984b089ebe073fef3befe9e8e242d01798404a55906671984b089ebe009859ac48e9c0e668ee0798c04a55906671984b089efe072fb64188b94c63406f007fbe83dd6860b04e93becc052e084e4499e8e242c01798c04a55906dc460a1e602f73fef37c746606668ee0798404a55906dcc7081e602e52fb84e44d960830f67397be9ee48a99f06ab14fbac28725fcd3befeba03263317fcd2e48a99702eb10f489bdc88a7e2188b3303668ee0798404a55906671984b089ebe0733efbe0aa94c63406f007ffe83dc65184330f1fcc0c6ffb84e4499e8e242c01798404a5591831dccf6089996ffb84e4d29e8e242c01798c04a5590286330f1f602f27e0d3befe9e8e242c01798404a5591831dccf6089995afb84c4db5308f7ca97bf9ee48a69a284f960893ef073fed27c94338b668ee09a367b63b728cec39c32fadc6fe384e4499e8e242c01798c04a559069172821ecc0c65fcd3befe9e8e242c01798404a5591831dccf60899965fb84c48e9c0e668ee0798404a55906
[18:09:55.909] - shake hand success
[18:09:56.414] - Not ack OK
[18:09:56.414] - result:
[18:09:56.414] - get_boot_info no ok
[18:09:56.414] - change bdrate: 2000000
[18:09:56.414] - Clock PLL set
[18:09:56.414] - Retry
[18:09:56.414] - Retry
[18:09:56.414] - Retry
[18:09:56.414] - ErrorCode: 000C, ErrorMsg: QCC74X SET CLOCK PLL FAIL
[18:09:56.414] - pll set fail!!
[18:09:56.414] - Burn Retry
[18:09:56.414] - 0
[18:09:56.414] - Burn return with retry fail
[18:09:56.419] - ErrorCode: 0005, ErrorMsg: QCC74X BURN RETRY FAIL
Failed to open file: No such file or directory

--------------------------- batch file -----------------------------

........

........

........

:: Run STM32_Programmer_CLI and capture output

for /f "tokens=3" %%i in ('"STM32_Programmer_CLI.exe -c port=swd mode=ur | findstr/C:"Board""') do set BOARD_ID=%%i

if "%BOARD_ID%" == "" echo Board ID not detected && goto :error

NCP_info\QConn_Eflash.exe -r --efuse --chipname=qcc743 -p %COMADDR% --start=0x0 --end=0x1ff --file=..\flash.bin

if %ERRORLEVEL% neq 0 goto :error

NCP_info\read_chip_info.exe flash.bin

if %ERRORLEVEL% neq 0 goto :error

del flash.bin >nul

pause

exit /B

:error

echo %RED%!!!! Error detected !!!!%NC%

pause

Additionally, I'm confused about the UART RX/TX pin configuration of X-NUCLEO-67W61M. I connected STLINK_RX to pin 2 (D1/TX) and STLINK_TX to pin 1 (D1/RX) of CN9, but no data was received. When I reversed the connection, a stream of unexpected data appeared. This seems to contradict the schematic. Could you please confirm whether this is the expected behavior?

I am eager to resolve this issue and would greatly appreciate your help. If there are any points I might have overlooked, please let me know.

Best regards,

[TarikAb]

Hi James,

Let me first clarify the UART TX/RX pins assignment. As you can see in the datasheet, pin 22 is UART_TX (from ST67 to UART master) and pin 23 is UART_RX (from UART master to ST67). On the X-NUCLEO-67W61M1, module pin 22 is routed to CN9.1 and pin 23 routed on CN9.2. This means that you need to connect CN9.1 on the receive (input) pin of your UART master and CN9.2 on the transmit (output) pin of your UART master. It looks from your description above that you've got it swapped.

Regarding the software, we do indeed provide examples for a sample of MCUs but you can port the software on your preferred MCU provided that it meets the minimum requirements. Note that we're using IAR EWARM for the NCP loader project and there are two possible configurations with the same project (boot loader and UART bypass).

Best regards,

Tarik