Skip to main content
MBC
MBC
Associate III
September 28, 2023
Question

STM32H5 bootloader uses USART pins that do not match roles in datasheet

  • September 28, 2023
  • 4 replies
  • 4884 views

STM32H5763IIK, Bootloader v14

I'm planning on using USART1 and USART3 in my application. I'd like to be able to access the bootloader from both. The bootloader documents say that USART2 and USART3 at very least use pins that are not attached to their respective modules.

On the chip, USART1 can be:

TX PA9, PB6, PB14
RX PA10, PB7, PB15
The bootloader note AN2606 says the H5763 USART1 uses: A9/A10 which are valid options! No issue.

For USART3 the chip can operate on:
TX PB10, PC10, PD8
RX PB11, PC11, PC4, PD9
AN2606 says USART3 can use: None of those pairs... uses PD9 ok, but also PA4 which isn't associated to UART3 at all.

Applies to USART2 as well.

  • I've checked all of the alternate function lists and verified at least CAN and USB have seemingly correct line ups. Didn't look at SPI or I(2/3)C.

  • The only way I think this can happen is if the bootloader's code defines and uses software UART TX. Where at least the TX pins aren't driven by hardware but bit-banging out their signals. I can not imagine why this would be the case, some peripherals use the correct pins, and others do not, for software reasons?

  • As a workaround USART2, I could use RX PA3 / TX PA2 and PA5 so that when the bootloader is running it uses PA5, but in the application I use hardware an PA2. Uses an extra pin only for bootloader, and that's fine so long as I know this limitation / configuration is real.

  • I would be less surprised if the list of bootloader pins was just incorrect.

I need someone from ST to confirm that AN2602 (Page 250) matches up with reality.

AN2602: https://www.st.com/resource/en/application_note/cd00167594-stm32-microcontroller-system-memory-boot-mode-stmicroelectronics.pdf

Datasheet: https://www.st.com/resource/en/datasheet/stm32h563ii.pdf

 

 

MBC_0-1695934054198.png

 

This topic has been closed for replies.

4 replies

TDK
TDK
September 28, 2023

Almost certainly an error in AN2606, unlikely to be a software-based USART. Probably copy/pasted the H7 tables and didn't update them appropriately.

If you can boot into the bootloader, you can debug and look at GPIOx registers to see the configuration.

"If you feel a post has answered your question, please click ""Accept as Solution""."
    MBC
    MBCAuthor
    Associate III
    September 28, 2023

    Yea, it doesn't look right to me. But it's also not impossible to use software peripheral or they have some access they don't disclose maybe because of TrustZone being able to access peripherals differently. IDK.

    I do not have access to an H5 unfortunately. It would also be a bit of setup to get there, as none of the peripherals are set up for transmit until they detect a valid signal on their receive lines.

    Foued_KH
    Foued_KH
    ST Employee
    September 29, 2023

    Hello @MBC , 

    I confirm this issue in the AN2606.
    I will report that internally.

    Thank you!
    Foued

    To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
      MBC
      MBCAuthor
      Associate III
      September 29, 2023

      Ok, well good to know.

      Now I need the correct bootloader pins for USART and CAN on this series chip. I don't quite have enough information to complete this layout yet, and I need to be at least closer in order to go to purchasing for an order of chips.

      Tesla DeLorean
      Tesla DeLorean
      Guru
      September 29, 2023

      If you know this is the part, and you're just finishing up the layout, might suggest you get the order on the books. The lead time is at least 15 weeks

      Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
      Foued_KH
      Foued_KH
      ST Employee
      October 4, 2023

      I confirm the issue and I reported internally.

      Internal ticket number: 162709  (This is an internal tracking number and is not accessible or usable by customers).

      Foued

      To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
      Foued_KH
      Foued_KH
      ST Employee
      November 7, 2023

      Hello,

      Rev60 is now published with corrections : STM32 microcontroller system memory boot mode - Application note

      Foued

      To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
      Terms & ConditionsAccessibility statement