Can't get code running on NUCLEO_WL55JC

[hallard]

Description of defect

Nucleo WL55JC board is recognized and can be flashed without any issue but once flashed, any program does not seems to start, I tested blinky also without any success.

Target(s) affected by this defect ?

NUCLEO_WL55JC

Toolchain(s) (name and version) displaying this defect ?

GNU Arm Embedded Toolchain 10-2020-q4-major 10.2.1 20201103 (release)
GNU Arm Embedded Toolchain 10.3-2021.07) 10.3.1 20210621 (release)

What version of Mbed-os are you using (tag or sha) ?

mbed-os-99.99.99

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

mbed studio V1.4.1
mbed-tools 7.27.0

How is this defect reproduced ?

From mbed ide New Program then mbed-os-example-blinky then plug NUCLEO_WL55JC with USB and select as target (it's auto detected) then click on run program This compile, then flash, then nothing.

From mbed CLI2

mbed-tools import mbed-os-example-blinky
cd mbed-os-example-blinky
mbed-tools compile -m NUCLEO_WL55JC -t GCC_ARM --flash

This compile, then flash, then nothing either

Don't know if it's related #14185 or #14236 but if someone has this board in hand, would be interested by a try, I first thought it was related from my office NUCLEO WL55 board, but tested at home with another one (and another computer), same thing (both received last week from mouser).

I tried on old B-L072Z-LRWAN1 and worked like a charm, so I suspect something strange on WL55JC.
Pay attention that I'm working on LoRa-E5 and RAK3172 (STM32WL Family also) without any issue but they are single core cortex M4, not dual core as WL55JC

Output of command line (partial)

[232/232] Linking CXX executable mbed-os-example-blinky.elf
-- built: /Users/charles/Mbed Programs/mbed-os-example-blinky/cmake_build/NUCLEO_WL55JC/develop/GCC_ARM/mbed-os-example-blinky.bin
-- built: /Users/charles/Mbed Programs/mbed-os-example-blinky/cmake_build/NUCLEO_WL55JC/develop/GCC_ARM/mbed-os-example-blinky.hex
| Module           |         .text |       .data |        .bss |
|------------------|---------------|-------------|-------------|
| [fill]           |       72(+72) |       4(+4) |     24(+24) |
| [lib]/c.a        |   4964(+4964) | 2108(+2108) |     58(+58) |
| [lib]/gcc.a      |     772(+772) |       0(+0) |       0(+0) |
| [lib]/misc       |     188(+188) |       4(+4) |     28(+28) |
| main.cpp.obj     |       48(+48) |       0(+0) |       0(+0) |
| mbed-os/cmsis    |   6944(+6944) |   168(+168) | 6208(+6208) |
| mbed-os/drivers  |     138(+138) |       0(+0) |       0(+0) |
| mbed-os/hal      |   1552(+1552) |       8(+8) |   114(+114) |
| mbed-os/platform |   5544(+5544) |   260(+260) |   424(+424) |
| mbed-os/rtos     |       32(+32) |       0(+0) |       0(+0) |
| mbed-os/targets  | 10306(+10306) |       8(+8) |   688(+688) |
| Subtotals        | 30560(+30560) | 2560(+2560) | 7544(+7544) |
Total Static RAM memory (data + bss): 10104(+10104) bytes
Total Flash memory (text + data): 33120(+33120) bytes

Copied /Users/charles/Mbed Programs/mbed-os-example-blinky/cmake_build/NUCLEO_WL55JC/develop/GCC_ARM/mbed-os-example-blinky.bin to 1 device(s).

[jeromecoutant]

Quick tests:

• build with CLI1 commands with ARM and GCC => OK
• build with CLI2 commands with ARM and GCC => blinky application doesn't blink...

[jeromecoutant]

Same issue with another random board... (NUCLEO_L552ZE_Q) :-(

mbed-tools 7.32.0

[jeromecoutant]

This issue should maybe be duplicated to https://github.com/ARMmbed/mbed-tools/issues ?

@Patater @0xc0170

[0xc0170]

It's fine to keep it here, I'll add this to the core project.

[0xc0170]

Same issue with another random board... (NUCLEO_L552ZE_Q) :-(

Can you git bisect to find when it broke?

[jeromecoutant]

I can't find any working version :-(

It's working with DISCO_L475VG_IOT01A

[hallard]

I wanted to try with mbed-cli (CLI1) so I plugged the nucleo on my USB cable and guess what, now the board is blinking (I did not done anything yet since yesterday), just amazing I did not flashed the board since last flash that was not working.
I'm wondering is something is not preventing board to start (reset line, boot pin, ...)

So tried same thing than yesterday (with clean)

mbed-tools compile -c -m NUCLEO_WL55JC -t GCC_ARM --flash

now works (until when? that's the $1 000 000 question), this is a very strange behavior

[hallard]

@jeromecoutant did you updated the embedded STlink firmware of your Nucleo boards?

[jeromecoutant]

@jeromecoutant did you updated the embedded STlink firmware of your Nucleo boards?

Yes:

$ mbedtools detect
Board name     Serial number             Serial port    Mount point(s)    Build target(s)    Interface Version
-------------  ------------------------  -------------  ----------------  -----------------  -------------------
NUCLEO-WL55JC  003600235553500a20393256  COM8           D:                NUCLEO_WL55JC      V3J8M3

After more tests, I agree there is some random issues... I flash application several times and/or unplug/plug the boards. Sometimes blink is started, sometimes not... :-(

@schstm

[hallard]

After more tests, I agree there is some random issues... I flash application several times and/or unplug/plug the boards. Sometimes blink is started, sometimes not... :-(

Yeah same thing here, to be sure it's not working, flash with mbed ide and board won't start, then flashed back with CLI2 works all time (today because it was not yesterday)

I'll try something later, build and flash with mbed ide then power the board with 3.3V only removing all USB/STlink Stage just to see. I'm pretty sure it's not related to compiled code (yesterday board was not working plugged this morning and started) but to specific starting GPIO pin, USB stuff or console lock