Wondering about commenys On Thu, 2 May 2019, 17.02 <[email protected]> wrote:
> Hi Justin > > The DE10_Nano_FB_Cramps.3x24_cap.rbf bitfile is as the name implies > designed to interface with a Cramps board and provide a framebuffer onthe > hdmi pins of the DE10 Nano. > I have created an Interface board for interfacing the DExx Nano (soc) > boards to the Cramps and > the design files are here: > > https://github.com/the-snowwhite/socfpga-kicad/tree/master/Cramps2nano-soc > > https://github.com/the-snowwhite/socfpga-kicad/blob/master/Cramps2nano-soc/Cramps2Nano.pdf > > This shows the pins of the DExx Gpio pins and can be easiely bread boarded. > > The cap sensor is not part of Cramps functionality so these pins are not > on that schematic... > > -- > About the "SOC-no-fw-load" config method: > > This makes Machinekit not reprogram the fpga when MACHINEKIT starts... > correct > > The "fpgaload_on_boot 1" in u-boot makes u-boot program the fpga BEFORE > linux starts up so that the Framebuffer then can be picked up, > > Ensure that the right devicetree (the one with framebuffer enabled) is > loaded by u-boot. > > Really I'm just looking to breadboard an encoder interface and level >> shifting circuits and get some feedback from MK as to how the GPIO is >> responding at this point >> > > Coincendentially I have just purchased an encoder: > E6B2-CWZ6C > > And will be doing the same exercise currently it seems... :-) > > While it may be possible to hook up this encoder to some gpio pins and > then run a "soft" encoder in the hal, > the Mesa Hostmot2 cores do provide Encoder cores that can be run in the > fpga HW fabric, this meens a new config has to be added to the > DE10_Nanoxxx_FBxxxx Quartus project in the Mksocfpga repo > > http://www.machinekit.io/docs/drivers/hostmot2/#encoder > > > On Wednesday, 1 May 2019 04:33:52 UTC+2, justin White wrote: >> >> So I picked up a DE10 Nano to do some testing on. As I explained in a >> previous thread, a remote GUI running on a different CPU is the intended >> goal with the DE10-Nano handling MK and the hardware headless as I'm sure >> most would intend it's use. I'm having all sorts of issues with just about >> everything MachineKit but this I got somewhere with. >> >> I need to work on making an interface board to get useable I/O out of >> this thing for my intended purpose. I found the >> "DE10-Nano/mksocfpga_stretch_machinekit_4.9.76-2018-05-26-de10_nano_desktop_sd.img" >> and got that setup with HDMI support and LXqt. The thought is that If I can >> get a working GUI setup going with a more or less generic bitfile I can >> basically breadboard the DE10-Nano and use HalShow and a few other LinuxCNC >> tools to verify the circuits. I ran into a couple of issues and there's >> some things I'm unsure of.... >> >> I tried what sounded like a more ideal bitimage but the HDMI output was >> no good unless I used >> the /lib/firmware/socfpga/DE10_Nano_FB_Cramps.3x24_cap.rbf bitimage. I >> couldn't find info on what the pin designations for this image are, I'm not >> really up to snuff on the 3D-printer/CRAMPS thing. I'm not really sure of >> how to create my own bitfile either especially if it's tied to the HDMI out. >> >> I did load MK and the only stock config I could get to load was the >> something "SOC-no-fw-load" config. I assume this does not reprogram the >> FPGA on start since the "fpgaload_on_boot 1" variable is set to program the >> FPGA on boot? Since I have no hardware to attach I can't really say whether >> the I/O was actually doing anything although I guess I would expect >> following errors or something if it wasn't while I was jogging around. I >> also couldn't start Halshow from the Axis GUI, just didn't open. It'd be >> great if somebody could point me in the right direction as to how I can >> either setup my own hardware bitfile or use a rather generic one that I can >> reference pin designations too. Really I'm just looking to breadboard an >> encoder interface and level shifting circuits and get some feedback from MK >> as to how the GPIO is responding at this point. >> > -- > 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/eVhvTnuhblE/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. > 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/CAGKWNWPEW2UfY16d1EdpADtEmNxRAu17ota_uQ4yf79_VuPstA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
