About Mkuma.7

Mkuma.7 · 2024-01-24

Description:I am trying to build the ST project using CLI without even building it once with STMcube IDE GUI, but I am getting some warnings like 'WARNING: No Project matched ".*". Skipping..', WARNING: No Project matched "'.project'". Skipping..., ...

Mkuma.7 · 2023-08-18

When I tried to upgrade the BLE stack(v1.16.0) for the first time then am able ti upgrade it properly.Then I tried to upgrade it again it showed me the following error.

Mkuma.7 · 2023-08-18

The option bytes WRP1A_STRT = 0xFF, WRP1A_END = 0xFF, WRP1B_STRT = 0xFF and WRP1B_END = 0xFFwere programmed initially, then it got changed to WRP1A_STRT = 0xFF, WRP1A_END = 0xFF, WRP1B_STRT = 0xFF and WRP1B_END = 0xFF. I don't know when and why it...

Mkuma.7 · 2023-04-10

Via USB interface the -rst using CLI was not working and even in GUI these options were grayed out or not available. Please refer the below images for reference.Using the WB package - 1.15Using the STM32Cubeprogrammer - 2.12Is there any possible way ...

Mkuma.7 · 2023-03-31

The steps performed:First read the FUS version.Selected the FUS bin file to flash.Flashed the above-mentioned file.Then again when I read the FUS version it was displaying as 00000000 in GUI

Mkuma.7 · 2023-10-11

This became a big issue for us!!Can you guys give a proper solution for that?

Mkuma.7 · 2023-08-25

@Issamos We are eliminating the use of Cube Programmer and programming the controller via USB using STM32_Programmer_CLI.

Mkuma.7 · 2023-08-23

@Issamos The errata that you pointed out is for the STM32WL series, but we are using the STM32WB series.Will this errata holds good for WB series?

Mkuma.7 · 2023-08-22

Sry @Sarra.S --> The option bytes WRP1A_STRT = 0xFF, WRP1A_END = 0xFF, WRP1B_STRT = 0xFF and WRP1B_END = 0xFF were programmed initially using CLI. It was successfully programmed.--> But in 2 of the cases these fuses were overwritten as shown WRP1...

Mkuma.7 · 2023-06-13

@Aziz BRIGUI Is there any way via FUSES to reset the micro-controller?

User statistics

User Activity

CLI Build command

Issue in upgrading BLE stack using CLI

Some of the microcontroller options bytes were changing by itself.

Via USB interface the -rst using CLI was not working and even in GUI these options were grayed out or not available. I have tried reset=SWrst/HWrst, but it did not work. Is there any way to reset the microcontroller via USB?

In STM32 using USB1 as an interface, when I flash the FUS version and BLE stack for the first time it is able to flash, but when I repeat the same steps then am not able to read the FUS version. Can anyone help me with this issue?

Re: Some of the microcontroller options bytes were changing by itself.

Re: Some of the microcontroller options bytes were changing by itself.

Re: Some of the microcontroller options bytes were changing by itself.

Re: Some of the microcontroller options bytes were changing by itself.

Re: Via USB interface the -rst using CLI was not working and even in GUI these options were grayed out or not available. I have tried reset=SWrst/HWrst, but it did not work. Is there any way to reset the microcontroller via USB?