STMicroelectronics / STM32CubeL4

STM32Cube MCU Full Package for the STM32L4 series - (HAL + LL Drivers, CMSIS Core, CMSIS Device, MW libraries plus a set of Projects running on all boards provided by ST (Nucleo, Evaluation and Discovery Kits))
Other
259 stars 151 forks source link

dsiPllInit.PLLNDIV too large for 32L4R9IDISCOVERY board #55

Closed Gallium70 closed 2 years ago

Gallium70 commented 2 years ago

Describe the set-up

Describe the bug The display on the screen seems compressed vertically, and bottom 2/3 of the display remains black.

dsi125

How To Reproduce

  1. Compile and upload BSP Example ; The bug is also reproducible using DSI Example

  2. Change PLLNDIV to 100, then the display works fine. (For the DSI example, it's located here ) dsi100

  3. If change PLLNDIV to 95, then about 1/5 bottom of the display remains black.

dsi95

I suspect that the default 125 PLLNDIV is not able to generate a clock speed high enough for the display.

Edit: I checked CubeMX and found that PLLNDIV is a multiplier instead of a divider, so maybe it's rather overclocked.

RKOUSTM commented 2 years ago

Hi @Gallium70,

First we would like to thank you for your report.

We tried to reproduce the issue you described, but we couldn't notice the problem.

Could you please confirm you are using the latest firmware v1.17.1 version and that the issue is systematically reproducible on your side?

Thank you again for your report.

With regards,

Gallium70 commented 2 years ago

Hi @RKOUSTM ,

Thanks for your reply.

At the time I posted this issue, the latest stable firmware version was v1.17.0. I have two l4r9i-disco boards and both of them could reproduce the issue then. The one in the picture stopped working several days ago though, so I can only try on the other board now.

I will try with v1.17.1 to see if the issue still exists.

Best regards,

RKOUSTM commented 2 years ago

Hi @Gallium70,

I hope you are fine. Any new feedback regarding this issue?

With regards,

Gallium70 commented 2 years ago

Hi @RKOUSTM ,

I tried with a CubeMX generated Makefile project and programmed the board using CubeProgrammer, then everything works fine, with both v1.17.0 and v1.17.1. However, the issue still exists when using PlatformIO IDE, so maybe it's something related to PIO? But PIO should be using firmware code (v1.17.0) from this repo directly. That's weird.

Thanks for your help. I'll close this issue for now.

Best regards,