On Friday, 25 May 2018 20:14:54 UTC+2, mugginsac wrote: > > I did built a new uSD and then did the following: > setenv bitimage DE10_Nano_FB_DB25.7I76_7I76_7I76_7I76.rbf >
The bitimage variable needs to contain the full path to the *.rbf file you compiled and placed somewhere on the sd card ie: /boot/DE10_Nano_SoC_FB_DB25.rbf (this assumes you copy the current test subject file you quartus compiled from the output_files folder to /boot folder on the sd card) > > setenv fdtfile DE10_Nano_FB_DB25.7I76_7I76_7I76_7I76.dtb (renamed from > soc_system.dtb) > No no no where are you getting soc_system.dtb from ... not my instructions. You need to use a sutable kernel compiled .dtb file from the /boot/dtb folder. (name something like: DE10_Nano_FB). The exact same dtb file as named in the instructions for the demo image... OK ? > and the result was that I couldn't boot at all. > So I reset the environment to default and started over. > I set the ethaddr, hostname, saveenv and tested the boot process and I > could boot again. > Then I did > setenv bitimage DE10_Nano_FB_DB25.7I76_7I76_7I76_7I76.rbf > saveenv > and could still boot. > So the question is do I need to change the fdtfile and if so what with? > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
