Yes, it would be much easier to load a single FPGA image via U-Boot
rather than deal with partial reconfiguration.

I was planning on just ignoring the HDMI to start.  :)

On 8/7/2017 11:05 PM, Michael Brown wrote:
> BTW
> It may be possible to boot configuring the fpga from u-boot with framebuffer 
> and 
> hm2 cores and then start machinekit hm2_soc_ol driver without 
> firmware=xxx.dtbo 
> for easy DE10-Nano fb startup. (uio driver then needs a uio entty in dts also 
> to 
> load).
> 
> 
> On Tuesday, 8 August 2017 00:40:22 UTC+2, Michael Brown wrote:
> 
>     I would like to insert some notes from my own experiments with the DE10 
> Nano:
> 
>     I you use the terasic supplied reference project as base you will need to
>     customize the device tree --> dtb
>     as the qsys system uses different addresses / bridges for the fpga ip 
> cores.
> 
>     they can boot with identical u-boot and root file system. (without hdmi,
>     piece of cake...)
> 
>     If you want to use the hdmi as local xserver xorg based display things 
> get a
>     bit more intrigant:
>     To be able to use the alt_vip fb core + alt_vipfb.c driver (which keeps
>     pooping in and out of the kernel, and also has been obsoleted after 
> quartus
>     v.16.1).
>     You have to program the fpga from uboot with at least the alt_vip
>     framebuffer qsys core and also have it in the devicetree so the the kernel
>     is ale to pick it up and initialize it when it boot. (also remember to 
> make
>     sure the bridges are offhanded by uboot before starting the kernel, if you
>     keep getting a blank screen after boot and /dev/fb0 is there).
> 
>     THe intrigant part is then that when machinekit reloads the fpga chances 
> are
>     the framebuffer may go haywire, so the most elegant solution would be to
>     create a partitioned 2 rev design with one containing only the qsys 
> system +
>     a rev 2 containing also the mesa hdl hostmot2 stuff behind a bridge.
> 
>     This can the be loaded via a partial reconfiguration .dtbo much like the
>     ones currently used except that is does not reconfigure the whole fpga but
>     only adds / replaces the Mk Hostmot2 mesa cores.
>     ---
>     I hope this is clear and understandable....
>     ---
>     I am atm tied up in finishing adding commits for a cramps based atlas soc
>     version with functional adc and some more to MK, before I can turn more
>     focus to DE10.NANO, for now I can only point towards my own socfpga
>     build-scripts on the-snowwhite@github which also contains all the elements
>     needed for generating a stretch image with hdmi and 4.9-rt kernet
>     framebuffer rootfs, u-boot etc initially made to create the first working
>     mksocfpga demo.
> 
>     Best Wishes Michael
> 
> 
> 
>     On Saturday, 5 August 2017 18:41:08 UTC+2, Charles Steinkuehler wrote:
> 
>         Since there seems to be interest, I've gone ahead and ordered a
>         DE10-Nano so I can do real-world tests.
> 
>         I don't have lots of free time right now, but I ought to at least be
>         able to help get a bootable uSD card image generated (if no one beats
>         me to it) and migrate the DE0 project for the hostmot2 VHDL code to
>         the DE10.
> 
>         -- 
>         Charles Steinkuehler
>         cha...@steinkuehler.net
> 
> -- 
> 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 
> <mailto:machinekit+unsubscr...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
> 


-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to