cancel
Showing results for 
Search instead for 
Did you mean: 

Where are release notes for the STM32-LPM01-XN firmware?

Andrew Neil
Evangelist III

See:

https://community.st.com/s/question/0D53W00000kvhhCSAQ/xnucleolpm01a-powershield-dynamic-current-range-too-limited

At the time of starting that thread, the STM32-LPM01-XN firmware for the X-NUCLEO-LPM01A board was at v1.0.1.

I see that the STM32-LPM01-XN firmware for the X-NUCLEO-LPM01A board is now at v1.0.6.

But I can't see any Release Notes - they aren't in the downloaded Zip, and I see nothing on the Product Page:

https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-utilities/stm32-lpm01-xn.html

So the question is: where are the release notes?

1 ACCEPTED SOLUTION

Accepted Solutions
Imen.D
ST Employee

Hello @Andrew Neil​ ,

Thanks for your feedback.

That’s right, the release note is missing.

A new version v1.0.7 will be released in Q4 2021, so a public release note will be added.

In the meantime, here is the detail of FW v1.0.6:

"

FW v1.0.6:

Support of board STM32L562E-DK (firmware STM32-LPM01-XN is common to all boards: no change for board X-NUCLEO-LPM01A).

More details on boards functionalities on user manual UM2269.

"

When your question is answered, please close this topic by choosing Select as Best. This will help other users find that answer faster.

Thanks

Imen

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen

View solution in original post

7 REPLIES 7
Imen.D
ST Employee

Hello @Andrew Neil​ ,

Thanks for your feedback.

That’s right, the release note is missing.

A new version v1.0.7 will be released in Q4 2021, so a public release note will be added.

In the meantime, here is the detail of FW v1.0.6:

"

FW v1.0.6:

Support of board STM32L562E-DK (firmware STM32-LPM01-XN is common to all boards: no change for board X-NUCLEO-LPM01A).

More details on boards functionalities on user manual UM2269.

"

When your question is answered, please close this topic by choosing Select as Best. This will help other users find that answer faster.

Thanks

Imen

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen

Thanks.

@Imen DAHMEN​ : "A new version v1.0.7 will be released in Q4 2021"

Will that address the behaviour on over-current (see the linked thread) ?

That would really make it a lot more useful!

No, in fact the board X-NUCLEO-LPM01A is limited to provide 50mA.

Regarding proposal "Even if it just gave an 'out-of-range' value in the logs, that would be preferable" :

this is not possible because the maximum current is due to HW capability, if exceeding it could be damaged. This is not a matter a measurement, this is a matter of current supply.

The over-current protection mechanism is a HW mechanism, this is not related to board FW.

Imen

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen

But the static maximum is stated as 200mA - so the hardware itself must be capable of that?

usually, a power supply would go into current-limit - not just die completely?

On board X-NUCLEO-LPM01A, dynamic and static measurement circuitry are different (you can refer to user manual of board UM2243, schematic "Hardware block diagram")

In fact, Dynamic measurement circuitry is limited to 50mA (due to transistors for voltage regulation).

Static measurement circuitry is limited to 200mA.

On board STM32L562E-DK, there is only dynamic measurement circuitry, components have been upgraded to support up to 150mA.

Hope this answers your question. 

Imen

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen

I see - thanks.

Any news of the "new solution with a highest max current value" mentioned by @Richard.Chvr​  in the other thread ... ?

The schedule for this solution is under refinement, but I can't give you any target date for the moment.

When your question is answered, please close this topic by clicking "Accept as Solution".
Thanks
Imen