Flashing original firmware onto STEVAL-DPS334M1 chip for the STEVAL-DPSTPFC1

[zeid1719]

Howdy,

I’m running into an issue trying to re-flash the original code onto the control board (STEVAL-DPS334M1, which uses the STM32F334R8T6 MCU) for the ST totem-pole PFC board (STEVAL-DPSTPFC1).

I’m using an ST-Link V2 with STM32CubeProgrammer to download the provided .bin file of the original control code back onto the board. The download completes successfully, but when I power the PFC board afterward, nothing happens. Normally, the PFC board has a startup sequence before the user can enable it, but now that sequence does not occur.

When I check device memory in STM32CubeProgrammer, I see that the first data location is at address 0x08000000 (screenshot attached). This makes me wonder if I also need a bootloader file for it to work. If so, where would I obtain it?

For reference, the original firmware I received from ST came as a zip file containing:

• Drivers folder

• EWRAM folder (which had the .bin file, no .hex included)

• Inc folder

• Src folder

• .mxproject file

• .ioc file

Backstory:
I originally tried modifying the code to change the switching frequency and flashed that version to the board. When it didn’t work, I attempted to restore the original code by flashing the provided .bin file. Despite the “download complete” message, the board no longer behaves as expected. To confirm the board itself isn’t bricked, I tested with a simple LED blink program and that ran successfully.

Any guidance on whether a bootloader is required, or if I’m missing a step in restoring the firmware, would be greatly appreciated.

Thanks in advance!

[Peter BENSCH]

Welcome @zeid1719, to the community!

Please note that you have posted your question in the public Community. However, the firmware was provided to you by the personal Online Support OLS upon signing an SLA. Therefore no one here in the community will be able to answer your questions, so please open a new ticket in OLS and refer to your old ticket number 00235149. Please also include photos of the front and back of the ST-LINK/V2 to that ticket so that our colleagues can check whether it is an original.

A side note: all Cortex-M-based MCUs start at address 0x08000000, so there is no error in this regard.

Regards
/Peter

[zeid1719]

Hey Peter,

Thanks for the clarification, the guidance, and the warm welcome.

I also appreciate you bringing the SLA restriction to my attention. The reason I initially posted here is because when I opened a new ticket in OLS for assistance, I was advised to post my question in the forum due to the technical nature of the issue. Should I go ahead and remove my post to make sure I’m not in violation of the SLA agreement?

Regarding the ST-Link/V2, I purchased it from Mouser, so it should be authentic. It has successfully connected to the control card and was able to program it, as shown in the screenshot I attached to the post.

And if it is not because of the boot loader file, then what else could it be in your opinion?

Best regards,
Zeid

[Peter BENSCH]

Since in a few cases the source code is only released against SLA, as mentioned, the personal OLS will have to help you instead of the community. Please point this fact out to them if they want to send you back here.

Only a moderator can delete the post; you can only edit it. However, it can remain here because it does not yet contain any relevant confidential information.

The ST-LINK/V2-ISOL looks original; at least, I have not come across any fakes that look the same.

Regards
/Peter