upstream u-boot with additional patches for our devices/boards:
https://lists.denx.de/pipermail/u-boot/2017-March/282789.html (AXP crashes) ;
Gbit ethernet patch for some LIME2 revisions ;
with SPI flash support
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Stefan Roese
b48dcd3751
|
7 years ago | |
|---|---|---|
| .. | ||
| acpi | ||
| .gitignore | 9 years ago | |
| Kconfig | 7 years ago | |
| MAINTAINERS | 7 years ago | |
| Makefile | ||
| README | 8 years ago | |
| conga-qeval20-qa3.c | 7 years ago | |
| dsdt.asl | ||
| start.S | ||
README
------------------------------
U-Boot console UART selection:
------------------------------
The U-Boot port for this congatec board currently supports two different
configurations (defconfig files). The only difference is the UART that
is used as the U-Boot console UART. The default defconfig file:
conga-qeval20-qa3-e3845_defconfig
provides this console on the UART0 which is provided via a Winbond
Super-IO chip connected on the congatec Qseven 2.0 evaluation carrier
board (conga-QEVAL). This UART is the one provided with a SubD9
connector on the mainboard (the low one). The 2nd defconfig file:
conga-qeval20-qa3-e3845-internal-uart_defconfig
provides the U-Boot console on the BayTrail internal legacy UART,
which is routed from the QSeven SoM to the X300 connector on the
baseboard. Here is called COM2. The baseboard already provides the
RS232 level shifters. So a TTL-USB UART adapter does not work in
this case. The signals need to get connected directly to the
RS232 level signals of the PC UART via some adapter cable.