BTW the newest de10 SD images are around here: https://github.com/the-snowwhite/soc-image-buildscripts
On Tue, 18 Feb 2020, 11.26 Michael Brown <[email protected]> wrote: > It's unfortunately not as simple as the frame buffer is hardwired to the > display parameters in quartus. Resolution change requires changing the FB > parameters in quartus... Generating a new bit file and then generating an > altered device tree with the new display parameters. > Michael B. > > On Tue, 18 Feb 2020, 01.22 justin White <[email protected]> wrote: > >> I know I've seen some resolution numbers in the quartus files so I >> assumed this was using part of the FPGA to do a framebuffer or something >> and it was actually part of the Quartus project. I thought the BBB actually >> had a GPU unlike the nano. I'll definitely try it when I get a chance, the >> 800x480 monitor looks like trash, even being small.....hoping to pick up >> and get this going on a 1024x600 version. >> >> I believe the de10-nano image here is the one I used >> https://drive.google.com/drive/folders/1THXnrnt-v7iNownBqmdOQrJ-i8EVAsSZ >> >> >> >> On Monday, February 17, 2020 at 5:34:07 PM UTC-5, Charles Steinkuehler >> wrote: >>> >>> I don't currently have a DE10-Nano running, but I reviewed the code and >>> it looks like you should be able to set the resolution the same as you >>> would for any other embedded display (by passing some kernel >>> parameters). Refer to: >>> >>> * The modedb documentation: >>> >>> https://www.kernel.org/doc/Documentation/fb/modedb.txt >>> >>> * My posts on setting resolutions on the BBB: >>> >>> >>> http://blog.machinekit.io/2013/06/force-beaglebone-black-hdmi-resolution.html >>> >>> http://blog.machinekit.io/2013/07/custom-hdmi-resolution.html >>> >>> I think you just need an entry similar to the following in your kernel >>> command line: >>> >>> video=800x480M@60 >>> >>> Are you using an available uSD card image? If so, I can pop it into my >>> DE10 and try to get it working with one of my small HDMI based LCD >>> screens if the above doesn't work for you. >>> >>> On 2/16/2020 7:46 PM, justin White wrote: >>> > Been away from this project for a short bit but I had a pretty good >>> use >>> > come up for it recently. Main thing I'm having a problem with is the >>> FB >>> > resolution that was configured, 1024x768 is a dead resolution. Only >>> old >>> > monitors natively support it and nothing with HDMI does. Larger HDMI >>> > monitors can handle it but nothing in the 7-9" range can display it >>> through >>> > HDMI. That's unfortunate because the main reason for FB use with this >>> thing >>> > is for an HMI all in one type device. Is there any chance more monitor >>> > resolutions can be supported? >>> > >>> > I asked this before and MB responded, but unfortunately this is over >>> my head >>> > >>> >> OK back to being able to be online with my workstation: >>> >> I have allways had a fight setting up proper display resolutions on >>> the >>> >> altera soc's however I can give you some key notes: >>> >> In qsys there are 3 cores to consider: >>> >> For display timing settings: >>> >> alt_vip_vfr_hdmi (framereader) >>> >> >>> >> alt_vip_itc_0 (Clocked video output) >>> >> >>> >> The display core clock itself: >>> >> pll_lcd --> lcd_clk >>> >> >>> >> >>> >> 1600x900 would allow me to test it out on my mill and I might have a >>> use >>> >>> for 800x480. I didn't realize the resolution was fixed, my 1080P >>> monitors >>> >>> don't have a problem displaying 1024x768, all my other monitors do. >>> I >>> >>> suppose in a real usage scenario I'd have to look further into your >>> >>> previous reply and try to figure out how to set a resolution for >>> whatever >>> >>> monitor I intended to use. >>> >> >>> >> >>> >> Sadly there are currently no presets for these 2 resolutions for the >>> >> framebuffer related cores (presets are found in qsys view menu), as I >>> >> havent had use of these resolutions m... >> >> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/machinekit/ad920189-10a0-4850-82f8-4436d5c20364%40googlegroups.com >> <https://groups.google.com/d/msgid/machinekit/ad920189-10a0-4850-82f8-4436d5c20364%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/CAGKWNWOjm%2B3X%3DnuZKr%3DiTz5Z3MK7zFQZ3WBkfTt-m%2B2povt%2BYQ%40mail.gmail.com.
