u-boot

History

Tom Rini 6e7df1d151 global: Finish CONFIG -> CFG migration At this point, the remaining places where we have a symbol that is defined as CONFIG_... are in fairly odd locations. While as much dead code has been removed as possible, some of these locations are simply less obvious at first. In other cases, this code is used, but was defined in such a way as to have been missed by earlier checks. Perform a rename of all such remaining symbols to be CFG_... rather than CONFIG_... Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org>		2023-01-20 12:27:24 -05:00
..
board.c	global: Finish CONFIG -> CFG migration	2023-01-20 12:27:24 -05:00
board.h	SPDX: Convert all of our single license tags to Linux Kernel style	2018-05-07 09:34:12 -04:00
Kconfig	board: eets: pdu001: Fix wrong default value in Kconfig	2018-05-31 08:53:11 -04:00
MAINTAINERS	arm: pdu001: Exend the list of maintained files	2022-02-03 12:15:34 -05:00
Makefile	arm: pdu001: Fix early debugging UART	2022-02-28 10:33:11 -05:00
mux.c	global: Move remaining CONFIG_SYS_NS16550_* to CFG_SYS_NS16550_*	2022-12-05 16:06:07 -05:00
README	arm: add support for PDU001	2018-01-28 12:27:32 -05:00

README

# Copyright (C) 2018 EETS GmbH - http://www.eets.ch/
#
# SPDX-License-Identifier: GPL-2.0+
#

Summary
=======

This document covers the PDU001 target.

Hardware
========

The PDU-001 (Processor and Display Unit) is a plugin card for 19" racks. It is
manufactured by EETS GmbH (https://www.eets.ch). The core of the board is a m2
SOM from bytes at work (https://www.bytesatwork.ch) which in turn is based on
AM3352 SOC from TI (http://www.ti.com).

Customization
=============

As usual the console serial interface is set by CONFIG_CONS_INDEX. Best choice
is 4 here since UART3 is wired to the connector K2.
The Run LED on the PDU-001 can be turned on red by setting CONFIG_RUN_LED_RED
or green by setting CONFIG_RUN_LED_GREEN. Setting CONFIG_RUN_LED_OFF will turn
off the Run LED.

Booting
=======

The system boots from either eMMC or SD card cage. It will first try to boot
from the SD card cage. If this fails (missing or unbootable SD card) it will
try to boot from the internal eMMC. The root file system is always expected to
be located in the second partition of the device (eMMC or SD card) that pro-
vided the boot loader.