Update RCar setup guide

Starting Apertis v2021dev3 we have full support of all ostree
capabilities as we have for SabreLite board. To support all features
U-Boot should be updated to version 2020.04+dfsg-2co5bv2022dev0b2 or
later.
Set proper links to proper U-Boot version and images in setup documentation.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

content/reference_hardware/rcar-gen3_setup.md

 +++
 date = "2019-03-14"
+lastmod = "2020-12-17"
 weight = 100
 
 title = "R-Car Hardware Setup"
@@ -15,11 +16,12 @@ aliases = [
 
 You should have at least:
 
-  - 1 suported R-car board
+  - 1 supported R-car board
   - 1 suitable Power adaptor
   - 1 USB to micro-usb cable
   - ATF /optee setup on the board and booting from the A57 CPU (See
-    manufactorer documentation on how to set this up)
+    the [documentation](https://elinux.org/R-Car/Boards/H3SK#Flashing_firmware)
+    on how to set this up)
 
 You need to provide your own:
 
@@ -27,26 +29,19 @@ You need to provide your own:
 
 ## Prepare SD card
 
-1.  Download the arm64 minimal image (for example,
-    [1](https://images.apertis.org/daily/17.03/images/minimal/arm64-generic/20170331.0/apertis-17.03-minimal-arm64-generic_20170331.0-collabora.btrfs.img.gz)),
-    plus the `.bmap` files (you can find them here,
-    [2](https://images.apertis.org/release/15.03) or You might want a
-    daily updated image. You can find it here as well
-    [3](https://images.apertis.org/daily/)), and flash the image to a
+  - Download the
+    [arm64 minimal image](https://images.apertis.org/release/v2020/v2020.3/arm64/minimal/apertis_v2020-minimal-arm64-uboot_v2020.3.img.gz),
+    plus the [`.bmap` file](https://images.apertis.org/release/v2020/v2020.3/arm64/minimal/apertis_v2020-minimal-arm64-uboot_v2020.3.img.bmap).
     microSD card using command:
-        sudo bmaptool copy path/to/image.img.gz /dev/mmcblk0
 
-Alternatively bmaptool can flash directly from http e.g. by using:
+        sudo bmaptool copy apertis_v2020-minimal-arm64-uboot_v2020.3.img.gz /dev/mmcblk0
 
-    sudo bmaptool copy https://images.apertis.org/release/v2020/v2020.0/arm64/minimal/apertis_v2020-minimal-arm64-uboot_v2020.0.img.gz /dev/mmcblk0
+    Alternatively bmaptool can flash directly from http e.g. by using:
 
-<li>
+        sudo bmaptool copy https://images.apertis.org/release/v2020/v2020.3/arm64/minimal/apertis_v2020-minimal-arm64-uboot_v2020.3.img.gz /dev/mmcblk0
 
-Put the SD card in the board
 
-</li>
-
-</ol>
+  - Put the SD card in the board
 
 ## Setup instructions
 
@@ -57,10 +52,10 @@ Renesas u-boot, as such at least u-boot needs to be updated.
 
 ### Updating U-Boot
 
-At the time of this writing most R-Car boards are still early production, this
-unfortunately means different IPL/DRAM setup versions (part of the
-arm-trusted-firmare Renesas repository) are needed for boards depending on the
-time of productions. As such Apertis doesn't currently supply builds for those
+R-Car boards are shipped with different IPL/DRAM setup versions (part of the
+[arm-trusted-firmare](https://github.com/renesas-rcar/arm-trusted-firmware)
+Renesas repository) depending on the
+time of productions. Apertis doesn't currently supply builds for those
 components (hence the requirement to already have that setup). The following
 instructions assume an IPL and Secure monitor revision newer than 1.0.10
 
@@ -90,10 +85,10 @@ The following table shows the file to get for the various types of boards:
 
 | Hardware                       | u-boot path                                                                                                                                       |
 | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| R-car Starter Kit Pro (M3)     | [m3ulcb/u-boot-elf.srec](https://images.apertis.org/release/v2021dev1/v2021dev1.0/firmware/u-boot/m3ulcb/u-boot-elf.srec)                         |
-| R-car Starter Kit Premier (H3) | [h3ulcb/u-boot-elf.srec](https://images.apertis.org/release/v2021dev1/v2021dev1.0/firmware/u-boot/h3ulcb/u-boot-elf.srec)                         |
-| R-car Salvator-X H3            | [r8a7795_salvator-x/u-boot-elf.srec](https://images.apertis.org/release/v2021dev1/v2021dev1.0/firmware/u-boot/r8a7795_salvator-x/u-boot-elf.srec) |
-| R-car Salvator-X M3            | [r8a7796_salvator-x/u-boot-elf.srec](https://images.apertis.org/release/v2021dev1/v2021dev1.0/firmware/u-boot/r8a7796_salvator-x/u-boot-elf.srec) |
+| R-car Starter Kit Pro (M3)     | [r8a7796_ulcb/u-boot-elf.srec](https://images.apertis.org/release/v2021dev3/v2021dev3.0/firmware/u-boot/r8a7796_ulcb/u-boot-elf.srec)             |
+| R-car Starter Kit Premier (H3) | [r8a7795_ulcb/u-boot-elf.srec](https://images.apertis.org/release/v2021dev3/v2021dev3.0/firmware/u-boot/r8a7795_ulcb/u-boot-elf.srec)             |
+| R-car Salvator-X H3            | [r8a7795_salvator-x/u-boot-elf.srec](https://images.apertis.org/release/v2021dev3/v2021dev3.0/firmware/u-boot/r8a7795_salvator-x/u-boot-elf.srec) |
+| R-car Salvator-X M3            | [r8a7796_salvator-x/u-boot-elf.srec](https://images.apertis.org/release/v2021dev3/v2021dev3.0/firmware/u-boot/r8a7796_salvator-x/u-boot-elf.srec) |
 
 To flash first configure the dip switches on the board to boot into the
 monitor. The exact configuration depends on the board and can be found in the
@@ -128,6 +123,12 @@ and reset the board. To do this on the boards currently availble to us:
 | Starter Kit Premier | SW6[ALL]=ON (this enables DDR3200)                       |
 | Salvator-X H3       | SW10\[5\]=ON, SW10\[6\]=ON, SW10\[7\]=OFF, SW10\[8\]=OFF |
 
+It is recommended to reset the U-Boot environment after flashing new version of bootloader.
+Stop in U-Boot prompt and execute commands:
+
+    setenv default -a
+    saveenv
+
 After reset the board should now boot Apertis from SD card automatically.
 
 ### Flashing image to eMMC
@@ -201,11 +202,11 @@ low is off).
   - In case if the boot has stopped after loading the kernel, initramfs
     and dtb with string `Starting kernel ...`
 
-Please check the values of `kernel_addr_r` and `ramdisk_addr_r` -- there
-should be enough space to load the kernel.
+    Check the values of `kernel_addr_r` and `ramdisk_addr_r` -- there
+    should be enough space to load the kernel.
 
-Probably you need to increase `ramdisk_addr_r` value to avoid
-overlapping of the kernel in memory. For example:
+    Probably you need to increase `ramdisk_addr_r` value to avoid
+    overlapping of the kernel in memory. For example:
 
-    kernel_addr_r=0x48080000
-    ramdisk_addr_r=0x4A000000
+        kernel_addr_r=0x48080000
+        ramdisk_addr_r=0x4A000000