r-car M3 show different rev version and model after u-boot flash on board.

I want to updated u-boot from 2018 to 2020.10  and I did the following steps.

 bblayers.conf :         

POKY_BBLAYERS_CONF_VERSION = "2"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
${TOPDIR}/../poky/meta \
${TOPDIR}/../poky/meta-poky \
${TOPDIR}/../poky/meta-yocto-bsp \
${TOPDIR}/../meta-renesas/meta-rcar-gen3 \
${TOPDIR}/../meta-openembedded/meta-python \
${TOPDIR}/../meta-openembedded/meta-oe \
/home/hiams_sv/workspace/renesas/yocto_5_1_0/m3ulcb/meta-rcar/meta-rcar-gen3-adas \"

Add soc family in local.conf 

# SOC family changes
SOC_FAMILY = "r8a7796"

after that I build ATF, optee and u-boot by using following command

bitbake u-boot

bitbake arm-trusted-firmware

bitbake optee-os

After that flash all required files on board by using the following steps on.

https://elinux.org/R-Car/Boards/M3SK#Flashing_firmware

after successfully flash all file I started the u-boot

it showing  R8A7796 rev3.0 and model m3ulcb based on r8a77960. but as per my understanding for this board it should be... 'r8a77961' . this is also mention at elinux page table. see the last option in below table that I have.

Why at one place it showing r8a77960  as per my board M3SK with SOC version 3 it should be r8a77961.

  • Hi Kalls,


    There is different dts files, and that might be misleading.

    There is one for Linux which indeed have to follow the table that you mentioned from eLinux, there is another dts

    which is quite similar to the Linux one but for u-boot. In this case u-boot doesn't have a specific dts for M3SKv1 and V3.

    Hope this helps

    Julien

  • Hi Kalls,

    I confirmed the same phenomenon with M3v3 SK (and H3v3 SK) in Yocto v510.

    Why at one place it showing r8a77960  as per my board M3SK with SOC version 3 it should be r8a77961.

    As you pointed out, "r8a77961" is correct.
    However, the current BSP(u-boot) is displayed as "r8a77960".
    It will be fixed in the future.

    Thank you for pointing it out.