[U-Boot] Nvidia Trega Tk1 - /cpus/cpu@0 missing clock-frequency property

Hi,
Currently I am working on an Nvidia Jetson Tk1 board.
With u-boot v2016.05 I am seeing the following messages on the start up
[ 0.000000] Tegra clk 127: register failed with -17 [ 0.004488] /cpus/cpu@0 missing clock-frequency property [ 0.008002] /cpus/cpu@1 missing clock-frequency property [ 0.013406] /cpus/cpu@2 missing clock-frequency property [ 0.018751] /cpus/cpu@3 missing clock-frequency property [ 0.879130] +USB0_VBUS_SW: Failed to request enable GPIO108: -517 [ 0.883400] reg-fixed-voltage regulators:regulator@7: Failed to register regulator: -517 [ 0.891700] +5V_USB_HS: Failed to request enable GPIO109: -517 [ 0.897438] reg-fixed-voltage regulators:regulator@8: Failed to register regulator: -517 [ 0.905852] +1.05V_RUN_AVDD_HDMI_PLL: Failed to request enable GPIO63: -517 [ 0.912605] reg-fixed-voltage regulators:regulator@11: Failed to register regulator: -517 [ 0.920982] +5V_HDMI_CON: Failed to request enable GPIO86: -517 [ 0.926818] reg-fixed-voltage regulators:regulator@12: Failed to register regulator: -517 [ 0.935194] +5V_SATA: Failed to request enable GPIO242: -517 [ 0.940771] reg-fixed-voltage regulators:regulator@13: Failed to register regulator: -517 [ 0.949148] +12V_SATA: Failed to request enable GPIO242: -517 [ 0.954811] reg-fixed-voltage regulators:regulator@14: Failed to register regulator: -517 [ 2.740489] tegra-xusb-padctl 7009f000.padctl: failed to setup XUSB ports: -517 [ 2.757663] tegra-pcie 1003000.pcie-controller: Failed to get supply 'avddio-pex': -517 [ 2.784372] serial-tegra serial@70006000: failed to get alias id, errno -19 [ 2.791460] serial-tegra serial@70006040: failed to get alias id, errno -19
I am not sure about what's the issue here. Google search shows something might be missing in the device tree. Can you let me know whats the issue here.
Mit Freundlichen Grüßen VinothKumar

On 08/12/2016 03:15 AM, vinoth eswaran wrote:
Hi,
Currently I am working on an Nvidia Jetson Tk1 board.
With u-boot v2016.05 I am seeing the following messages on the start up
...
I am not sure about what's the issue here. Google search shows something might be missing in the device tree. Can you let me know whats the issue here.
The DTB file that's passed to the kernel should be the DTB file built along with the kernel binary. If you're already doing that, and there are still problems, I suggest discussing this on the Tegra kernel mailing list; those messages are all kernel messages and nothing to do with U-Boot.
(BTW, the -517 messages aren't actually errors; they're expected behaviour when a device attempts to initialize and the dependencies it needs are not yet available. The initialization will be retried later and should succeed then).
participants (2)
-
Stephen Warren
-
vinoth eswaran