rpi: BCM2837 and Raspberry Pi 3 32-bit support
The Raspberry Pi 3 contains a BCM2837 SoC. The BCM2837 is a BCM2836 with
the CPU complex swapped out for a quad-core ARMv8. This can operate in 32-
or 64-bit mode. 32-bit mode is the current default selected by the
VideoCore firmware on the Raspberry Pi 3. This patch adds a 32-bit port of
U-Boot for the Raspberry Pi 3.
>From U-Boot's perspective, the only delta between the RPi 2 and RPi 3 is a
change in usage of the SoC UARTs. On all previous Pis, the PL011 was the
only UART in use. The Raspberry Pi 3 adds a Bluetooth module which uses a
UART to connect to the SoC. By default, the PL011 is used for this purpose
since it has larger FIFOs than the other "mini" UART. However, this can
be configured via the VideoCore firmware's config.txt file. This patch
hard-codes use of the mini UART in the RPi 3 port. If your system uses the
PL011 UART for the console even on the RPi 3, please use the RPi 2 U-Boot
port instead. A future change might determine which UART to use at
run-time, thus allowing the RPi 2 and RPi 3 (32-bit) ports to be squashed
together.
The mini UART has some limitations. One externally visible issue in the
BCM2837 integration is that the UART divides the SoC's "core clock" to
generate the baud rate. The core clock is typically variable, and under
control of the VideoCore firmware for thermal management reasons. If the
VC FW does modify the core clock rate, UART communication will be
corrupted since the baud rate will vary from the expected value. This was
not an issue for the PL011 UART, since it is fed by a fixed 3MHz clock. To
work around this, the VideoCore firmware can be told not to modify the SoC
core clock. However, the only way this can happen and be thermally safe is
to limit the core clock to a low/minimum frequency. This leaves
performance on the table for use-cases that don't care about a UART
console. Consequently, use of the mini UART console must be explicitly
requested by entering the following line into config.txt:
enable_uart=1
A recent version of the VC firmware is required to ensure that the mini
UART is fully and correctly initialized by the VC FW; at least
firmware.git 046effa13ebc "firmware: arm_loader: emmc clock depends on
core clock See: https://github.com/raspberrypi/firmware/issues/572".
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
2016-03-25 04:15:20 +00:00
|
|
|
CONFIG_ARM=y
|
2021-08-28 01:18:30 +00:00
|
|
|
CONFIG_SKIP_LOWLEVEL_INIT=y
|
2019-08-14 13:29:25 +00:00
|
|
|
CONFIG_ARCH_CPU_INIT=y
|
rpi: BCM2837 and Raspberry Pi 3 32-bit support
The Raspberry Pi 3 contains a BCM2837 SoC. The BCM2837 is a BCM2836 with
the CPU complex swapped out for a quad-core ARMv8. This can operate in 32-
or 64-bit mode. 32-bit mode is the current default selected by the
VideoCore firmware on the Raspberry Pi 3. This patch adds a 32-bit port of
U-Boot for the Raspberry Pi 3.
>From U-Boot's perspective, the only delta between the RPi 2 and RPi 3 is a
change in usage of the SoC UARTs. On all previous Pis, the PL011 was the
only UART in use. The Raspberry Pi 3 adds a Bluetooth module which uses a
UART to connect to the SoC. By default, the PL011 is used for this purpose
since it has larger FIFOs than the other "mini" UART. However, this can
be configured via the VideoCore firmware's config.txt file. This patch
hard-codes use of the mini UART in the RPi 3 port. If your system uses the
PL011 UART for the console even on the RPi 3, please use the RPi 2 U-Boot
port instead. A future change might determine which UART to use at
run-time, thus allowing the RPi 2 and RPi 3 (32-bit) ports to be squashed
together.
The mini UART has some limitations. One externally visible issue in the
BCM2837 integration is that the UART divides the SoC's "core clock" to
generate the baud rate. The core clock is typically variable, and under
control of the VideoCore firmware for thermal management reasons. If the
VC FW does modify the core clock rate, UART communication will be
corrupted since the baud rate will vary from the expected value. This was
not an issue for the PL011 UART, since it is fed by a fixed 3MHz clock. To
work around this, the VideoCore firmware can be told not to modify the SoC
core clock. However, the only way this can happen and be thermally safe is
to limit the core clock to a low/minimum frequency. This leaves
performance on the table for use-cases that don't care about a UART
console. Consequently, use of the mini UART console must be explicitly
requested by entering the following line into config.txt:
enable_uart=1
A recent version of the VC firmware is required to ensure that the mini
UART is fully and correctly initialized by the VC FW; at least
firmware.git 046effa13ebc "firmware: arm_loader: emmc clock depends on
core clock See: https://github.com/raspberrypi/firmware/issues/572".
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
2016-03-25 04:15:20 +00:00
|
|
|
CONFIG_ARCH_BCM283X=y
|
2022-10-21 00:22:39 +00:00
|
|
|
CONFIG_TEXT_BASE=0x00008000
|
2021-11-01 12:19:22 +00:00
|
|
|
CONFIG_TARGET_RPI_3_32B=y
|
2018-08-16 12:16:24 +00:00
|
|
|
CONFIG_NR_DRAM_BANKS=1
|
2023-02-17 14:58:06 +00:00
|
|
|
CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=y
|
|
|
|
|
CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x7ffff00
|
2020-08-10 19:31:07 +00:00
|
|
|
CONFIG_ENV_SIZE=0x4000
|
2020-07-28 12:46:52 +00:00
|
|
|
CONFIG_DEFAULT_DEVICE_TREE="bcm2837-rpi-3-b"
|
2023-05-01 15:50:26 +00:00
|
|
|
CONFIG_OF_LIBFDT_OVERLAY=y
|
2021-08-23 14:25:31 +00:00
|
|
|
CONFIG_SYS_LOAD_ADDR=0x1000000
|
2023-07-27 21:54:28 +00:00
|
|
|
CONFIG_BOOTSTD_DEFAULTS=y
|
rpi: BCM2837 and Raspberry Pi 3 32-bit support
The Raspberry Pi 3 contains a BCM2837 SoC. The BCM2837 is a BCM2836 with
the CPU complex swapped out for a quad-core ARMv8. This can operate in 32-
or 64-bit mode. 32-bit mode is the current default selected by the
VideoCore firmware on the Raspberry Pi 3. This patch adds a 32-bit port of
U-Boot for the Raspberry Pi 3.
>From U-Boot's perspective, the only delta between the RPi 2 and RPi 3 is a
change in usage of the SoC UARTs. On all previous Pis, the PL011 was the
only UART in use. The Raspberry Pi 3 adds a Bluetooth module which uses a
UART to connect to the SoC. By default, the PL011 is used for this purpose
since it has larger FIFOs than the other "mini" UART. However, this can
be configured via the VideoCore firmware's config.txt file. This patch
hard-codes use of the mini UART in the RPi 3 port. If your system uses the
PL011 UART for the console even on the RPi 3, please use the RPi 2 U-Boot
port instead. A future change might determine which UART to use at
run-time, thus allowing the RPi 2 and RPi 3 (32-bit) ports to be squashed
together.
The mini UART has some limitations. One externally visible issue in the
BCM2837 integration is that the UART divides the SoC's "core clock" to
generate the baud rate. The core clock is typically variable, and under
control of the VideoCore firmware for thermal management reasons. If the
VC FW does modify the core clock rate, UART communication will be
corrupted since the baud rate will vary from the expected value. This was
not an issue for the PL011 UART, since it is fed by a fixed 3MHz clock. To
work around this, the VideoCore firmware can be told not to modify the SoC
core clock. However, the only way this can happen and be thermally safe is
to limit the core clock to a low/minimum frequency. This leaves
performance on the table for use-cases that don't care about a UART
console. Consequently, use of the mini UART console must be explicitly
requested by entering the following line into config.txt:
enable_uart=1
A recent version of the VC firmware is required to ensure that the mini
UART is fully and correctly initialized by the VC FW; at least
firmware.git 046effa13ebc "firmware: arm_loader: emmc clock depends on
core clock See: https://github.com/raspberrypi/firmware/issues/572".
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
2016-03-25 04:15:20 +00:00
|
|
|
CONFIG_OF_BOARD_SETUP=y
|
2023-10-02 17:58:20 +00:00
|
|
|
CONFIG_FDT_SIMPLEFB=y
|
2019-07-21 02:51:14 +00:00
|
|
|
CONFIG_USE_PREBOOT=y
|
2024-01-03 14:26:16 +00:00
|
|
|
CONFIG_SYS_PBSIZE=1049
|
2016-10-08 18:41:44 +00:00
|
|
|
# CONFIG_DISPLAY_CPUINFO is not set
|
2016-10-12 01:33:46 +00:00
|
|
|
# CONFIG_DISPLAY_BOARDINFO is not set
|
2020-10-09 16:22:06 +00:00
|
|
|
CONFIG_MISC_INIT_R=y
|
2023-10-02 14:35:27 +00:00
|
|
|
CONFIG_SYS_PROMPT="U-Boot> "
|
rpi: BCM2837 and Raspberry Pi 3 32-bit support
The Raspberry Pi 3 contains a BCM2837 SoC. The BCM2837 is a BCM2836 with
the CPU complex swapped out for a quad-core ARMv8. This can operate in 32-
or 64-bit mode. 32-bit mode is the current default selected by the
VideoCore firmware on the Raspberry Pi 3. This patch adds a 32-bit port of
U-Boot for the Raspberry Pi 3.
>From U-Boot's perspective, the only delta between the RPi 2 and RPi 3 is a
change in usage of the SoC UARTs. On all previous Pis, the PL011 was the
only UART in use. The Raspberry Pi 3 adds a Bluetooth module which uses a
UART to connect to the SoC. By default, the PL011 is used for this purpose
since it has larger FIFOs than the other "mini" UART. However, this can
be configured via the VideoCore firmware's config.txt file. This patch
hard-codes use of the mini UART in the RPi 3 port. If your system uses the
PL011 UART for the console even on the RPi 3, please use the RPi 2 U-Boot
port instead. A future change might determine which UART to use at
run-time, thus allowing the RPi 2 and RPi 3 (32-bit) ports to be squashed
together.
The mini UART has some limitations. One externally visible issue in the
BCM2837 integration is that the UART divides the SoC's "core clock" to
generate the baud rate. The core clock is typically variable, and under
control of the VideoCore firmware for thermal management reasons. If the
VC FW does modify the core clock rate, UART communication will be
corrupted since the baud rate will vary from the expected value. This was
not an issue for the PL011 UART, since it is fed by a fixed 3MHz clock. To
work around this, the VideoCore firmware can be told not to modify the SoC
core clock. However, the only way this can happen and be thermally safe is
to limit the core clock to a low/minimum frequency. This leaves
performance on the table for use-cases that don't care about a UART
console. Consequently, use of the mini UART console must be explicitly
requested by entering the following line into config.txt:
enable_uart=1
A recent version of the VC firmware is required to ensure that the mini
UART is fully and correctly initialized by the VC FW; at least
firmware.git 046effa13ebc "firmware: arm_loader: emmc clock depends on
core clock See: https://github.com/raspberrypi/firmware/issues/572".
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
2016-03-25 04:15:20 +00:00
|
|
|
CONFIG_CMD_GPIO=y
|
2017-08-14 23:58:53 +00:00
|
|
|
CONFIG_CMD_MMC=y
|
|
|
|
|
CONFIG_CMD_USB=y
|
2018-10-23 13:35:52 +00:00
|
|
|
CONFIG_CMD_FS_UUID=y
|
2017-09-08 14:14:49 +00:00
|
|
|
CONFIG_OF_EMBED=y
|
2017-08-28 11:16:32 +00:00
|
|
|
CONFIG_ENV_FAT_DEVICE_AND_PART="0:1"
|
2019-11-13 03:46:36 +00:00
|
|
|
CONFIG_SYS_RELOC_GD_ENV_ADDR=y
|
2018-04-01 16:37:53 +00:00
|
|
|
CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG=y
|
2021-05-12 08:03:04 +00:00
|
|
|
CONFIG_TFTP_TSIZE=y
|
2022-03-22 01:33:30 +00:00
|
|
|
CONFIG_BCM2835_GPIO=y
|
2016-12-07 13:10:28 +00:00
|
|
|
CONFIG_MMC_SDHCI=y
|
2016-12-07 13:10:29 +00:00
|
|
|
CONFIG_MMC_SDHCI_BCM2835=y
|
2018-04-08 00:27:54 +00:00
|
|
|
CONFIG_PHYLIB=y
|
2018-02-11 01:27:45 +00:00
|
|
|
CONFIG_PINCTRL=y
|
|
|
|
|
# CONFIG_PINCTRL_GENERIC is not set
|
2016-09-08 20:11:59 +00:00
|
|
|
# CONFIG_REQUIRE_SERIAL_CONSOLE is not set
|
2021-04-12 13:38:52 +00:00
|
|
|
CONFIG_SYSINFO=y
|
|
|
|
|
CONFIG_SYSINFO_SMBIOS=y
|
2016-09-08 20:31:26 +00:00
|
|
|
CONFIG_USB=y
|
2017-07-03 16:30:06 +00:00
|
|
|
CONFIG_USB_DWC2=y
|
2016-10-18 02:13:01 +00:00
|
|
|
CONFIG_USB_KEYBOARD=y
|
2017-08-28 08:50:45 +00:00
|
|
|
CONFIG_USB_HOST_ETHER=y
|
2018-04-08 00:27:54 +00:00
|
|
|
CONFIG_USB_ETHER_LAN78XX=y
|
2017-08-28 08:50:46 +00:00
|
|
|
CONFIG_USB_ETHER_SMSC95XX=y
|
2022-10-18 13:46:31 +00:00
|
|
|
CONFIG_VIDEO=y
|
2020-02-04 21:43:06 +00:00
|
|
|
# CONFIG_VIDEO_BPP8 is not set
|
|
|
|
|
# CONFIG_VIDEO_BPP16 is not set
|
2017-04-27 04:27:57 +00:00
|
|
|
CONFIG_SYS_WHITE_ON_BLACK=y
|
2022-01-23 14:04:14 +00:00
|
|
|
CONFIG_VIDEO_BCM2835=y
|
2016-11-29 14:14:57 +00:00
|
|
|
CONFIG_CONSOLE_SCROLL_LINES=10
|
rpi: BCM2837 and Raspberry Pi 3 32-bit support
The Raspberry Pi 3 contains a BCM2837 SoC. The BCM2837 is a BCM2836 with
the CPU complex swapped out for a quad-core ARMv8. This can operate in 32-
or 64-bit mode. 32-bit mode is the current default selected by the
VideoCore firmware on the Raspberry Pi 3. This patch adds a 32-bit port of
U-Boot for the Raspberry Pi 3.
>From U-Boot's perspective, the only delta between the RPi 2 and RPi 3 is a
change in usage of the SoC UARTs. On all previous Pis, the PL011 was the
only UART in use. The Raspberry Pi 3 adds a Bluetooth module which uses a
UART to connect to the SoC. By default, the PL011 is used for this purpose
since it has larger FIFOs than the other "mini" UART. However, this can
be configured via the VideoCore firmware's config.txt file. This patch
hard-codes use of the mini UART in the RPi 3 port. If your system uses the
PL011 UART for the console even on the RPi 3, please use the RPi 2 U-Boot
port instead. A future change might determine which UART to use at
run-time, thus allowing the RPi 2 and RPi 3 (32-bit) ports to be squashed
together.
The mini UART has some limitations. One externally visible issue in the
BCM2837 integration is that the UART divides the SoC's "core clock" to
generate the baud rate. The core clock is typically variable, and under
control of the VideoCore firmware for thermal management reasons. If the
VC FW does modify the core clock rate, UART communication will be
corrupted since the baud rate will vary from the expected value. This was
not an issue for the PL011 UART, since it is fed by a fixed 3MHz clock. To
work around this, the VideoCore firmware can be told not to modify the SoC
core clock. However, the only way this can happen and be thermally safe is
to limit the core clock to a low/minimum frequency. This leaves
performance on the table for use-cases that don't care about a UART
console. Consequently, use of the mini UART console must be explicitly
requested by entering the following line into config.txt:
enable_uart=1
A recent version of the VC firmware is required to ensure that the mini
UART is fully and correctly initialized by the VC FW; at least
firmware.git 046effa13ebc "firmware: arm_loader: emmc clock depends on
core clock See: https://github.com/raspberrypi/firmware/issues/572".
Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Tom Rini <trini@konsulko.com>
2016-03-25 04:15:20 +00:00
|
|
|
CONFIG_PHYS_TO_BUS=y
|
