-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong dtb file in Arch Linux ARM image #5
Comments
Are you saying that the arch linux arm image is using the de0 dtb instead of the de10 dtb which is present in U-boot? This is intentional. I have explained the reason for doing this in this section. The short answer is, I don't believe the de10 device tree is up to date in u-boot and linux sources. But the de0 device tree seems to be in sync between the two sources. Also, the de0 device tree works great on the de10 so I'm okay to stick with it. |
Sorry, I did not see that. Just tried the image without reading docs. Excellent explanation. But should then fdtfile not point to the de0 dtb? |
The way I set it up, U-boot uses it's own device tree which defaults to the de10. U-boot is a mini OS of sorts, it needs to have a device tree as well so that the peripherals (ethernet, sdram etc) are available to it. And it bundles up the device tree separate from the kernel. In this section, we are just using the default build configuration for U-boot. This ends up using the device tree for de10. In any case, what you are seeing is just the file name. It doesn't matter as long as the device details are correct in the file :). |
There is the right name in the U-Boot environment
=> print fdtfile
fdtfile=socfpga_cyclone5_de10_nano.dtb
But the DE0 dtb file in the FAT32 partition
socfpga_cyclone5_de0_nano_soc.dtb
The text was updated successfully, but these errors were encountered: