Charles, The DE10 won’t boot from the DE0-Nano-SOC MachineKit image. I need to get an adapter for USB female to Micro male (or USB OTG) so I can plug in my powered USB hub or at the very least a USB keyboard with built in touch pad.
I guess I will try to set up so I can compile on the DE10-nano. The only linux box I have in the house is an i386 and the current cross compiler only runs 64bit mode. I may be able to use the 386 box to run linuxcnc in the shop and bring the D525MW inside to set up a cross compile environment but the D525MW only has a 32gb SSD at the moment. Alan > On Jul 30, 2017, at 4:48 PM, Charles Steinkuehler <[email protected]> > wrote: > > The DE0-Nano image will /probably/ boot on the DE10, but the FPGA will > not be programmed. If the DE10 doesn't boot, the issue is almost > certainly the kernel and/or device tree. If you use the kernel and > device tree from the DE10 image on a DE0 image you ought to be able to > boot with the DE0 uSD. > > Basically, it looks like the DE10 is the DE0 with a larger FPGA and an > HDMI output... > > ...and all of the Cyclone-V SoC+FPGA parts share the same ARM hard > processor side, so the kernel/device-tree will be mostly identical for > things like Ethernet, uSD, flash, SDRAM, etc. as long as the boards > are not too dramatically different. > > On 7/30/2017 6:07 PM, mugginsac wrote: >> Charles, >> >> OK, I got my DE10-nano. So let me ask another question, will the >> DE0-Nano-Soc >> MachineKit image boot on the DE10-Nano board (as a starting point for doing >> the >> implementation)? Or do I need to start with the DE10-Nano image from Terasic? >> >> Alan >> >> On Thursday, July 27, 2017 at 9:21:19 AM UTC-7, mugginsac wrote: >> >> I placed the order for a DE10-Nano. >> Alan >> >> On Wednesday, July 26, 2017 at 2:15:29 PM UTC-7, Charles Steinkuehler >> wrote: >> >> >> I'll try to carve out some time to get an FPGA project setup for the >> DE10-nano, unless someone else feels up to the task. >> >> -- >> Charles Steinkuehler >> [email protected] >> >> -- >> 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] >> <mailto:[email protected]> >> <mailto:[email protected] >> <mailto:[email protected]>>. >> Visit this group at https://groups.google.com/group/machinekit >> <https://groups.google.com/group/machinekit>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. >> > > > -- > Charles Steinkuehler > [email protected] <mailto:[email protected]> > > -- > website: http://www.machinekit.io <http://www.machinekit.io/> blog: > http://blog.machinekit.io <http://blog.machinekit.io/> github: > https://github.com/machinekit <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/fleGyyOwDgE/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. For more options, visit https://groups.google.com/d/optout.
