Then in the HW divison all you need to do is add the uio-generic / hm2-uio 
ip core in qsys at address 0x0004_0000.
And then the hm2 qip (include) file wire things up and add the config stuff.

If you are working in verilog / systemverilog I made an intermediary 
upgrade of the original DE0_NANO_GHRD project adding the new firmware id 
stuff and made docker compilable before morphing it into an experimental 
CRAMPS I/O based version:

I suggest using that commit as template for adding your new (renamed) 
DE10-NANO project to MK mksocfpga @ github:

On Tuesday, 8 August 2017 18:32:05 UTC+2, mugginsac wrote:
> I got a USB OTG cable from Digikey and I am now able to boot the DE10-Nano 
> with an HDMI monitor, keyboard and mouse.
> On Tuesday, August 8, 2017 at 8:49:21 AM UTC-7, mugginsac wrote:
>> Charles,
>> I understand how ignoring HDMI to start may be easier, however, the 
>> reason that I bought the DE10 instead of the DE0 is the HDMI. :-(
>> Alan
>> On Tuesday, August 8, 2017 at 4:01:07 AM UTC-7, Charles Steinkuehler 
>> wrote:
>>> 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). 
>>> > 
>>> > 

website: blog: github:
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 
Visit this group at
For more options, visit

Reply via email to