Michael, I built a uSD from the new image. I tried both my rbf “/lib/firmware/socfpga/DE10_Nano_FB_DB25.7I76_7I76_7I76_7I76.rbf” and the one you listed in the instructions “/lib/firmware/socfpga/DE10_Nano_FB_Cramps.3x24_Cap.rbf” I still am not getting a display from the HDMI port of the DE10_Nano. I realized that I had missed a crucial instruction earlier, I was not setting FPGA_LOAD_ON_BOOT to 1. The console looks like it is initializing the desktop according to the messages but I don’t see anything on the monitor when I turn off my development system to try and allow the DE10_Nano to control the monitor. I think Monday I will try to get an extra monitor so that each system can have its own.
Alan > On May 26, 2018, at 4:44 PM, Michael Brown <[email protected]> wrote: > > OK > > New PR stuff is now in the pipeline,,, please enjoy ... :-) > images: > https://drive.google.com/open?id=1THXnrnt-v7iNownBqmdOQrJ-i8EVAsSZ > HDMI readme: > https://drive.google.com/open?id=1rLFGJgvm_q9CqeKDvfdKwD5T9ZRUgJaY > No desktop (console version) readme: > https://drive.google.com/open?id=1goTy8C6fB2O5MGCEg_sDuG1fZVy63AsE > > > On Saturday, 26 May 2018 23:19:52 UTC+2, Michael Brown wrote: > While the former dtb file will enable the display, it will not let you run > machinekit > as the name of the uio port is not correct for machinekit use. > this mishap is now corrected in this one. > --- > I am now running the full quartus docker build, and then expect if all goes > well > to upload the 2 fresh images, reduce the instructions and push my PR in a few > hours.... > :-) > > On Saturday, 26 May 2018 19:38:07 UTC+2, Michael Brown wrote: > > > On Saturday, 26 May 2018 06:36:46 UTC+2, mugginsac wrote: > I am seeing three errors on the putty console when it starts to load the > kernel > the first says [failed] Failed to start Load Kernel Modules > the second says [failed] Failed to start iSCSI initiator daemon(iscsid) > the third says [failed] Failed to start Login to default iSCSI targets > > Those errors are not important... however: > > I think I know why you are booting to a blank screen: > > In the (former released now online) sd image the framebuffer's address was > 0x0005_0000, so that is the setting in that device tree. > I my recent work I have changed to using 0x0003_1000 for the framebuffer > address..... > > So I have attached my current version that will make the hdmi monitor work. > Copy this file to the /boot/dtb folder on you sd card overwriting the former > version. > > --- BTW > I am very close to having and updated image ready for release with: > > -- A speedier framebuffer. > -- A much more simple u boot setup. > -- no missing -dev source files,(due to being built on stretch which has a > newer qemu version than kde neon 16.04) > > > > > On May 25, 2018, at 7:11 PM, Charles Steinkuehler <[email protected] > > <>> wrote: > > > > On 5/25/2018 5:28 PM, Condit Alan wrote: > >> > >> 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. > > > > I recommend always having a UART serial terminal connected, you will > > see a lot of errors you would otherwise miss. And most of the dev > > boards (including the DE10) have a Linux console by default on the USB > > UART interface. > > > > -- > > Charles Steinkuehler > > [email protected] <> > > > > -- > > 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 > > [email protected] <>. > > 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 <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 > [email protected] > <mailto:[email protected]>. > 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 [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
