Load commands were working fine, as I shared in screenshot too. It properly reads all bytes. And moreover if I undo the change, it still gives the issue.
I can't say for sure, but looks like it might be the device partition number only.
I would be more than happy to know if you have an explanation for the same.
I have compiled my own. Can you tell which flags it could be regarding USB support?
In my .config USB_EHCI_HCD is enabled under USB Host Controller Drivers.
What all needs to be enabled?
Thanks.
Comments
Maybe its the partition number at which u-boot is expecting the kernel image and fdt
That isn't how it works. Maybe your load commands never succeeded in the first place previously.
I can't say for sure, but looks like it might be the device partition number only.
I would be more than happy to know if you have an explanation for the same.
I just noted that board can't identify any usb devices when connected to any usb type A port.
Following is the screenshot of dmesg error.
Are you using the standard kernel or did you ocmpile your own? If you are compiling your own, you are probably missing flags.
In my .config USB_EHCI_HCD is enabled under USB Host Controller Drivers.
What all needs to be enabled?
Thanks.
Please check the existing config file from /proc/config.gz of our images or Google it.
okay, I'll check.
Thanks.
I checked your image file but /proc directory of those images are empty.
Which config.gz are you referring to?
Please Google. This is getting into Linux basic questions that are already answered.
Okay, I'll try to resolve it.
Thanks