Not very easy from my cell phone here however: In qsys there are 2 instances where you set up the timings for the screen monitor. There should be some saved setups HD etc. Lastly you need to place the correct screen settings in the device tree there is a HD example there too. 1920 x1080. Sorry for not being online atm...
On Tue, 30 Jul 2019, 00.16 justin White <blazin...@gmail.com> wrote: > Yup still on the edge of understanding. dk beyond reason. I'm still on 1/2 >> gear ......... >> > > That's OK, at the moment I'm just trying to make sure the hardware works > OK for smart serial and maybe get you a little insight of the issue when > you get around to looking at it. From what I gather ClockLowTag is what > should be specified in the pinfile and ClockMed is I guess used internally > to determine SS baud rate. Seems that somewhere in the firmware SS is not > "connected", as in it should print "SmartSerial version 43" when > instantiated rather that version 0 as does when I build with it. That's > just the way I understand it so take it with a grain of salt. > > and you do know that mksocfpga only has an accelerated frame buffer and >> still no real unlicenced GPU. >> > > Yeah I know, I'm not trying to run 3D acceleration or anything, it's just > since the FB is fixed the monitor must either display 1024x768 natively or > scale it. Alot of smaller or obscure monitors don't seem to negotiate > resolutions well or at all so the server side must do it, in this case it > can't so I suppose the firmware needs to be built for whatever resolution > is needed. If you can point me in the right direction I can try to build it > myself......In the meantime I scooped up an older 4:3 LCD so I don't have > to drag a monitor I use over to my mill when I need to try something. > > I had some time so I made up a standalone test GUI. I did sort out the ADC > conversion stuff in hardware and HAL. Resistor dividers actually do work > well, I initially didn't use correct values. I used the method I mentioned > previously to scrub the 32bit integer and scale it to a useable voltage > with hal components. It actually works very well this way but has a bit of > noise. I gave a friend of mine some guidance on writing a single HAL > component that can handle the conversion as well as digitally filter the > output. I'll see how well that works before I go back and add more passives > to try to filter the noise. > > [image: remmina_DE10-Nano MK VNC_192.168.1.125_2019729-53925.864069.png] > > > > -- > 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 > machinekit+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/machinekit/dfe26639-27a7-4ba6-b9bf-344bd1d0da9e%40googlegroups.com > <https://groups.google.com/d/msgid/machinekit/dfe26639-27a7-4ba6-b9bf-344bd1d0da9e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/CAGKWNWPV48N-D8-ZEY6KgyfsOHbCt4rvhk%3D9x%3D%3D3_V%3Df-koPHA%40mail.gmail.com.
