summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTom Rini <trini@konsulko.com>2017-12-12 11:39:33 -0500
committerTom Rini <trini@konsulko.com>2017-12-12 11:39:33 -0500
commit32c975c027bc6fc498597f4061fdb9869d5bc897 (patch)
tree80f7c575b776b42ccae8cc93ddde1fedd8a8f75c
parent1be4bfa832615f2e66f9ff517fd74befa740b3d5 (diff)
R-Car-Starter-Kit-gen3.md: Include references to firmware update
We need to have the firmware on the device updated to match the rest of the BSP. Refer to the steps listed on eLinux.org rather than duplicate this information. Bug-AGL: SPEC-1175 Signed-off-by: Tom Rini <trini@konsulko.com>
-rw-r--r--getting-started/machines/R-Car-Starter-Kit-gen3.md20
1 files changed, 18 insertions, 2 deletions
diff --git a/getting-started/machines/R-Car-Starter-Kit-gen3.md b/getting-started/machines/R-Car-Starter-Kit-gen3.md
index 1d1ad69..cc99163 100644
--- a/getting-started/machines/R-Car-Starter-Kit-gen3.md
+++ b/getting-started/machines/R-Car-Starter-Kit-gen3.md
@@ -1,4 +1,4 @@
-# AGL Kickstart on Renesas R-Car Starter Kit Gen3 V2.16 (h3ulcb, m3ulcb)
+# AGL Kickstart on Renesas R-Car Starter Kit Gen3 V2.23 (h3ulcb, m3ulcb)
Here is a non exhaustive list of hardware parts that could be used to setup the R-Car Starter Kit Gen3 board development environment:
@@ -134,13 +134,26 @@ In case of failure of the build it is safe to first check that the Linux distrib
# Booting AGL Image on R-Car Starter Kit Gen3 boards using a microSD card
-To boot the board using a micro-SD card, there are two operations that should be done prior to first initial boot:
+To boot the board using a micro-SD card, there are three operations that should be done prior to first initial boot:
+* Update all firmware on the device.
* Create a SD-card with one ext4 partition,
* Set up the board to boot on the SD-card.
Then, for each build, the SD-card is merely rewritten and used to boot the configured board.
+## Firmware Update
+
+This proceedure is done in two steps. The first step only needs to be done once per device. The second step should be done, starting with the Eel release, per release.
+
+### Update Sample Loader and MiniMonitor
+
+Follow the documentation on the [eLinux.org wiki][R-car loader update] for the exact list of steps on how to perform the required steps to update to at least version 3.02. This should be done even in the case where a **Kingfisher** or other expansion board will not be connected.
+
+### Update the firmware stack
+
+As an AArch64 platform both the **h3ulcb** and **m3ulcb** have a firmware stack that consists of multiple parts. In both cases we have **ARM Trusted Firmware**, **OP-Tee** and **U-Boot** in use. Starting with Eel you must update the firmware to at least the version referenced here. For the exact steps required to flash the device see the eLinux.org wiki for **[h3ulcb][R-car h3ulcb firmware update]** or **[m3ulcb][R-car m3ulcb firmware update]** respectively. In both cases the files listed in the table will be found in the *\$AGL_TOP/build/tmp/deploy/images/$MACHINE* directory as specified in previous steps.
+
## Prepare the SD-card on the host
Plug the microSD card and get its associated device by either running *`dmesg | tail -15`* or *`lsblk`*, for example:
@@ -618,7 +631,10 @@ Detailed guides on how to build AGL for Renesas boards and using AGL SDK inside
* [AGL Developer Website](http://docs.automotivelinux.org)
[R-car m3ulcb]: http://elinux.org/R-Car/Boards/M3SK
+[R-car m3ulcb firmware update]: https://elinux.org/R-Car/Boards/M3SK#Flashing_firmware
[R-car h3ulcb]: http://elinux.org/R-Car/Boards/H3SK
+[R-car h3ulcb firmware update]: https://elinux.org/R-Car/Boards/H3SK#Flashing_firmware
+[R-car loader update]: http://elinux.org/R-Car/Boards/Kingfisher#How_to_update_of_Sample_Loader_and_MiniMonitor
[R-car yocto]: http://elinux.org/R-Car/Boards/Yocto-Gen3
[rcar Linux Drivers]: https://www.renesas.com/solutions/automotive/rcar-demoboard.html
[rcar Linux Drivers 2]: https://www.renesas.com/en-us/solutions/automotive/rcar-demoboard-2.html