Alan Go to the first mail in this thread and klick on open: Then will be able to navigate to the folder I have direct linked to here: https://drive.google.com/drive/folders/1LHKEyp9e5REHnqrYcpMyL0f6340UE7Iu
The folder contains the instructions I have repetedly asked you to follow exactly to the letter the first time you do it without any (of your own habitual) modifikations. And report the outcome directly back to this thread. In that same folder with the instructions is only 1 folder rev2.11 or so named This folder only contains 1 DE0xxx and 1 DE10xxx(the one with framebuffer support) sd-image, plus the 3 udated kernel .debs + a readme of how to install them(without any typos). Good luck with having success booting with framebuffer, so you then have a stable reference to fall back on if custumizing goes bad.... :-) On Saturday, 4 August 2018 05:57:25 UTC+2, mugginsac wrote: > > Michael, > > Are you talking about the 2018/05/26 stretch image? Or is there a later > one? > > What repository are the *.deb files in? > > Did you mean /boot/deb or did spell-check bite and you meant /boot/dtb ? > > Thanks, > Alan > > > On Aug 2, 2018, at 6:14 AM, Michael Brown <[email protected] > <javascript:>> wrote: > > Hi Alan > > I would like to hear an updated status: > > regarding the dtb (device tree) issue this should have been solved with > the DE10..stretch ...img provided in the shared folder plus then installing > the newer kernel .deb 's with > > sudo dpkg -i <kernel deb file namer here or *.deb> > > This should then provide the needed device tree (DE10...FB...dtb) in the > /boot/deb folder, > this dtb will then run the framebuffer and any DE10_Nano..._DB25 bitfile, > provided in the rbf bitfile .deb package online .. including > the DE10_Nano_FB_DB26.7I76_7I76_7I76_7I76.rbf. > > This bitfile needs to be loaded from u-boot before the kernel starts, AND > machinekit must then not reconfigure the fpga while the system is running: > > > No firmware load >> If you are dependent upon programming the fpga before starting Machinekit >> (ie: from u-boot before booting linux for framebuffer or similar) It is >> possible to inform the hm2_soc_ol driver to not re-program the fpga by >> issuing (already_programmed=1): >> newinst HOSTMOT2 [HOSTMOT2]DEVNAME already_programmed=1 -- config=HOSTMOT2 >> a working example of how to get this into a working .ini file is in the >> example config (5i25-soc-cramps_no-fw-load.ini) here: >> https://github.com/machinekit/machinekit/blob/master/configs/hm2-soc-stepper/5i25-soc-cramps_no-fw-load.ini > > > This will soon be in the docs :) > > > On Wednesday, 11 July 2018 01:49:30 UTC+2, mugginsac wrote: >> >> I couldn't get DE10_Nano_SoC_FB_DB25.vhd to compile without error >> (Version 17.1), it had to do with version 17.1 and the "work" library. So, >> I translated it to SystemVerilog as DE10_Nano_FB_DB25.sv. I have uploaded >> it to github/muggins branch muggins-master. I can get it to build >> DE10_Nano_FB_DB26.7I76_7I76_7I76_7I76.rbf. However, when I use it with the >> .dtb that Michael sent me it hangs up in the boot process (I believe at the >> point where it should be loading the rbf). In fact I can not reset it I >> have to power down the board to get back in to the u-boot monitor. When I >> restore the environment to point to the pair (dtb and rbf) that Michael >> sent me it boots fine. The problem with the dtb and rbf that Michael sent >> me is that it is designed to work with a 3x24... board rather than the 7I76 >> that I need. >> >> Question: I thought dtc was supposed to be able to compile a dts file >> into a dtb OR disassemble a dtb file into a dts file? I get an error when I >> try to disassemble the dtb the Michael sent me. Is this normal? >> >> Thanks, >> Alan >> > > -- > website: http://www.machinekit.io blog: http://blog.machinekit.io github: > 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. > To unsubscribe from this group and all its topics, send an email to > [email protected] <javascript:>. > Visit this group at https://groups.google.com/group/machinekit. > For more options, visit 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.
