Re: [Machinekit] Re: Running Machinekit on Zynq Zturn board or Zed Board
On 10/13/2017 1:12 PM, automata wrote: > > From this youtube video by Charles > S. https://www.youtube.com/watch?v=veM83KCytuQ, somewhere around the 24 > minute mark, it references the various repositories required to get the > Altera SOC And teh ZYNQ systems working. > > The items required along with their repositories are: > 1. Uboot : https://github.com/JDSquared/u-boot-xlnx/ > 2. Linux kernel : https://github.com/JDSquared/linux-stable/ > 3. rootfs : https://github.com/cdsteinkuehler/omap-image-builder/ > 4. FPGA bit files :https://github.com/machinekit/mksocfpga/ > 5. FPGA packages : https://github.com/machinekit/mksocfpga/ - not sure > where this fits in .. but it could be required to make the BOOT.BIN file > with the FSBL (First stage bootloader), kernel image etc > 6. uSD image - bring it all together > : https://github.com/cdsteinkuehler/omap-image-builder/ > 7. machinekit application software where it all comes together. This is > included in the rootfs repo. with an RIP (run in place) build. That's how to rebuild everything from scratch, but you don't have to go to the trouble unless you want. > At the moment, I am trying to muck around the jenkins jobs to see what they > are trying to compile in the docker containers. > > However, I am still new to docker, jenkins, compiling kernels, uboot and > zynq. So I was hoping something readymade was available to get a head > start. You should be able to get u-Boot and the kernel from example Xilinx images. The rootfs can be any generic Debian rootfs, I typically start with the Jessie rootfs from RCN's BBB Machinekit image. The FPGA bitfiles are available as a package from the Machinekit repo. AFAIK, the main thing missing (as long as you're using the Zynq board Michael was working with) is a ready-to-use uSD image. I typically start with a generic example for the target board, replace the rootfs and FPGA bitfile, then replace the kernel (if needed, some images come with a real-time kernel already). Remember you'll probably need to copy a few bits from the old rootfs (like the kernel modules). -- 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] Error with CRAMPS.hal
On Fri, Oct 13, 2017 at 2:23 PM, 'Dimitar Dobrev' via Machinekitwrote: > Option 1 made no difference to the output. Option 2 removed this line: > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.10-1-g143c9ee] > > Unfortunately, it makes no difference. I still get: > > grep: /sys/devices/bone_capemgr.*/slots: No such file or directory That's 3.8.x path in v4.1.x + it's debian@test-bbb-2:~$ cat /proc/cmdline console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 debian@test-bbb-2:~$ uname -r 4.9.54-ti-r68 debian@test-bbb-2:~$ ls -lha /sys/devices/platform/bone_capemgr/ total 0 drwxr-xr-x 4 root root0 Oct 13 20:43 . drwxr-xr-x 20 root root0 Oct 13 20:43 .. drwxr-xr-x 2 root root0 Oct 13 20:43 baseboard lrwxrwxrwx 1 root root0 Oct 13 20:43 driver -> ../../../bus/platform/drivers/bone_capemgr -rw-r--r-- 1 root root 4.0K Oct 13 20:43 driver_override -r--r--r-- 1 root root 4.0K Oct 13 20:43 modalias lrwxrwxrwx 1 root root0 Oct 13 20:43 of_node -> ../../../firmware/devicetree/base/bone_capemgr drwxr-xr-x 2 root root0 Oct 13 20:43 power -rw-r--r-- 1 root root 4.0K Oct 13 20:43 slots lrwxrwxrwx 1 root root0 Oct 13 20:43 subsystem -> ../../../bus/platform -rw-r--r-- 1 root root 4.0K Oct 13 20:43 uevent While the slots file is only there if U-Boot does not pass: bone_capemgr.uboot_capemgr_enabled=1 btw, do you have a file located here: /uEnv.txt That also breaks U-Boot overlays, remove it. 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: Running Machinekit on Zynq Zturn board or Zed Board
Hi, For item 1. i.e., U-boot, The compilation procedure was relatively straight forward. inside the docker container ubker ( https://github.com/dkhughes/ubker-docker) Uboot was pulled earlier from: https://github.com/JDSquared/u-boot-xlnx/ 1. cd /home/developer/u-boot-xlnx 2. make zynq_zturn_config OR 2. make zynq_zed_config 3. make This should have the u-boot.img file in the u-boot-xlnx directory. Not sure what to do with it yet.. but going to hold onto it just in case. Next comes the kernel. I got an RT patched kernel from https://github.com/JDSquared/linux-stable/ 1. cd linux-stable 2. ?? This is where I am stuck. Need some guidance here. Also not sure where to build the rootfs ... inside the docker container or need to set some environment variables and use debian jessie amd64? Regards, -automata On Friday, October 13, 2017 at 11:42:57 PM UTC+5:30, automata wrote: > > > > On Friday, October 13, 2017 at 9:46:14 PM UTC+5:30, Eric Keller wrote: >> >> the first step of porting Machinekit to a new processor is to build a >> compatible real time kernel. Then build Machinekit against that kernel. >> It's not a matter of d/l an image. >> Eric >> >> Hi Eric, > > Thanks for the response. > > I have also been trying to compile an appropriate kernel from: > https://github.com/JDSquared/linux-stable/ using the docker image from > https://github.com/dkhughes/ubker-docker. After a couple days of staring > at the name, I understood that "ubker" was a mashup of uboot and Kernel. So > I need to use that particular docker image to compile the ubbot and linux > kernel to replicate the kernel that dkhughes has successfully compiled. > > This information was made available from the machinekit jenkins site: > https://jenkins.machinekit.io/ > > From this youtube video by Charles S. > https://www.youtube.com/watch?v=veM83KCytuQ, somewhere around the 24 > minute mark, it references the various repositories required to get the > Altera SOC And teh ZYNQ systems working. > > The items required along with their repositories are: > 1. Uboot : https://github.com/JDSquared/u-boot-xlnx/ > 2. Linux kernel : https://github.com/JDSquared/linux-stable/ > 3. rootfs : https://github.com/cdsteinkuehler/omap-image-builder/ > 4. FPGA bit files :https://github.com/machinekit/mksocfpga/ > 5. FPGA packages : https://github.com/machinekit/mksocfpga/ - not sure > where this fits in .. but it could be required to make the BOOT.BIN file > with the FSBL (First stage bootloader), kernel image etc > 6. uSD image - bring it all together : > https://github.com/cdsteinkuehler/omap-image-builder/ > 7. machinekit application software where it all comes together. This is > included in the rootfs repo. with an RIP (run in place) build. > > At the moment, I am trying to muck around the jenkins jobs to see what > they are trying to compile in the docker containers. > > However, I am still new to docker, jenkins, compiling kernels, uboot and > zynq. So I was hoping something readymade was available to get a head > start. > > On the other hand I am also open to advise on how to get and compile and > put together the 7 repositories and generate a bootable uSD card image. I > am still missing the bit about a device tree and fsbl. But I am hoping that > will all come together in the mksocfpga repository in the FPGA Package step. > > I am using a Debian Jessie amd64 VM on Windows10 host using Virtualbox to > bring all this together. Currently compiling uboot and the kernel in the > ubker docker (https://github.com/dkhughes/ubker-docker). At the same time > I am trying to setup the vivado docker image ( > https://github.com/dkhughes/vivado-docker) with the 2017.2 Xilinx vivado > +SDK installer from Xilinx. > > Hardware wise I have the Zturn board with a 7020 chip and a Avnet/ > Digillent Zedboard again with the 7020 Zynq chip. > > The learning curve is sTeeP and any help or pointers on how to proceed > will be graciously accepted. > > Regards, > > -automata > > > >> On Fri, Oct 13, 2017 at 11:40 AM, automata>> wrote: >> >>> >>> >>> On Friday, October 13, 2017 at 4:22:21 PM UTC+5:30, automata wrote: Hi, I am trying to run machinekit on a Zturn board with a Zynq7020 processor. I downloaded the SD card image from http://deb.machinekit.io/uploads/zynq/debian-8.5-console-armhf-2016-08-25/ But could not get much further from there. Can someone point out how to start with either the Zturn board or the Zedboard with Zynq7020 chip. I am willing (with a little help) to make the startup documentation / gist like https://gist.github.com/mhaberler/89a813dc70688e35d8848e8e467a1337 which is for the Altera SOC+FPGA board. Regards, -automata >>> >>> I tried using the image from >>> http://deb.mah.priv.at/uploads/zynq/debian-8.5-console-armhf-2016-11-21/ >>> which seems to be the
Re: [Machinekit] Error with CRAMPS.hal
On Fri, Oct 13, 2017 at 1:11 PM, 'Dimitar Dobrev' via Machinekitwrote: > git:/opt/scripts/:[6b111dede3053d977465860905cfc27d6effe51e] > eeprom:[A335BNLT00C04016BBBK042B] > model:[TI_AM335x_BeagleBone_Black] > dogtag:[Machinekit Debian Image 2017-02-12] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2017.09-2-g0f3f1c7907] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.10-1-g143c9ee] So here's the issue, eMMC version of U-Boot get's used, and all uboot overlay options get ignored.. So you have two options: 1: care about the data on eMMC just run this to nuke the "MLO" file sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 bs=128k 2: Erase the eMMC.. sudo dd if=/dev/zero of=/dev/mmcblk1 > kernel:[4.4.91-bone-rt-r19] > nodejs:[v6.11.2] > uboot_overlay_options:[enable_uboot_overlays=1] > uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/BB-UART1-00A0.dtbo] > uboot_overlay_options:[disable_uboot_overlay_video=1] > uboot_overlay_options:[disable_uboot_overlay_audio=1] > uboot_overlay_options:[disable_uboot_overlay_wireless=1] > uboot_overlay_options:[enable_uboot_cape_universal=1] > pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728] > WARNING:pkg:[bb-wl18xx-firmware]:[NOT_INSTALLED] > WARNING:pkg:[firmware-ti-connectivity]:[NOT_INSTALLED] Then reboot, you should see the kernel come up differently.. 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: Running Machinekit on Zynq Zturn board or Zed Board
On Friday, October 13, 2017 at 9:46:14 PM UTC+5:30, Eric Keller wrote: > > the first step of porting Machinekit to a new processor is to build a > compatible real time kernel. Then build Machinekit against that kernel. > It's not a matter of d/l an image. > Eric > > Hi Eric, Thanks for the response. I have also been trying to compile an appropriate kernel from: https://github.com/JDSquared/linux-stable/ using the docker image from https://github.com/dkhughes/ubker-docker. After a couple days of staring at the name, I understood that "ubker" was a mashup of uboot and Kernel. So I need to use that particular docker image to compile the ubbot and linux kernel to replicate the kernel that dkhughes has successfully compiled. This information was made available from the machinekit jenkins site: https://jenkins.machinekit.io/ >From this youtube video by Charles S. https://www.youtube.com/watch?v=veM83KCytuQ, somewhere around the 24 minute mark, it references the various repositories required to get the Altera SOC And teh ZYNQ systems working. The items required along with their repositories are: 1. Uboot : https://github.com/JDSquared/u-boot-xlnx/ 2. Linux kernel : https://github.com/JDSquared/linux-stable/ 3. rootfs : https://github.com/cdsteinkuehler/omap-image-builder/ 4. FPGA bit files :https://github.com/machinekit/mksocfpga/ 5. FPGA packages : https://github.com/machinekit/mksocfpga/ - not sure where this fits in .. but it could be required to make the BOOT.BIN file with the FSBL (First stage bootloader), kernel image etc 6. uSD image - bring it all together : https://github.com/cdsteinkuehler/omap-image-builder/ 7. machinekit application software where it all comes together. This is included in the rootfs repo. with an RIP (run in place) build. At the moment, I am trying to muck around the jenkins jobs to see what they are trying to compile in the docker containers. However, I am still new to docker, jenkins, compiling kernels, uboot and zynq. So I was hoping something readymade was available to get a head start. On the other hand I am also open to advise on how to get and compile and put together the 7 repositories and generate a bootable uSD card image. I am still missing the bit about a device tree and fsbl. But I am hoping that will all come together in the mksocfpga repository in the FPGA Package step. I am using a Debian Jessie amd64 VM on Windows10 host using Virtualbox to bring all this together. Currently compiling uboot and the kernel in the ubker docker (https://github.com/dkhughes/ubker-docker). At the same time I am trying to setup the vivado docker image (https://github.com/dkhughes/vivado-docker) with the 2017.2 Xilinx vivado +SDK installer from Xilinx. Hardware wise I have the Zturn board with a 7020 chip and a Avnet/ Digillent Zedboard again with the 7020 Zynq chip. The learning curve is sTeeP and any help or pointers on how to proceed will be graciously accepted. Regards, -automata > On Fri, Oct 13, 2017 at 11:40 AM, automata> wrote: > >> >> >> On Friday, October 13, 2017 at 4:22:21 PM UTC+5:30, automata wrote: >>> >>> Hi, >>> >>> I am trying to run machinekit on a Zturn board with a Zynq7020 processor. >>> >>> I downloaded the SD card image from >>> http://deb.machinekit.io/uploads/zynq/debian-8.5-console-armhf-2016-08-25/ >>> >>> But could not get much further from there. >>> >>> Can someone point out how to start with either the Zturn board or the >>> Zedboard with Zynq7020 chip. >>> >>> I am willing (with a little help) to make the startup documentation / >>> gist like >>> https://gist.github.com/mhaberler/89a813dc70688e35d8848e8e467a1337 >>> which is for the Altera SOC+FPGA board. >>> >>> Regards, >>> >>> -automata >>> >> >> I tried using the image from >> http://deb.mah.priv.at/uploads/zynq/debian-8.5-console-armhf-2016-11-21/ >> which seems to be the last machinekit Zynq SD card image I can find. The >> other one being at >> http://deb.machinekit.io/uploads/zynq/debian-8.5-console-armhf-2016-08-25/ >> which is considerably older. >> >> On the Zturn board I got the following output. IT skipped looking for >> partition 2 and straight started with 3. >> U boot seems to have booted the processor and it is not able to find the >> kernel uImage? >> >> -automata >> >> ** Output on serial console.* >> U-Boot SPL 2016.01-00024-g5cf690d7 (Aug 16 2016 - 17:00:16) >> mmc boot >> Trying to boot from MMC >> reading fpga.bin >> spl_load_image_fat: error reading image fpga.bin, err - -1 >> spl: error reading image fpga.bin, err - 1 >> reading system.dtb >> spl_load_image_fat_os: error reading image system.dtb, err - -1 >> reading u-boot.img >> reading u-boot.img >> >> >> U-Boot 2016.01-00024-g5cf690d7 (Aug 16 2016 - 17:00:16 +), Build: >> jenkins-u-boot-xilinx-9 >> >> Model: MYIR Z-turn Development Board >> Board: Xilinx Zynq >> DRAM: ECC disabled 1 GiB >>
Re: [Machinekit] Error with CRAMPS.hal
On Fri, Oct 13, 2017 at 10:21 AM, 'Dimitar Dobrev' via Machinekitwrote: > Bas, I have run: > > grep -c bone_capemgr.uboot_capemgr_enabled=1 /proc/cmdline > > I get: > > 0 > > This was both before and after I enabled enable_uboot_cape_universal=1 in > /boo/uEnv.txt (with a reboot between, of course). I've also tried enabling: > > cape_enable=bone_capemgr.enable_partno=BB-UART1 > > to no avail. I've also followed > https://groups.google.com/d/msg/beagleboard/go89maLiYPc/ebAJrTtJzMsJ . I > keep getting 0 from > grep -c bone_capemgr.uboot_capemgr_enabled=1 /proc/cmdline > and the same error with CRAMPS. > Do I perhaps need to enable additional settings? Please run: sudo /opt/scripts/tools/version.sh So we can see a better picture of your u-boot/kernel combination for debugging.. 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: Running Machinekit on Zynq Zturn board or Zed Board
the first step of porting Machinekit to a new processor is to build a compatible real time kernel. Then build Machinekit against that kernel. It's not a matter of d/l an image. Eric On Fri, Oct 13, 2017 at 11:40 AM, automatawrote: > > > On Friday, October 13, 2017 at 4:22:21 PM UTC+5:30, automata wrote: >> >> Hi, >> >> I am trying to run machinekit on a Zturn board with a Zynq7020 processor. >> >> I downloaded the SD card image from http://deb.machinekit.io/ >> uploads/zynq/debian-8.5-console-armhf-2016-08-25/ >> >> But could not get much further from there. >> >> Can someone point out how to start with either the Zturn board or the >> Zedboard with Zynq7020 chip. >> >> I am willing (with a little help) to make the startup documentation / >> gist like https://gist.github.com/mhaberler/89a813dc70688e35d8848 >> e8e467a1337 which is for the Altera SOC+FPGA board. >> >> Regards, >> >> -automata >> > > I tried using the image from http://deb.mah.priv.at/ > uploads/zynq/debian-8.5-console-armhf-2016-11-21/ which seems to be the > last machinekit Zynq SD card image I can find. The other one being at > http://deb.machinekit.io/uploads/zynq/debian-8.5-console-armhf-2016-08-25/ > which is considerably older. > > On the Zturn board I got the following output. IT skipped looking for > partition 2 and straight started with 3. > U boot seems to have booted the processor and it is not able to find the > kernel uImage? > > -automata > > ** Output on serial console.* > U-Boot SPL 2016.01-00024-g5cf690d7 (Aug 16 2016 - 17:00:16) > mmc boot > Trying to boot from MMC > reading fpga.bin > spl_load_image_fat: error reading image fpga.bin, err - -1 > spl: error reading image fpga.bin, err - 1 > reading system.dtb > spl_load_image_fat_os: error reading image system.dtb, err - -1 > reading u-boot.img > reading u-boot.img > > > U-Boot 2016.01-00024-g5cf690d7 (Aug 16 2016 - 17:00:16 +), Build: > jenkins-u-boot-xilinx-9 > > Model: MYIR Z-turn Development Board > Board: Xilinx Zynq > DRAM: ECC disabled 1 GiB > MMC: sdhci@e010: 0 > SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, > total 16 MiB > *** Warning - bad CRC, using default environment > > In:serial@e0001000 > Out: serial@e0001000 > Err: serial@e0001000 > Model: MYIR Z-turn Development Board > Board: Xilinx Zynq > Net: ZYNQ GEM: e000b000, phyaddr 0, interface rgmii-id > eth0: ethernet@e000b000 > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > Checking for: /boot/uEnv.txt ... > Trying interface=mmc bootpart=0:2 ... > 282 bytes read in 110 ms (2 KiB/s) > Loaded environment from /boot/uEnv.txt > Using: dtb=zynq-zturn.dtb ... > Skipping FPGA load ... > Checking if uname_r is set in /boot/uEnv.txt ... > Running uname_boot ... > Trying interface=mmc bootpart=0:3 ... > ** Invalid partition 3 ** > Trying interface=mmc bootpart=0:4 ... > ** Invalid partition 4 ** > Trying interface=mmc bootpart=0:5 ... > ** Invalid partition 5 ** > Trying interface=mmc bootpart=0:6 ... > ** Invalid partition 6 ** > Trying interface=mmc bootpart=0:7 ... > ** Invalid partition 7 ** > Zynq> > > > -- > 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. > -- 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: Running Machinekit on Zynq Zturn board or Zed Board
On Friday, October 13, 2017 at 4:22:21 PM UTC+5:30, automata wrote: > > Hi, > > I am trying to run machinekit on a Zturn board with a Zynq7020 processor. > > I downloaded the SD card image from > http://deb.machinekit.io/uploads/zynq/debian-8.5-console-armhf-2016-08-25/ > > But could not get much further from there. > > Can someone point out how to start with either the Zturn board or the > Zedboard with Zynq7020 chip. > > I am willing (with a little help) to make the startup documentation / gist > like https://gist.github.com/mhaberler/89a813dc70688e35d8848e8e467a1337 > which is for the Altera SOC+FPGA board. > > Regards, > > -automata > I tried using the image from http://deb.mah.priv.at/uploads/zynq/debian-8.5-console-armhf-2016-11-21/ which seems to be the last machinekit Zynq SD card image I can find. The other one being at http://deb.machinekit.io/uploads/zynq/debian-8.5-console-armhf-2016-08-25/ which is considerably older. On the Zturn board I got the following output. IT skipped looking for partition 2 and straight started with 3. U boot seems to have booted the processor and it is not able to find the kernel uImage? -automata ** Output on serial console.* U-Boot SPL 2016.01-00024-g5cf690d7 (Aug 16 2016 - 17:00:16) mmc boot Trying to boot from MMC reading fpga.bin spl_load_image_fat: error reading image fpga.bin, err - -1 spl: error reading image fpga.bin, err - 1 reading system.dtb spl_load_image_fat_os: error reading image system.dtb, err - -1 reading u-boot.img reading u-boot.img U-Boot 2016.01-00024-g5cf690d7 (Aug 16 2016 - 17:00:16 +), Build: jenkins-u-boot-xilinx-9 Model: MYIR Z-turn Development Board Board: Xilinx Zynq DRAM: ECC disabled 1 GiB MMC: sdhci@e010: 0 SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 16 MiB *** Warning - bad CRC, using default environment In:serial@e0001000 Out: serial@e0001000 Err: serial@e0001000 Model: MYIR Z-turn Development Board Board: Xilinx Zynq Net: ZYNQ GEM: e000b000, phyaddr 0, interface rgmii-id eth0: ethernet@e000b000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Checking for: /boot/uEnv.txt ... Trying interface=mmc bootpart=0:2 ... 282 bytes read in 110 ms (2 KiB/s) Loaded environment from /boot/uEnv.txt Using: dtb=zynq-zturn.dtb ... Skipping FPGA load ... Checking if uname_r is set in /boot/uEnv.txt ... Running uname_boot ... Trying interface=mmc bootpart=0:3 ... ** Invalid partition 3 ** Trying interface=mmc bootpart=0:4 ... ** Invalid partition 4 ** Trying interface=mmc bootpart=0:5 ... ** Invalid partition 5 ** Trying interface=mmc bootpart=0:6 ... ** Invalid partition 6 ** Trying interface=mmc bootpart=0:7 ... ** Invalid partition 7 ** Zynq> -- 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] Running Machinekit on Zynq Zturn board or Zed Board
Hi, I am trying to run machinekit on a Zturn board with a Zynq7020 processor. I downloaded the SD card image from http://deb.machinekit.io/uploads/zynq/debian-8.5-console-armhf-2016-08-25/ But could not get much further from there. Can someone point out how to start with either the Zturn board or the Zedboard with Zynq7020 chip. I am willing (with a little help) to make the startup documentation / gist like https://gist.github.com/mhaberler/89a813dc70688e35d8848e8e467a1337 which is for the Altera SOC+FPGA board. Regards, -automata -- 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.