Re: [Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
Robert, Thanks. At least it loaded right up as shown on the serial terminal. Now it is at least looking for the ext4 filesystem before loading the ext2 filesystem. Something that I read suggested that the journal-ing stuff on ext4 could shorten the life of the uSD card but that the ext4 has higher performance. Should I go ahead and change it back to an ext4 filesystem? As far as I can tell it isn't activating the HDMI. When I hook up to the monitor and keyboard (like with the other uSD) I don't see any action. Also I don't see any action on the leds like the original uSD system. Is it likely that it is failing to load the .rbf file? I don't even know where it expects to find it. But I don't see any message to indicate that it is looking for it and failing to find it. Thanks again, Alan -- 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. U-Boot SPL 2017.05-dirty (Aug 21 2017 - 18:44:30) drivers/ddr/altera/sequencer.c: Preparing to start memory calibration drivers/ddr/altera/sequencer.c: CALIBRATION PASSED drivers/ddr/altera/sequencer.c: Calibration complete Trying to boot from MMC1 U-Boot 2017.05-dirty (Aug 21 2017 - 18:44:30 -0700) CPU: Altera SoCFPGA Platform FPGA: Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0 BOOT: SD/MMC Internal Transceiver (3.0V) Watchdog enabled I2C: ready DRAM: 1 GiB MMC: dwmmc0@ff704000: 0 In:serial Out: serial Err: serial Model: Terasic DE10-Nano Net: Error: ethernet@ff702000 address not set. No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:2... Found /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf 163 bytes read in 15 ms (9.8 KiB/s) 1: Linux 4.4.60-socfpga-r3 Retrieving file: /boot/vmlinuz-4.4.60-socfpga-r3 5223096 bytes read in 363 ms (13.7 MiB/s) append: root=/dev/mmcblk0p2 ro rootwait quiet Retrieving file: /boot/dtbs/4.4.60-socfpga-r3/socfpga_cyclone5_de10_nano.dtb 29940 bytes read in 30 ms (974.6 KiB/s) ## Flattened Device Tree blob at 0200 Booting using the fdt blob at 0x200 reserving fdt memory region: addr=0 size=1000 Loading Device Tree to 03ff5000, end 03fff4f3 ... OK Starting kernel ... [0.00] L2C: platform provided aux values permit register corruption. [4.669971] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities [ OK ] Started File System Check on Root Device. Starting Remount Root and Kernel File Systems... [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting Raise network interfaces... Starting Load/Save Random Seed... Starting udev Coldplug all Devices... Starting Flush Journal to Persistent Storage... [ OK ] Started Load/Save Random Seed. [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Started Create Volatile Files and Directories. Starting Network Time Synchronization... Starting Update UTMP about System Boot/Shutdown... [ OK ] Started udev Coldplug all Devices. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Found device /dev/ttyS0. [ OK ] Started Raise network interfaces. [ OK ] Started Network Time Synchronization. [ OK ] Reached target System Initialization. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting DUN service... Starting System Logging Service... [ OK ] Started Regular background program processing daemon. [ OK ] Started D-Bus System Message Bus. [ OK ] Started DUN service. Starting Connection service... Starting Login Service... Starting Cape Manager Service... Starting Avahi mDNS/DNS-SD Stack... Starting Telephony service... Starting Generic Board Startup... Starting LSB: Load kernel modules needed to enable cpufreq scaling... [ OK ] Reached target System Time Synchronized. [ OK ] Started System Logging Service. [ OK ] Started Cape Manager Service. [ OK ] Started Generic Board Startup. [ OK ] Started Telephony service. [ OK ] Started Avahi mDNS/DNS-SD Stack. [ OK ] Started Connection service. [ OK ] Started Login Service. Starting Hostname Service...
Re: [Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
On Mon, Aug 21, 2017 at 4:56 PM, mugginsacwrote: > Here is what I am getting from trying to boot the uSD I built. Is it > possible that I have a bad uSD? > > U-Boot SPL 2017.05 (Aug 20 2017 - 08:57:37) > drivers/ddr/altera/sequencer.c: Preparing to start memory calibration > drivers/ddr/altera/sequencer.c: CALIBRATION PASSED > drivers/ddr/altera/sequencer.c: Calibration complete > Trying to boot from MMC1 > > > U-Boot 2017.05 (Aug 20 2017 - 08:57:37 -0700) > > CPU: Altera SoCFPGA Platform > FPGA: Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0 > BOOT: SD/MMC Internal Transceiver (3.0V) >Watchdog enabled > I2C: ready > DRAM: 1 GiB > MMC: dwmmc0@ff704000: 0 > *** Warning - bad CRC, using default environment > > In:serial > Out: serial > Err: serial > Model: Terasic DE10-Nano > Net: > Error: ethernet@ff702000 address not set. > No ethernet found. > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > Unknown command 'part' - try 'help' add: CONFIG_CMD_PART=y this was missed in v2017.05-ish time frame... diff --git a/configs/socfpga_de10_nano_defconfig b/configs/socfpga_de10_nano_defconfig index 26addc3c4d..fc2dcc3951 100644 --- a/configs/socfpga_de10_nano_defconfig +++ b/configs/socfpga_de10_nano_defconfig @@ -25,6 +25,7 @@ CONFIG_CMD_DFU=y CONFIG_CMD_GPIO=y CONFIG_CMD_I2C=y CONFIG_CMD_MMC=y +CONFIG_CMD_PART=y CONFIG_CMD_SPI=y CONFIG_CMD_USB=y CONFIG_CMD_USB_MASS_STORAGE=y Regards, -- Robert Nelson https://rcn-ee.com/ -- 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.
Re: [Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
On 8/21/2017 5:59 PM, mugginsac wrote: > Charles, > > What terminal software are you using? > Is there any special setup required other than 115,200 baud and 8N1 > (data,parity, and stop bits)? > I can't get putty to work with the DE10 and I sometimes get those weird > single column scroll down the right hand side with minicom. I'm using Putty on my Windows 7 box: 115,200 baud 8n1 no parity no flow control You might play with the terminal settings. I usually use VT100 or Linux, but I typically don't see any issues with either until I try using full-screen programs (like vi). Most anything should be OK for interacting with the U-Boot terminal prompt. -- 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.
Re: [Machinekit] Re: machinekit post processor
The problem appears to be a small amount of flex in the linear rods. I used 8mm rods thinking that the stresses wouldn't very much when used as a drag engraver. I will probably up size the rods to 12mm in the final design version. The 8mm rods would probably be fine for laser engraving. On Friday, August 18, 2017 at 3:13:04 AM UTC-7, Frederic RIBLE wrote: > > Could you post a picture showing the issue ? > You can try with a small hand written GCODE file engraving basic shapes > (circles). > Backlash, if any, should be visible as geometric distortion when the > direction of the motion is changing. > > Frederic > http://cnc.f1oat.org > On 2017-08-18 01:14, 'Harley Engholm' via Machinekit wrote: > > Have worked with the backlash parameter and have observed no differences > in the engravings. Thanks for the info and I will keep playing with the > machine to see if there is > a solution. > > On Tuesday, August 15, 2017 at 5:38:04 PM UTC-7, Harley Engholm wrote: >> >> I am using Vectric Cut2d for my designs and have been using EMC2 post >> processors for the g code creation. Everything works except that the >> text on engravings are somewhat distorted, ie a straight line on the >> bottom of an "L" is curved. Also circles are not complete, there is a very >> small opening at the ends. All of the distortions seem to be the identical >> when repeating an engraved word, so it seems that it may be more of a code >> issue than a mechanical issue. I am wondering if anyone else has had this >> problem and if there is a dedicated post processor for machinekit running >> on a BBB. >> >> Harley >> > -- > 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+...@googlegroups.com . > 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 machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
Charles, What terminal software are you using? Is there any special setup required other than 115,200 baud and 8N1 (data,parity, and stop bits)? I can't get putty to work with the DE10 and I sometimes get those weird single column scroll down the right hand side with minicom. Alan -- 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.
Re: [Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
On 8/21/2017 4:56 PM, mugginsac wrote: > Here is what I am getting from trying to boot the uSD I built. Is it > possible that I have a bad uSD? Your uSD is probably fine. There's a CRC error because you don't (yet) have a saved U-Boot environment on the A2 partition. Based on the output you are getting, I suspect your uSD setup does not match the default environment compiled into U-Boot. I recommend dropping into the U-Boot shell (press a command when prompted to stop the autoboot) and poke around to see what U-Boot is expecting. You can probably fix this by either updating your uSD image to match what U-Boot expects (filesystems, partitions, kernel/dts filenames, etc) or by modifying the U-Boot environment to match your uSD and storing the updated environment on the A2 partition. -- 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.
[Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
Here is what I am getting from trying to boot the uSD I built. Is it possible that I have a bad uSD? U-Boot SPL 2017.05 (Aug 20 2017 - 08:57:37) drivers/ddr/altera/sequencer.c: Preparing to start memory calibration drivers/ddr/altera/sequencer.c: CALIBRATION PASSED drivers/ddr/altera/sequencer.c: Calibration complete Trying to boot from MMC1 U-Boot 2017.05 (Aug 20 2017 - 08:57:37 -0700) CPU: Altera SoCFPGA Platform FPGA: Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0 BOOT: SD/MMC Internal Transceiver (3.0V) Watchdog enabled I2C: ready DRAM: 1 GiB MMC: dwmmc0@ff704000: 0 *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Model: Terasic DE10-Nano Net: Error: ethernet@ff702000 address not set. No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Unknown command 'part' - try 'help' Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** a -- 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.
[Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
Taking a break from watching the progress of the solar eclipse. What I am trying to do is get to the point of building a system that will run with HDMI before I start trying to add MachineKit and the hm2 stuff. At the moment the build doesn't seem to run HDMI. I thought I was using the same dtbs and rbf that the original DE10-Nano system used. However, since it doesn't seem to boot with my monitor, keyboard and mouse like the original system maybe I didn't get the correct files. -- 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.