u-boot-brain/board/eets/pdu001
Simon Glass 401d1c4f5d common: Drop asm/global_data.h from common header
Move this out of the common header and include it only where needed.  In
a number of cases this requires adding "struct udevice;" to avoid adding
another large header or in other cases replacing / adding missing header
files that had been pulled in, very indirectly.   Finally, we have a few
cases where we did not need to include <asm/global_data.h> at all, so
remove that include.

Signed-off-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Tom Rini <trini@konsulko.com>
2021-02-02 15:33:42 -05:00
..
Kconfig board: eets: pdu001: Fix wrong default value in Kconfig 2018-05-31 08:53:11 -04:00
MAINTAINERS arm: add support for PDU001 2018-01-28 12:27:32 -05:00
Makefile arm: add support for PDU001 2018-01-28 12:27:32 -05:00
README arm: add support for PDU001 2018-01-28 12:27:32 -05:00
board.c common: Drop asm/global_data.h from common header 2021-02-02 15:33:42 -05:00
board.h SPDX: Convert all of our single license tags to Linux Kernel style 2018-05-07 09:34:12 -04:00
mux.c arm: pdu001: Fix order of include files 2019-02-28 14:21:46 -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.