DE10 / DE0-nano-SoC U-Boot & Kernel differences(?)

I was following both descriptions
https://www.digikey.com/eewiki/display/linuxonarm/DE0-Nano-SoC+Kit
and
https://www.digikey.com/eewiki/display/linuxonarm/DE10-Nano+Kit to build system images for the respective systems.
It appears to me that the generated image is identical. The files cloned off git are the same and even the patch(es) are the same referring to the “de0_nano” and applied when building de10 image.

wget -c …/0001-de0_nano-fixes.patch
and
make ARCH=arm CROSS_COMPILE=${CC} socfpga_de0_nano_soc_defconfig

Am I missing something? The SoC chips are similar (Cyclone5) yet the CPU frequencies are different and I am not certain whether BSP preloader is aware of that if it may be responsible for setting the CPU clock(?)
On another note: I have seen some SPL preloaders reporting the clock frequencies but didn’t figure out how to enable this feature.

Hi @mates, correct when i initially created the DE10 page, i started using the DE10 specific config’s but it actually would not boot. I was only able to get it to work with the DE0 configurations… That might be fixed now in both u-boot/kernel, I believe i have both boards at home, so i’ll plan to retest pretty soon.

Regards,

Hi @RobertCNelson. Thanks for the prompt reply. That inspired me to give it a try:

export CC=/home/ubuntu/install/gcc-linaro-6.5.0-2018.12-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-
${CC}gcc -v
git clone -b v2019.07 https://github.com/u-boot/u-boot --depth=1
cd u-boot
make ARCH=arm CROSS_COMPILE=${CC} distclean
make ARCH=arm CROSS_COMPILE=${CC} socfpga_de10_nano_defconfig
make ARCH=arm CROSS_COMPILE=${CC} u-boot-with-spl.sfp
lsblk
sudo dd if=./u-boot-with-spl.sfp of=/dev/sdb1

Simply skipped the patch and specified socfpga_de10_nano_defconfig.
I took a shortcut - replacing only the contents of the custom partition (type=0xA2) and left kernel, filesystem, dtb and u-boot environment untouched. The board boots, u-boot reports
Model: Terasic DE10-Nano,
FPGA gets loaded - all seems to be working.
Am I correct thinking that the u-boot doesn’t need to be aware of the dtb (other than passing it on to the kernel) so that kernel and u-boot may be swapped (within reason) independently?
Thanks!