Overview

This is the Linux BSP (Board Support Package) for the Emcraft Systems STM32F7 System-On-Module (SOM) Starter Kit.

The BSP provides a software development environment for evaluation and development of Linux (uClinux) on the Cortex-M7 processor core of the STM32F7 microcontroller using the Emcraft Systems STM32F7 SOM Starter Kit as a hardware platform.

Supported Features

The following list summarizes the features and capabilities of this release of the STM32F7 SOM Starter Kit BSP:

• Linux:
  • Kernel v4.2;
  • Serial Linux console;
  • Ethernet device driver and Linux TCP/IP networking (ping, NFS, Telnet, FTP, NTPD, etc);
  • WiFi connectivity with security;
  • PPP-based TCP/IP connectivity over GSM/3G modems;
  • Bluetooth support using bluez;
  • busybox v1.17;
  • POSIX pthreads;
  • Hardened exception handling; an exception triggered by a process affects only the offending process;
  • Secure shell (ssh) and secure copy (scp);
  • MTD-based Flash partitioning and persistent Flash file system in external Flash;
  • Multi-port serial UART driver;
  • USB Host and Device (gadget) device drivers for both the USB HS (High Speed) and USB FS (Full Speed) interfaces;
  • SD Card device driver;
  • I2C master-mode device driver;
  • SPI master-mode device driver;
  • GPIO device driver.
• U-Boot firmware:
  • U-Boot v2010.03;
  • Target initialization from power-on / reset;
  • Runs from the internal eNVM and internal SRAM (no external memory required for standalone operation);
  • Serial console;
  • Ethernet driver for loading images to the target;
  • Device driver for built-in Flash (eNVM) and self-upgrade capability;
  • Device driver for storing environment and Linux images in external Flash;
  • Autoboot feature, allowing boot of OS images from Flash or other storage with no operator intervention;
  • Persistent environment in Flash for customization of target operation;
  • Sophisticated command interface for maintenance and development of the target.
• Development tools:
  • Linux-hosted cross-development environment;
  • ARMv7-optimized GNU toolchain from CodeSourcery (2010q1) is used for development of U-Boot, Linux and user-space applications (toolchain must be downloaded separately from the CodeSourcery web site);
  • Cross GDB for debugging user-space applications;
  • Integration with Eclipse IDE;
  • mkimage tool used by the Linux kernel build process to create a bootable Linux image.

New and Changed Features

This section lists new and changed features of this release:

1. Get rid of the warning about the reg property for crtouch@0.
   ID: RM 141.
2. Port STM32F7 SOM BSP to kernel v.4.2.
   ID: RM 193.
3. Remove workaround for NOR Flash in Linux STM32F7.
   ID: RM 309.
4. MTD: use buffer writes instead of word writes.
   ID:RM 491.
5. Add support for Ethernet in Linux STM32F7 SOM BSP (kernel v.4.2).
   ID: RM 498.
6. Add support for USB HS in Linux STM32F7 SOM BSP (kernel v.4.2).
   ID: RM 499.
7. Move U-Boot environment to NOR Flash.
   ID: RM 510.
8. Add support for USB FS in Linux STM32F7 SOM BSP (kernel v.4.2).
   ID: RM 646.
9. Port RTC fix 32d56d95e3 from 2.6 kernel.
   ID: RM 413.
10. Copy-paste to serial (kernel v4.2).
    ID: RM 639.
11. Garbage in telnet sessions (kernel v4.2).
    ID: RM 640.
12. Cache state in boot logs (kernel 4.2).
    ID: RM 643.
13. rootfs: The fw_env utility is built for stm-som.
    ID: RM 730.
14. Port low-power mode support (suspend-to-RAM) to kernel 4.2.
    ID: RM 736
15. Fix SPI on STM32F7.
    ID: RM 795.
16. Support cs_change in STM32 SPI.
    ID: RM 802.
17. Fix MTD buffered writes on STM32F7.
    ID: RM 819.
18. Support STM32 GPIO interrupts.
    ID: RM 825.

Known Problems & Limitations

This section lists known problems and limitations of this release:

1. JTAG debugging rates are limited to 1 KHz.
   ID: RT 101140.
   Workaround: If you require running JTAG at higher frequencies, interrupt the Linux autoboot sequence by resetting the target and pressing any key on the serial console, thus entering the U-Boot command line interface. The Linux kernel is configured to enter a low-power mode by executing a wfi instructions whenever the system enters the so called idle loop (there are no active tasks to execute), which interferes with running JTAG at high-rate frequencies.