feat: Blues Heron (STM32U575CIT6) #2873
Conversation
zfields
force-pushed
the
zak-heron
branch
5 times, most recently
from
ac21877 to
016df1b
Compare
zfields
force-pushed
the
zak-heron
branch
10 times, most recently
from
832bf50 to
c25c5b3
Compare
|
@fpistm Does the ST Low Power Library work with the U5? All my tests are passing, except I cannot achieve Low Power using the same sketch I use on both the Cygnet and Swan. Do you see anything wrong with my board configuration that would prevent me from achieving low power? |
As far as I remember, yes it works. Anyway it is possible that a bug or a missing configuration exist. Like for the USB part. |
| Blues.menu.dbg.enable_all=Core Logs and Symbols Enabled (-g) | ||
| Blues.menu.dbg.enable_all.build.flags.debug=-g | ||
| Blues.menu.dbg.enable_sym=Symbols Enabled (-g) | ||
| Blues.menu.dbg.enable_sym.build.flags.debug=-g -DNDEBUG | ||
| Blues.menu.dbg.enable_log=Core logs Enabled | ||
| Blues.menu.dbg.enable_log.build.flags.debug= | ||
| Blues.menu.dbg.enable_all=Core Logs and Symbols Enabled (-g) | ||
| Blues.menu.dbg.enable_all.build.flags.debug=-g | ||
| Blues.menu.dbg.none=None |
There was a problem hiding this comment.
I don't recommend to change this order.
If you need to debug, the correct way is to enable the "Optimize for debugging" in the Arduino IDE menu. Then debug and symbol is activated.
Else this mean by default binary is more fat.
There was a problem hiding this comment.
In my mind, you want to start a project with debug symbols, then once you have hardened your implementation, you will either optimize for size or speed.
This follows the precedent of adding -DNDEBUG to your compilation, only after you are happy with what you've built and you are ready to release a production build.
This will also allow our users to simply press the debug button and start debugging without having to "learn" how to set it up.
That being said, if this is a STM32duino experience faux pas, and you are not asking, but telling me to change it, then I will change it, no problem.
There was a problem hiding this comment.
Only a advice. in a general case Arduino users do not debug and assume the binary is in release mode.
Anyway, that's fine for me as it only concerns Blues menu.
So keep it like this.
| | :----: | :-------: | ---- | :-----: | :---- | | ||
| | :green_heart: | STM32L4R5ZIYx | [Swan R5](https://blues.com/products/swan) | *2.1.0* | | | ||
| | :green_heart: | STM32L433CC | [Cygnet](https://blues.com/products) | *2.8.0* | | | ||
| | :yellow_heart: | STM32U575CITx | [Heron](https://blues.com/products) | *2.12.0* | | |
There was a problem hiding this comment.
| | :yellow_heart: | STM32U575CITx | [Heron](https://blues.com/products) | *2.12.0* | | | |
| | :yellow_heart: | STM32U575CITx | [Heron](https://blues.com/products) | **2.12.0** | | |
| RCC_OscInitStruct.MSIState = RCC_MSI_ON; | ||
| RCC_OscInitStruct.MSIClockRange = RCC_MSIRANGE_0; // 100 kHz initially (will be overridden later) | ||
| RCC_OscInitStruct.MSICalibrationValue = RCC_MSICALIBRATION_DEFAULT; | ||
| RCC_OscInitStruct.HSI48State = RCC_HSI48_ON; // Critical for USB |
There was a problem hiding this comment.
Only if you left the CLK48 clk mux by default (HSI48).
As in your case you do not used PLL the only way is effectively HSI48 or maybe set MSK at 48000.
github-project-automation
bot
moved this from In progress
to Needs review
in STM32 core based on ST HAL
2 participants
No description provided.