the difference between /drivers/spi and /drivers/mtd

2019-12-10 Thread Tomek Domek
Hi I have in device tree node: qspi: somename@0 { compatible = "nameOfDriverFrom/drivers/spi"; reg = ; clocks = ; clock-names = "some names"; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; and then I have such thing: &qspi { pinctrl-names="default

Re: Missing FDT description in DTB

2019-12-06 Thread Tomek Domek
gru 2019 o 12:26 Valdis Klētnieks napisał(a): > On Fri, 06 Dec 2019 10:03:34 +0100, Tomek Domek said: > > > And this uboot and spl is somekind of experimental software which is in > > the middle of creation. Could anyone try to guide what might be possible > > the reason o

Re: Missing FDT description in DTB

2019-12-06 Thread Tomek Domek
OK I found on my own. The proper mkimage command is: ./tools/mkimage -A arm -T firmware -C none -O u-boot -a 0x10 -e 0 -n "someName" -d u-boot-dtb.bin u-boot.img without '-f auto and -E' pt., 6 gru 2019 o 10:03 Tomek Domek napisał(a): > Hi > I have FSBL

Missing FDT description in DTB

2019-12-06 Thread Tomek Domek
Hi I have FSBL and SSBL. SPL uboot starts successfully and u-boot.img is loaded successfully but it hangs on 'boot_from_devices' function and 'fit_find_config_node': fit_find_config_node: Missing FDT description in DTB No matching DT out of these options: Firmware image with one or more FDT blobs