|
| 1 | +================ |
| 2 | +ST Nucleo H723ZG |
| 3 | +================ |
| 4 | + |
| 5 | +.. tags:: chip:stm32, chip:stm32h7, chip:stm32h723 |
| 6 | + |
| 7 | +This page discusses issues unique to NuttX configurations for the |
| 8 | +STMicro Nucleo-H723ZG development board featuring the STM32H723ZG |
| 9 | +MCU. The STM32H723ZG is a up-to 550MHz Cortex-M7 operation with 1MByte Flash |
| 10 | +memory and 564KBytes of SRAM. The board features: |
| 11 | + |
| 12 | +- On-board ST-LINK/V2-1 for programming and debugging, |
| 13 | +- 3 user LEDs |
| 14 | +- Two pushbuttons (user and reset) |
| 15 | +- 32.768 kHz crystal oscillator |
| 16 | +- USB OTG HS with Micro-AB connector |
| 17 | +- Ethernet connector compliant with IEEE-802.3-2002 |
| 18 | +- Board connectors: |
| 19 | + - USB with Micro-AB |
| 20 | + - SWD |
| 21 | + - Ethernet RJ45 |
| 22 | + - ST Zio connector including Arduino Uno V3 |
| 23 | + - ST morpho |
| 24 | + |
| 25 | +Refer to the http://www.st.com website for further information about this |
| 26 | +board (search keyword: Nucleo-H723ZG) |
| 27 | + |
| 28 | +Serial Console |
| 29 | +============== |
| 30 | + |
| 31 | +Many options are available for a serial console via the Morpho connector. |
| 32 | +Here two common serial console options are suggested: |
| 33 | + |
| 34 | +1. Arduino Serial Shield. |
| 35 | + |
| 36 | + If you are using a standard Arduino RS-232 shield with the serial |
| 37 | + interface with RX on pin D0 and TX on pin D1 from USART6: |
| 38 | + |
| 39 | + ======== ========= ===== |
| 40 | + ARDUINO FUNCTION GPIO |
| 41 | + ======== ========= ===== |
| 42 | + DO RX USART6_RX PG9 |
| 43 | + D1 TX USART6_TX PG14 |
| 44 | + ======== ========= ===== |
| 45 | + |
| 46 | +2. Nucleo Virtual Console. |
| 47 | + |
| 48 | + The virtual console uses Serial Port 3 (USART3) with TX on PD8 and RX on |
| 49 | + PD9. |
| 50 | + |
| 51 | + ================= === |
| 52 | + VCOM Signal Pin |
| 53 | + ================= === |
| 54 | + SERIAL_RX PD9 |
| 55 | + SERIAL_TX PD8 |
| 56 | + ================= === |
| 57 | + |
| 58 | + These signals are internally connected to the on board ST-Link. |
| 59 | + |
| 60 | + The Nucleo virtual console is the default serial console in all |
| 61 | + configurations unless otherwise stated in the description of the |
| 62 | + configuration. |
| 63 | + |
| 64 | +Configurations |
| 65 | +============== |
| 66 | + |
| 67 | +Information Common to All Configurations |
| 68 | +---------------------------------------- |
| 69 | + |
| 70 | +Each Nucleo-H723ZG configuration is maintained in a sub-directory and |
| 71 | +can be selected as follow:: |
| 72 | + |
| 73 | + tools/configure.sh [options] nucleo-h723zg:<subdir> |
| 74 | + |
| 75 | +Where options should specify the host build platform (-l for Linux, -c for |
| 76 | +Cygwin under Windows, etc.). Try ``tools/configure.sh -h`` for the complete |
| 77 | +list of options. |
| 78 | + |
| 79 | +Before starting the build, make sure that (1) your PATH environment variable |
| 80 | +includes the correct path to your toolchain, and (2) you have the correct |
| 81 | +toolchain selected in the configuration. |
| 82 | + |
| 83 | +And then build NuttX by simply typing the following. At the conclusion of |
| 84 | +the make, the nuttx binary will reside in an ELF file called, simply, nuttx.:: |
| 85 | + |
| 86 | + make |
| 87 | + |
| 88 | +Configuration Sub-directories |
| 89 | +============================= |
| 90 | + |
| 91 | +nsh: |
| 92 | +---- |
| 93 | + |
| 94 | +This configuration provides a basic NuttShell configuration (NSH) |
| 95 | +for the Nucleo-H723ZG. The default console is the VCOM on USART3. |
| 96 | + |
| 97 | +netnsh: |
| 98 | +-------- |
| 99 | + |
| 100 | +This configuration enables support for the Ethernet and a set |
| 101 | +of networking functionalities. |
| 102 | + |
| 103 | +.. NOTE:: |
| 104 | + The initialization logic waits for Ethernet auto negotiation to complete |
| 105 | + up to a timeout. The timeout is a number of times the MII status register |
| 106 | + is read from the PHY. First to verify the link status is up, subsequently |
| 107 | + to verify the auto negotiation is complete. The timeout is set to a fixed |
| 108 | + value of ``PHY_RETRY_TIMEOUT=0x1998``. |
| 109 | + In each cycle the program waits for ``nxsched_usleep(100)``. By default |
| 110 | + this gets rounded up to the value of the tick time which is 10 ms! |
| 111 | + Therefore the time you will wait for the nsh console if the Ethernet |
| 112 | + is not plugged in is ``2 * 10 ms * 0x1998 = 130s``. |
0 commit comments