last rpi-update broke my raspbian-ua-netinst(doesn't boot anymore) #572

trulio · 2016-03-22T19:54:26Z

last rpi-update broke my raspbian-ua-netinst(doesn't boot anymore)

pelwell · 2016-03-22T20:19:39Z

Which model of Pi do you have?

What are the symptoms?

trulio · 2016-03-23T08:22:27Z

Rpi2

trulio · 2016-03-23T08:23:03Z

Yellow led blink once at boot then nothing

trulio · 2016-03-23T08:24:42Z

I replaced manually prevoious 4.1.20 boot files and it worked. There is an issue with yesterday's update.

pelwell · 2016-03-23T09:12:09Z

So far you are the only person to report a problem with the update, so either your installation failed in some way or there is something different about your setup.

What is is in your config.txt and cmdline,txt?

trulio · 2016-03-23T17:27:28Z

here are the files content:
config.txt:
#[pi2]
#kernel=vmlinuz-3.18.0-trunk-rpi2
#initramfs initrd.img-3.18.0-trunk-rpi2 followkernel
gpu_mem=16
#arm_freq=800
#core_freq=250
#sdram_freq=400
#over_voltage=0
dtparam=i2c_arm=off
dtparam=spi=off
device_tree=
start_x=0

cmdline.txt:
dwc_otg.lpm_enable=0 kgdboc=ttyAMA0,115200 console=tty1 elevator=deadline root=/dev/mmcblk0p2 rootfstype=ext4 rootwait

pelwell · 2016-03-23T18:00:49Z

With a similar configuration I can repeat the boot failure. It's going to take a while to fully diagnose this - not before tomorrow - but I can see that the mmc driver is unhappy.

You are booting with Device Tree disabled (and yet using dtparam to try and disable things that are already disabled by default - double futility) - that isn't going to be supported on 4.4 and beyond. Why not remove that device_tree= line and see what happens.

trulio · 2016-03-23T18:46:23Z

ok lets do it

trulio · 2016-03-23T19:57:34Z

it works as you said.

pelwell · 2016-03-23T20:16:07Z

That's a useful data point, and it gives you a work-around for now and a potential path to 4.4.

I'll investigate the problem anyway, though.

pelwell · 2016-03-24T12:18:12Z

Adding the enable_uart setting changed the dependencies between various parts of the system. In resolving those dependencies, by allowing a more flexible initialisation sequence, one dependency was missed - that of the emmc clock on the core clock. Fortunately it is simple to put that dependency back, and the next firmware will do that. Sorry for the inconvenience.

trulio · 2016-03-24T12:46:47Z

Thanks but it was not a convenience.
I could have tried to solve the problem without noticing.
But I wanted to raise up the bug as a contribution to the community.
So thanks to you for your hard work.

See: #572 firmware: arm_loader: Remove emmc_pll_core and init_emmc_clock as they are not recommended to be changed

See: raspberrypi/firmware#572 firmware: arm_loader: Remove emmc_pll_core and init_emmc_clock as they are not recommended to be changed

pelwell · 2016-03-24T12:59:58Z

The master firmware branch has now been updated.

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: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> --- v2: - Fix Kconfig syntax error. - Update required VC FW commit ID to cover MMC fix too.

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: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> --- v2: - Fix Kconfig syntax error. - Update required VC FW commit ID to cover MMC fix too.

This allows U-Boot to known the name of the board. The existing rpi_2_defconfig can operate correctly on the Raspberry Pi 3 in 32-bit mode /if/ you have configured the firmware to use the PL011 UART as the console UART (the default is the mini UART). This requires two things: a) config.txt should contain dtoverlay=pi3-miniuart-bt b) You should run the following to tell the VC FW to process DT when booting, and copy u-boot.bin.img (rather than u-boot.bin) to the SD card as the kernel image: path/to/kernel/scripts/mkknlimg --dtok u-boot.bin u-boot.bin.img This works as of firmware.git commit 046effa13ebc "firmware: arm_loader: emmc clock depends on core clock See: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> --- v2: Enhance the commit description to contain complete details re: how to run rpi_2_defconfig on a Raspberry Pi 3.

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: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> --- v2: - Fix Kconfig syntax error. - Update required VC FW commit ID to cover MMC fix too.

inspector71 · 2016-03-25T06:25:16Z

FYI I had the same experience on my RPi2: wouldn't boot after upgrading to the latest firmware, re-applied previous firmware and it booted again as normal.

trulio · 2016-03-25T09:36:38Z

Thanks to pelwell. everything is OK with the update
(but i must add that i modified my config files to match the default recommanded configuration now)

This allows U-Boot to known the name of the board. The existing rpi_2_defconfig can operate correctly on the Raspberry Pi 3 in 32-bit mode /if/ you have configured the firmware to use the PL011 UART as the console UART (the default is the mini UART). This requires two things: a) config.txt should contain dtoverlay=pi3-miniuart-bt b) You should run the following to tell the VC FW to process DT when booting, and copy u-boot.bin.img (rather than u-boot.bin) to the SD card as the kernel image: path/to/kernel/scripts/mkknlimg --dtok u-boot.bin u-boot.bin.img This works as of firmware.git commit 046effa13ebc "firmware: arm_loader: emmc clock depends on core clock See: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: Enhance the commit description to contain complete details re: how to run rpi_2_defconfig on a Raspberry Pi 3.

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: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: - Fix Kconfig syntax error. - Update required VC FW commit ID to cover MMC fix too.

This allows U-Boot to known the name of the board. The existing rpi_2_defconfig can operate correctly on the Raspberry Pi 3 in 32-bit mode /if/ you have configured the firmware to use the PL011 UART as the console UART (the default is the mini UART). This requires two things: a) config.txt should contain dtoverlay=pi3-miniuart-bt b) You should run the following to tell the VC FW to process DT when booting, and copy u-boot.bin.img (rather than u-boot.bin) to the SD card as the kernel image: path/to/kernel/scripts/mkknlimg --dtok u-boot.bin u-boot.bin.img This works as of firmware.git commit 046effa13ebc "firmware: arm_loader: emmc clock depends on core clock See: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: Enhance the commit description to contain complete details re: how to run rpi_2_defconfig on a Raspberry Pi 3.

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: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: - Fix Kconfig syntax error. - Update required VC FW commit ID to cover MMC fix too.

This allows U-Boot to known the name of the board. The existing rpi_2_defconfig can operate correctly on the Raspberry Pi 3 in 32-bit mode /if/ you have configured the firmware to use the PL011 UART as the console UART (the default is the mini UART). This requires two things: a) config.txt should contain dtoverlay=pi3-miniuart-bt b) You should run the following to tell the VC FW to process DT when booting, and copy u-boot.bin.img (rather than u-boot.bin) to the SD card as the kernel image: path/to/kernel/scripts/mkknlimg --dtok u-boot.bin u-boot.bin.img This works as of firmware.git commit 046effa13ebc "firmware: arm_loader: emmc clock depends on core clock See: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: Enhance the commit description to contain complete details re: how to run rpi_2_defconfig on a Raspberry Pi 3.

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: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: - Fix Kconfig syntax error. - Update required VC FW commit ID to cover MMC fix too.

This allows U-Boot to known the name of the board. The existing rpi_2_defconfig can operate correctly on the Raspberry Pi 3 in 32-bit mode /if/ you have configured the firmware to use the PL011 UART as the console UART (the default is the mini UART). This requires two things: a) config.txt should contain dtoverlay=pi3-miniuart-bt b) You should run the following to tell the VC FW to process DT when booting, and copy u-boot.bin.img (rather than u-boot.bin) to the SD card as the kernel image: path/to/kernel/scripts/mkknlimg --dtok u-boot.bin u-boot.bin.img This works as of firmware.git commit 046effa13ebc "firmware: arm_loader: emmc clock depends on core clock See: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]>

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: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]>

This allows U-Boot to known the name of the board. The existing rpi_2_defconfig can operate correctly on the Raspberry Pi 3 in 32-bit mode /if/ you have configured the firmware to use the PL011 UART as the console UART (the default is the mini UART). This requires two things: a) config.txt should contain dtoverlay=pi3-miniuart-bt b) You should run the following to tell the VC FW to process DT when booting, and copy u-boot.bin.img (rather than u-boot.bin) to the SD card as the kernel image: path/to/kernel/scripts/mkknlimg --dtok u-boot.bin u-boot.bin.img This works as of firmware.git commit 046effa13ebc "firmware: arm_loader: emmc clock depends on core clock See: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: Enhance the commit description to contain complete details re: how to run rpi_2_defconfig on a Raspberry Pi 3.

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: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: - Fix Kconfig syntax error. - Update required VC FW commit ID to cover MMC fix too.

This allows U-Boot to known the name of the board. The existing rpi_2_defconfig can operate correctly on the Raspberry Pi 3 in 32-bit mode /if/ you have configured the firmware to use the PL011 UART as the console UART (the default is the mini UART). This requires two things: a) config.txt should contain dtoverlay=pi3-miniuart-bt b) You should run the following to tell the VC FW to process DT when booting, and copy u-boot.bin.img (rather than u-boot.bin) to the SD card as the kernel image: path/to/kernel/scripts/mkknlimg --dtok u-boot.bin u-boot.bin.img This works as of firmware.git commit 046effa13ebc "firmware: arm_loader: emmc clock depends on core clock See: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: Enhance the commit description to contain complete details re: how to run rpi_2_defconfig on a Raspberry Pi 3.

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: raspberrypi/firmware#572". Signed-off-by: Stephen Warren <[email protected]> Reviewed-by: Tom Rini <[email protected]> --- v2: - Fix Kconfig syntax error. - Update required VC FW commit ID to cover MMC fix too.

See: raspberrypi#572 firmware: arm_loader: Remove emmc_pll_core and init_emmc_clock as they are not recommended to be changed

pelwell mentioned this issue Mar 23, 2016

Boot issues with the latest firmware #574

Closed

swarren mentioned this issue Mar 24, 2016

Property mbox get_clock_rate for eMMC returning 0 in recent firmware #575

Closed

popcornmix added a commit that referenced this issue Mar 24, 2016

firmware: arm_loader: emmc clock depends on core clock

046effa

See: #572 firmware: arm_loader: Remove emmc_pll_core and init_emmc_clock as they are not recommended to be changed

popcornmix added a commit to Hexxeh/rpi-firmware that referenced this issue Mar 24, 2016

firmware: arm_loader: emmc clock depends on core clock

37f187c

See: raspberrypi/firmware#572 firmware: arm_loader: Remove emmc_pll_core and init_emmc_clock as they are not recommended to be changed

swarren mentioned this issue Mar 25, 2016

Raspberry Pi 3 model B Serial console does not use correct baudrate #553

Closed

popcornmix closed this as completed Mar 25, 2016

swarren mentioned this issue Apr 3, 2016

64-bit boot stub? #579

Closed

XECDesign pushed a commit to RPi-Distro/firmware that referenced this issue May 4, 2016

firmware: arm_loader: emmc clock depends on core clock

02a1a4c

See: raspberrypi#572 firmware: arm_loader: Remove emmc_pll_core and init_emmc_clock as they are not recommended to be changed

neuschaefer pushed a commit to neuschaefer/raspi-binary-firmware that referenced this issue Feb 27, 2017

firmware: arm_loader: emmc clock depends on core clock

52269dd

See: raspberrypi#572 firmware: arm_loader: Remove emmc_pll_core and init_emmc_clock as they are not recommended to be changed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

last rpi-update broke my raspbian-ua-netinst(doesn't boot anymore) #572

last rpi-update broke my raspbian-ua-netinst(doesn't boot anymore) #572

trulio commented Mar 22, 2016

pelwell commented Mar 22, 2016

trulio commented Mar 23, 2016

trulio commented Mar 23, 2016

trulio commented Mar 23, 2016

pelwell commented Mar 23, 2016

trulio commented Mar 23, 2016

pelwell commented Mar 23, 2016

trulio commented Mar 23, 2016

trulio commented Mar 23, 2016

pelwell commented Mar 23, 2016

pelwell commented Mar 24, 2016

trulio commented Mar 24, 2016

pelwell commented Mar 24, 2016

inspector71 commented Mar 25, 2016

trulio commented Mar 25, 2016

last rpi-update broke my raspbian-ua-netinst(doesn't boot anymore) #572

last rpi-update broke my raspbian-ua-netinst(doesn't boot anymore) #572

Comments

trulio commented Mar 22, 2016

pelwell commented Mar 22, 2016

trulio commented Mar 23, 2016

trulio commented Mar 23, 2016

trulio commented Mar 23, 2016

pelwell commented Mar 23, 2016

trulio commented Mar 23, 2016

pelwell commented Mar 23, 2016

trulio commented Mar 23, 2016

trulio commented Mar 23, 2016

pelwell commented Mar 23, 2016

pelwell commented Mar 24, 2016

trulio commented Mar 24, 2016

pelwell commented Mar 24, 2016

inspector71 commented Mar 25, 2016

trulio commented Mar 25, 2016