U-Boot stranger things

I have an Omnia 2020. Running strings on /dev/mtd0 I found this strange (for me) result.

    U-Boot SPL 2019.07 (Oct 08 2019 - 23:24:25 +0000)
    U-Boot
    U-Boot 2019.07 for turris_omnia 
    ** Invalid partition type "%.32s" (expect "U-Boot")
    scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
    U-Boot.armv7
    No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file.dtb>
    U-Boot
    U-Boot 2019.07 (Oct 08 2019 - 23:24:25 +0000)
    U-Boot
    scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done

What does it mean?

There is nothing strange in that. Running strings on binary file will give you all text readable STRINGS in that file. So basicaly you get all the possible text outputs of U-Boot.