stbenn opened a new pull request, #14813:
URL: https://github.com/apache/nuttx/pull/14813

   The PLL clock configuration was simplified on the assumption the clocks are 
correctly set in the board.h file. Instead of seperate conditions for register 
components, assume the relevant PLL registers are fully defined in board.h. 
This should result in easier to understand defines in board.h and simpler code 
flow in the standard clock configuration function.
   
   Changes were mad in the board file alongside changing the arch files. 
Changes to board/stm32h5:
     - PLL1 has been configured to use integer instead of fractional mode to 
reach the 250 MHz target. PLL2 and PLL3 configurations were removed since they 
are currently unused in the H5 configuration.
     - PLL1 output was verified by testing for changes in serial baud rate.
   
   *Note: Please adhere to [Contributing 
Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).*
   
   ## Summary
   
   This change is primarily to make it easier to configure PLL clocks when 
working with peripherals. It followed the H7 `board.h` practice of fully 
defining each register.
   
   ## Impact
   
   This makes PLL clock setup easier in `board.h`, and will make it easier for 
peripherals to be configured based off the PLL configuration. This change 
continues to assume clocks must be set up properly in `board.h`
   
   ## Testing
   
   Changes in the system clock would be detected by a change in baud rate on 
the serial com port. After the changes, the serial com port continued to work 
at the intended baud rate and the board booted to the nutshell. 
   
   Host OS: Ubuntu 24.04 on WSL 2 (Windows 11)
   Compiler: arm-none-eabi-gcc (15:13.2.rel1-2) 13.2.1 20231009
   
   Target:
   - Arch: STM32H5
   - Chip: STM32H563ZIT6U
   - Board: Nucleo-H563ZI
   - Config: nucleo-h563zi:nsh
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to