-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot flash/debug STM32WL55JC #1465
Comments
Running with
|
Try my fix at #1428 in comments. |
I'm having the exact same issue with a NUCLEO-WL55JC1 board. Also trying the latest pyocd release (v0.34.2) didn't help. Here are my logs for executing The logs indicate some permission problems, however I already installed pyocd's udev rules. As a workaround, I'm currently using the mass-storage flash method, i.e. I copy the compiled binary to the NUCLEO-WL55JC1 mass-storage device with a file manager. Afterwards, I have to unplug the board to make it reset and run the flashed program. @DariusBabrauskas what do exactly mean with "your bug fix" ? |
@niliha |
@DariusBabrauskas |
stlink_probe.py.log |
@DariusBabrauskas thanks for sharing the file. |
@niliha Is possible program your device with stmCubeProgrammer? Try different speed. |
@DariusBabrauskas Yes I can do it with STM32CubeProgrammer. Can you elaborate on the stop mode issue, i.e. how to avoid it. |
//insert this code anywhere and must be executed: |
Hello,
When trying to flash a Nucleo WL55JC1 (stm32wl55jci7u) using the command
pyocd flash --target STM32WL55JCIx --frequency 1800000 -O connect_mode=under-reset mbed-os-example-blinky.bin
I receive transfer errors. I am running the latest ST Link firmware (3.10.3) and have installed theKeil.STM32WLxx_DFP.1.1.0-small.pack
CMSIS pack for this chip usingpyocd pack install
but it is the same if I use the one bundled with Mbed Studio or one downloaded directly from CMSIS.On first attempt I get:
and on subsequent attempts I get:
Is this indicating that the pack is malformed? How do I fix this?
The text was updated successfully, but these errors were encountered: