feat(bsp): add STM32F767ZI-Nucleo board enablement verified by ThreadX demo

[alieissa-commits]

Pull Request Description

Overview

This pull request establishes a fully isolated, portable, and self-contained Board Support Package (BSP) for the STMicroelectronics STM32F767ZI-Nucleo-144 board under the STMicroelectronics/STM32F767ZI-Nucleo/ directory.

Following a modular design strategy, all build configurations, compiler flags, and target-specific drivers are completely localized. This isolates the platform from other targets, carries zero risk of namespace or library conflicts, and keeps the root workspace clean.

To verify the integration, a 4-thread real-time kernel multitasking application is implemented and fully validated.

---

Key Features

1. Isolated CMake Compilation Toolchain:

   • Localized Cortex-M7 CMake toolchain config (arm-gcc-cortex-m7.cmake) with double-precision hardware Floating Point Unit (FPU) optimizations.
   • Portable CMake discovery modules (FindCMSIS.cmake, FindSTM32HAL.cmake) linking the official, lightweight ST peripheral drivers.
   • Automated build control script (scripts/build.ps1) supporting parallel jobs.

2. Boot & Memory Configuration:

   • Physical linker mapping script (STM32F767ZITx_FLASH.ld) defining boundary zones for Flash (2MB) and SRAM (320KB).
   • Customized low-level context assembly (tx_initialize_low_level.S) mapping the ThreadX RTOS kernel to run at a system clock frequency of 216 MHz.
   • Standard vector interrupt tables (startup_stm32f767xx.s) and clock configs.

3. Peripheral Driver Adaptations:

   • Console Redirection: Configured USART3 (PD8/PD9) to redirect standard C printf outputs directly to the ST-LINK Virtual COM port.
   • Ethernet Transceiver Setup: Implemented low-level MAC initializations and DMA descriptor table allocations in SRAM for the Microchip LAN8742A PHY.

4. 4-Thread Verification RTOS Demo:

   • Thread 1 (Status Monitor): Toggles the Green LED (LD1) at 2 Hz to verify core RTOS scheduler clock ticks.
   • Thread 2 (Button Controller): Scans the user button (PC13) with debouncing and triggers the Blue LED (LD2).
   • Thread 3 (System Logger): Blocks efficiently on an RTOS Message Queue. Upon receiving a button-press packet, it prints real-time logging timestamps to the terminal.
   • Thread 4 (Interrupt-driven Console Input): Captures incoming serial keyboard input over USART3 and flashes the Red LED (LD3).

[fdesbiens]

A good start!

Please see the comments below. In particular, we must figure out the actual license for the ST code included. We should then create a NOTICE.md file at the root of the app listing the licenses applicable to the third-party code in this sample.

You can also start working on a README.md explaining what this sample / demo does and how to build / deploy the code on the target board.

[fdesbiens]

For the upcoming Q2 release, I must correct all copyright statements that add "-present" to the current year. This is a mistake I made in the Q1 release.

Please perform a search and replace and ensure that the statement in all the files you produced is:

Copyright (c) 2026 Eclipse ThreadX contributors

Of course, if files have been generated by vendor tooling, you should respect the existing notices and add our own only if you modified the file.

[fdesbiens]

The F767 relies on a Cortex-M7 MCU. Why would you use older code from the AZ3166, which relies on an M4?

The AZ3166 is a special case where we cannot touch the dependencies since we do not have the source code for the WiFi driver.

If you want up-to-date CMSIS for the F767, where will you find it?

[fdesbiens]

We also should have shell scripts for Linux.

Use Ubuntu 24.04 as your base for those.