On Mon, Apr 29, 2019 at 4:36 PM rafael mello <[email protected]> wrote: > > Hello Simon, > > Adding the "clock-frequency = <100000000>;" line to the dts file solved the > issue,
Great to hear that. I'll post a patch to fix that. > But I had found another solution before reading your repply. > There is one dtsi file missing for the de10 nano board, the file should be > named > "socfpga_cyclone5_de10_nano-u-boot.dtsi" and it's content should be the same > as > the "socfpga_cyclone5_de0_nano_soc-u-boot.dtsi". Not exactly. There are "u-boot.dtsi" files for devicetrees copied by Linux. It's a make automatism to ensure we can use unmodified Linux devicetress and add U-Boot specific changes in different files. However, the de10 board does not exist in Linux, so there's no point in splitting U-Boot specific code to a "u-boot.dtsi" file since the whole devicetree is U-Boot specific. Regards, Simon > For some reason the "*-u-boot.dtsi" files are loaded even whan not called in > the dts file, > and the clock-frequency definition was in that file for all the cyclone5 > boards, except for > the de10 nano. Creating the file made the board follow the current > pattern/standard and > solved the issue. > Maybe a patch is required. > > I'm attaching the socfpga_cyclone5_de10_nano-u-boot.dtsi file and the > socfpga_cyclone5_de10_nano.dts files > > Thank you very much for the help, even with the solution that I found, I > failed to see that the clock-frequency was the real issue. > > Best regards, > Rafael Villatore _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
