Sorry Michael, I copied the .rbf to lib/firmware/socfpga and I used the full path when I did the "setenv bitimage …".
I ran make dtb on the QuartusProject. It produced soc_system.dtb and soc_system.dts in the project directory. When I did "env default -f -a" it restored the fdtfile to socfpga_cyclone5_de10_nano_fb.dtb and when I tried booting it I was able to boot again. I wish I understood what the device tree blob is accomplishes, that would make it easier to avoid these errors. I am thinking about buying a small LCD monitor say (16” 1366x768). So that I can have a monitor on the putty console at the same time I am trying to see if the de10-nano is booting into the desktop. Right now I can’t easily switch between the x86 linux desktop and the de10-nano desktop to see if I am being successful or not. When I turn off my development box and try to boot the de10-nano desktop I am not seeing anything, the monitor just reports no signal. Thanks for your patience, Alan > On May 25, 2018, at 2:03 PM, Michael Brown <mib.holotro...@gmail.com> wrote: > > > > 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 <http://www.machinekit.io/> blog: > http://blog.machinekit.io <http://blog.machinekit.io/> github: > https://github.com/machinekit <https://github.com/machinekit> > --- > You received this message because you are subscribed to a topic in the Google > Groups "Machinekit" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/machinekit/BPRQpoyvFm8/unsubscribe > <https://groups.google.com/d/topic/machinekit/BPRQpoyvFm8/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > machinekit+unsubscr...@googlegroups.com > <mailto:machinekit+unsubscr...@googlegroups.com>. > Visit this group at https://groups.google.com/group/machinekit > <https://groups.google.com/group/machinekit>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.