Search the Community

Showing results for tags 'linux'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 106 results

  1. kadionik

    I2C PMOD access under Linux

    Hi all, I've built with the Nexyx4 DDR board a system running Linux. In my running HW design, I've added the onboard temperature sensor of the board and the PMOD A connector to connect a I2C TMP3 temperature sensor. The HW interface for the onboard temperature sensor is the AXI IIC interface. For the TMP3 sensor with the Digilent's vivado library (as explained in: https://reference.digilentinc.com/learn/programmable-logic/tutorials/pmod-ips/start), it's the AXI LITE IIC interface. With the Linux I2C tools, I see the onboard sensor: nexys4ddr:/# uname -r 4.14.0-00493-gb68293ad2c93-dirty nexys4ddr:/# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- 4b -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- And I can read temperature with the Linux I2C API: nexys4ddr:/# tsttemp TEMP=29.2 oC nexys4ddr:/# But I don't see the I2C TMP3 sensor. My questions are: - The vivado TMP3 instance has a I2C interface (AXI LITE IIC). Can I use the Linux I2C API? If yes, on the PMOD ja port, what are the pins of the connector corresponding to SCL, SDA (easy for ground and 3V3 ;-)? I didn't find this information in the Digilent's vivado library. - If I I can't use the Linux I2C API, I must generate by hand and by software the SCL and SDA signals and what is the role of AXI LITE IIC interface? In this case, would it better to use directly the IIC AXI interface as with the onboard sensor and precise after in a XDC file connexions between to the PMOD A port and TMP3 sensor? Thank you for your help. Pat.
  2. I'm using pynq z1board, use the pynq_z1_v2.3.img image file, when the board start the micro sd card has been automatically divided into 2 partition, the first partition is fat16 format and has BOOT.BIN and image.ub file, the second partition is linux ext3 foramt; the whole volume of my sd card is 32GB; when I use 'TAB' key there is warning as follows: -bash: cannot create temp file for here-document: No space left on device So I use command 'df -hl',as follows,the /dev/root/ is full, how can I solve the problem? xilinx@pynq:~$ df -hl Filesystem Size Used Avail Use% Mounted on /dev/root 5.2G 5.2G 0 100% / devtmpfs 185M 0 185M 0% /dev tmpfs 249M 0 249M 0% /dev/shm tmpfs 249M 27M 223M 11% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 249M 0 249M 0% /sys/fs/cgroup tmpfs 50M 0 50M 0% /run/user/1000
  3. Hi all, This is a quick and dirty howto. This howto describes how to use I2C modules (onboard and through PMOD connector) under embedded Linux. I've chosen to build my own Linux distro based on Linux kernel source for MicroBlaze softcore and busybox project for the init RAM DISK. My board is the Nexys4 DDR board. If you respect the following requirements for the HW design compatible with Linux, you can use Petalinux too. HW Vivado requirements (according to Xilinx UG1144) design to boot Linux: MicroBlaze with MMU support by selecting either Linux with MMU or Low-end Linux with MMU configuration template in the MicroBlaze configuration wizard. External memory controller with at least 32 MB of memory. Dual channel timer with interrupt connected. UART with interrupt connected. Ethernet with interrupt connected. Note that all peripherals you use must be interrupt capable. For the UART peripheral, if you have not enabled interrupts, you have no Linux console outputs. For the Nexys4 DDR, you can follow this online tutorial: https://reference.digilentinc.com/learn/programmable-logic/tutorials/nexys-4-ddr-getting-started-with-microblaze-servers/start At this stage, for the Nexys4 DDR board, you can add the onboard i2C temperature sensor (ADT7420) that uses the AXI IIC IP block. I've added a second external temperature sensor (PMOD TMP3) connected to PMOD JA pins of the Nexys4 DDR board. I've chosen to connect SCL TMP3 pin to JA1 PMOD JA pin (C17 FPGA pin) and SDA MP3 pin to JA2 PMOD JA pin (D18 FPGA pin). You connect GND and 3V3 pins from PMOD JA connector to corresponding TMP3 pins. You have finally 4 pins to connect. You obtain the Vivado design shown below. Notice that both AXI IIC IP blocks have interrupts connected for Linux compatibility. For the TMP3 sensor, I have an external port named temp3_sensor. I've created a XDC file containing: set_property -dict { PACKAGE_PIN D5 IOSTANDARD LVCMOS33 } [get_ports { eth_ref_clk }]; # Sch=eth_ref_clk set_property -dict { PACKAGE_PIN C17 IOSTANDARD LVCMOS33 } [get_ports { tmp3_sensor_scl_io }]; set_property -dict { PACKAGE_PIN D18 IOSTANDARD LVCMOS33 } [get_ports { tmp3_sensor_sda_io }]; You can see that: tmp3_sensor_scl_io signal is for SCL I2C signal. tmp3_sensor_sda_io signal is for SDA I2C signal Please respect notation: xxx external I2C port gives xxx_scl_io and xxx_sda_io signal names in the XDC file. Generate .bit file. Launch Vivado SDK tool, install the device tree plugin and generate Device Tree files. You can follow this link: https://numato.com/kb/neso-microblaze-linux-run-linux-neso-artix-7-fpga-module/ Copy the generated pl.dtsi file (under project_1/project_1.sdk/device_tree_bsp_0/ directory) into arch/microblaze/boot/dts/ Linux directory. Use the generated system-top.dts file (under project_1/project_1.sdk/device_tree_bsp_0/ directory) to create the xilinx.dts file into arch/microblaze/boot/dts/ Linux directory. Be carefull with stdout options in the xilinx.dts file if you want Linux output enabled. Mine is: /dts-v1/; /include/ "pl.dtsi" / { chosen { bootargs = "console=ttyUL0,9600"; linux,stdout-path = &axi_uartlite_0; stdout-path = &axi_uartlite_0; }; aliases { ethernet0 = &axi_ethernetlite_0; serial0 = &axi_uartlite_0; i2c0 = &axi_iic_0; i2c1 = &axi_iic_1; }; memory { device_type = "memory"; reg = <0x80000000 0x8000000>; }; }; &axi_ethernetlite_0 { local-mac-address = [00 0a 35 00 00 00]; }; Generate your init RAM Disk for root File sytem. I suppose that you can do this. Generate your Linux kernel. I suppose that you can do this: $ make ARCH=microblaze CROSS_COMPILE=microblazeel-xilinx-linux-gnu- simpleImage.xilinx -j 4 Program the FPGA device and download the simpleImage.xilinx file (kernel + init RAM Disk) under arch/microblaze/boot directory into RAM with the JTAG interface and finally execute. That's all folks! Ramdisk addr 0x00000000, Compiled-in FDT at c03ad4f8 Linux version 4.14.0-00493-gb68293ad2c93-dirty (kadionik@ipcchip) (gcc version 8 setup_cpuinfo: initialising setup_cpuinfo: Using full CPU PVR support wt_msr_noirq setup_memory: max_mapnr: 0x8000 setup_memory: min_low_pfn: 0x80000 setup_memory: max_low_pfn: 0x88000 setup_memory: max_pfn: 0x88000 Zone ranges: DMA [mem 0x0000000080000000-0x0000000087ffffff] Normal empty Movable zone start for each node Early memory node ranges node 0: [mem 0x0000000080000000-0x0000000087ffffff] Initmem setup node 0 [mem 0x0000000080000000-0x0000000087ffffff] On node 0 totalpages: 32768 free_area_init_node: node 0, pgdat c0525af4, node_mem_map c07a2000 DMA zone: 256 pages used for memmap DMA zone: 0 pages reserved DMA zone: 32768 pages, LIFO batch:7 pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 pcpu-alloc: [0] 0 Built 1 zonelists, mobility grouping on. Total pages: 32512 Kernel command line: console=ttyUL0,9600 PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 121948K/131072K available (3765K kernel code, 121K rwdata, 1312K rodata) Kernel virtual memory layout: * 0xffffe000..0xfffff000 : fixmap * 0xffffe000..0xffffe000 : early ioremap * 0xf0000000..0xffffe000 : vmalloc & ioremap NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 irq-xilinx: /amba_pl/interrupt-controller@41200000: num_irq=5, edge=0x6 /amba_pl/timer@41c00000: irq=1 clocksource: xilinx_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_is xilinx_timer_shutdown xilinx_timer_set_periodic sched_clock: 32 bits at 100MHz, resolution 10ns, wraps every 21474836475ns Calibrating delay loop... 49.15 BogoMIPS (lpj=245760) pid_max: default: 4096 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) random: get_random_u32 called from bucket_table_alloc+0x2e4/0x35c with crng_ini0 clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 191s NET: Registered protocol family 16 clocksource: Switched to clocksource xilinx_clocksource NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 1024 (order: 2, 20480 bytes) TCP: Hash tables configured (established 1024 bind 1024) UDP hash table entries: 128 (order: 0, 6144 bytes) UDP-Lite hash table entries: 128 (order: 0, 6144 bytes) NET: Registered protocol family 1 RPC: Registered named UNIX socket transport module. RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. random: fast init done Skipping unavailable RESET gpio -2 (reset) workingset: timestamp_bits=30 max_order=15 bucket_order=0 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) io scheduler mq-deadline registered io scheduler kyber registered Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled 40600000.serial: ttyUL0 at MMIO 0x40600000 (irq = 5, base_baud = 0) is a uartlie console [ttyUL0] enabled brd: module loaded libphy: Fixed MDIO Bus: probed xilinx_emaclite 40e00000.ethernet: Device Tree Probing xilinx_emaclite 40e00000.ethernet: Failed to register mdio bus. xilinx_emaclite 40e00000.ethernet: MAC address is now 00:0a:35:00:00:00 xilinx_emaclite 40e00000.ethernet: Xilinx EmacLite at 0x40E00000 mapped to 0xF02 i2c /dev entries driver NET: Registered protocol family 17 Freeing unused kernel memory: 2296K This architecture does not have kernel memory protection. Hostname : nexys4ddr Kernel release : Linux 4.14.0-00493-gb68293ad2c93-dirty Kernel version : #120 Thu Dec 6 16:51:57 CET 2018 Please press Enter to activate this console. nexys4ddr:/# For the first I2C sensor (onboard ADT7420 sensor of the Nexys4 DDR board), we must use the /dev/i2c/0 (or /dev/i2c/i2c-0) character driver file (Major=89 minor=0). For the second I2C sensor (external TCN75A PMOD TMP3 sensor), we must use the /dev/i2c/1 (or /dev/i2c/i2c-1) character driver file (Major=89 minor=1). nexys4ddr:/# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- 4b -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- nexys4ddr:/# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- You can now use the Linux API for reading the I2C sensors... Pat.
  4. Scarlet

    Zybo Z7-10 with Linaro

    I am trying to boot Linux with Linaro file system on Zybo Z7-10 without Petalinux. I would like to connect a monitor to HDMI TX output to be able to see Linaro graphical interface but I am getting errors while Linaro Ubuntu is booting, and nothing is being shown on the monitor. I am sure that HDMI output works on my board since I got HDMI demo project to work. I am using Zybo base system design from here, adapted to Zybo Z7 on Vivado 2018.2. I have generated device tree from this design using Xilinx SDK following this tutorial. I am using Digilent's u-boot and Linux kernel and I've downloaded Linaro file system from here (last file). These are the errors that are showing up when Linaro Ubuntu is booting: systemd-bootchart.service failed. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Create Static Device Nodes in /dev. Starting udev Kernel Device Manager... Starting Load/Save Random Seed... [ OK ] Reached target Local File Systems (Pre). [FAILED] Failed to start Load Kernel Modules. See "systemctl status systemd-modules-load.service" for details. systemd-modules-load.service failed. Starting Apply Kernel Variables... [ OK ] Started udev Coldplug all Devices. [ OK ] Started Increase datagram queue length. [FAILED] Failed to mount Temporary Directory. See "systemctl status tmp.mount" for details. [FAILED] Failed to start RealtimeKit Scheduling Policy Service. See "systemctl status rtkit-daemon.service" for details. My goal is to enable HDMI output on Zybo Z7. I suspect that these errors are the cause of the problem, but I am not sure if there is any additional step I need to perform to get HDMI to work, like enabling some drivers in Linux kernel, or configuring the device tree. I have tried using different Linux kernel versions (by checking out different tags from Digilent's repository), using different versions of Linaro file system, using default device tree for Zybo Z7 provided with Linux kernel, but I've had no success since various errors are always showing up. I would appreciate any help or someone pointing me in the right direction, since I am not sure what is the cause of the problem. Thank you!
  5. Hello: I am unable to get Ethernet interface to work on Genesys-2 in my design which is migrated from a Xilinx board. I have a Microblaze based design that I am trying to port to Genesys-2 Board. This design is working on Xilinx KC705 evaluation board which uses the same Kintex-7 FPGA as Genesys-2. On this design I have Ethernet interface, DDR3 Interface and some other peripherals. We are using Linux for this design. This design was originally developed by another company and was used for evaluating their chip. It was developed on Xilinx evaluation board KC705. This company does not support any other evaluation board. I am hoping to get some help from forum experts to bring-up this design. For this design on Xilinx KC705 board after power up, downloading the bit file and running the SW from *.elf file we can open a PUTTY terminal and issue 'ifconfig' command to check whether the ethernet interface is up and which IP address it got. This works for Xilinx board. But the same does not work for Genesys-2 board, I can issue 'ifconfig' command but I don't see the ethernet interface active. I had looked for pinout differences and made changes accordingly. When I described the symptoms to the original authors of the design they said that because the PHY is different between the two boards I have to update the device tree. Below is the device tree from Xilinx KC705 design. Ethernet Device Tree axi_ethernet: ethernet@40e00000 { compatible = "xlnx,xps-ethernetlite-1.00.a"; device_type = "network"; interrupt-parent = <&axi_intc>; interrupts = <1 0>; local-mac-address = [00 0a 35 00 00 02]; phy-handle = <&phy0>; reg = <0x40e00000 0x2000>; xlnx,duplex = <0x1>; xlnx,include-global-buffers = <0x1>; xlnx,include-internal-loopback = <0x0>; xlnx,include-mdio = <0x1>; xlnx,rx-ping-pong = <0x1>; xlnx,s-axi-id-width = <0x1>; xlnx,select-xpm = <0x1>; xlnx,tx-ping-pong = <0x1>; xlnx,use-internal = <0x0>; axi_ethernet_mdio: mdio { #address-cells = <1>; #size-cells = <0>; phy0: phy@7 { device_type = "ethernet-phy"; reg = <7>; }; }; }; PHY on Xilinx KC705 board is Marvell 88e1111. PHY on Genesys-2 is RealTek RTL8211E. The original authors of the design had suggested that at a minimum the line "reg = <7>;' should be changed for Genesys-2. My questions on the forum are below. 1) How should I modify the device tree for Ethernet for Genesys-2 board? 2) Does it seem that just changing the device tree for Ethernet will fix our issue? 3) Any suggestions on how to debug this issue? Thank you so much. Best regards,
  6. I am trying to access the audio codec SSM2603 on ZYBO over i2c interface from linux user-space for some register get and set, what i did so far I enabled in the device-tree PS I2C_0 in system-user.dtsi &i2c0 { ssm2603: ssm2603@1a{ #sound-dai-cells = <0>; compatible = "adi,ssm2603"; reg = <0x1a>; }; i2cdetect -l output i2c-1 i2c Cadence I2C at e0004000 I2C adapter i suppose i2c coec should appear on address 0x1a but nothing i2cdetect -y -r 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- if i add the codec drivers in my kernel snd_soc_ssm2602_i2c.ko and snd_soc_ssm2602.ko the i2cdetect -y -r 1 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- -- which means the i2c device is detected on 0x1a address but its been used by the driver. what i want to do is to make the raw i2c register get /set using i2cget/i2cset but the codec didn't appear without driver, any clue?
  7. deppenkaiser

    Vivado-SDK 2017.2 Linux

    Hello, i have a problem with the Vivado SDK. I like to include some c Header: #include <stdio.h> #include <unistd.h> #include <stdbool.h> #include <string.h> #include <arpa/inet.h> #include <sys/select.h> #include <sys/socket.h> Eclipse tell me, that my includes are unresolved. I think that is because i have nearly thirty directories in my Vivado 2017.2 SDK Installation, but it is not defined what directory exactly should be used. Can anybody tell me what is the correct include path for a 32 bit Linux application for my arty board? Thank you...
  8. Guacamoleroger

    Linux on Digilent boards

    Hi, guys, I am in need of a Digilent board to run Linux with a GUI to have access to IOpins and peripherals, and also to work together with the vhdl codes on the FPGA. I am not sure how to install Linux on SD card, start a boot from there, ANDhave at the same time a vhdl code running on FPGA that I could edit and compile using the vivado (2018.2). The idea is to have the vhdl code running the hardware and the GUI on linux to present values of input, output, make the configuration on-line of the vhdl variables, etc... I was thinking about the Zybo board. Can someone give me, please, some directions and/or suggestions? Regards,
  9. studogger

    Embedded-Linux-Tutorial-Zybo

    Hi, I came across this tutorial that @Commanderfranz created for the Zybo https://www.instructables.com/id/Embedded-Linux-Tutorial-Zybo/. It is also referenced here: https://blog.digilentinc.com/zybo-embedded-linux-hands-on-tutorial/, which also includes the "Embedded Linux Tutorial for the Zedboard". As far as I can tell the Embedded Linux Tutorial for the Zedboard uses the Xilinx ISE instead of Vivado. What differences will there be to follow the "Embedded Linux Tutorial for the Zedboard" tutorial in Vivado? Likewise, what differences will I have to make if I follow the https://www.instructables.com/id/Embedded-Linux-Tutorial-Zybo/ on the Zedboard? My initial skimming of the tutorial makes me think that the most obvious thing will be changing the constraints to match the Zedboard for the custom LED IP that is being created. The only other thing that I see that would need to be changed is creating the base system. The base Zybo system looks like a simple Zynq IP with a few GPIO modules to support the LEDS, switches and buttons. Is there anything else that I would need to include for it? Or perhaps is there a better/bigger image of what the Zybo base system looks like? Thanks, Stuart
  10. yohboy

    Zybo linux and PMOD WIFI

    Hello, I recently received a PMOD wifi (the digilent one). I want to connect it to my zybo, already running linux-yocto with spi interface etc ... So I don't think I need the IP pmod wifi, I can make the connection myself. My question is, is there a getting started to make work the PMOD wifi ? e.g. some code to comminucate with the module. regards, Yohan
  11. Victor McKeighan

    Install Failed for Linux Runtime

    I'm trying to install the Linux Runtime under cygwin on a Windows 10 platform. Getting this message on the first library file: I checked to make sure lib64/libdabs.so exists, and it does, so I don't understand the error. Could this be a privileges issue? I am the administrator on the PC. Do I need to do something to run with root privilege? I did install the SDK without this problem. Hope someone can help. Thanks, Vic
  12. There do not seem to be any specifications for CPU platforms and Linux OSes that work best with the Analog Discovery 2 (i.e. that run the software and can keep up with the sample rate of the device). I see from past questions that it doesn't work properly with any model of Raspberry Pi (seems to be a Pi hardware problem, not Digilent's fault) and there are problems installing certain libraries on various Linux versions. From my experience with the HackRF One, you need a powerful enough CPU that can keep up with the sample rate being generated by the device without overruns or totally consuming the CPU capacity. Plus the operating system and library versions need to be compatible with what the software was compiled on (preferably identical). Since Digilent doesn't publish such detailed information on their website, I thought I'd ask forum members - what Linux systems are people using successfully with the Analog Discovery 2 and are happy with? Exact OS and platform would be helpful (i.e. Dell XPS 13 laptop running Ubuntu version 9999.1). Thank you.
  13. Hi, I'm running Arch Linux (https://archlinuxarm.org/platforms/armv7/xilinx/zedboard) on Zedboard and I'd like to use the OTG-USB as a host, but my Zedboard doesn't seem to detect the device plugged in (I've tried a USB flash drive). What are your suggestions? I've followed the instructions on http://zedboard.org/sites/default/files/documentations/GS-AES-Z7EV-7Z020-G-V7-1.pdf , but Zedboard just won't see the device.
  14. Hello, I am having trouble outputting sound on Linux using SSM2603. The SSM2603 device driver loads normally. It is also registered in ALSA sound card list. However, "input / output error" is raised in "alsactl init". ("amixer" is also the same.) It plays when I play wave file with "aplay" but it does not output to "R/LOUT pin" of SSM2603. Regards, Namio
  15. Hello all, I have a question pertaining to my ZedBoard. I'm running Linux on the PS using the built in SD card slot. I'm simultaneously building an isolated system in the PL, currently consisting of a Microblaze running a baremetal application. Now I'd like to run Python in the PL without touching the PS setup. Could I use the SD card Pmod to persist Linux to run on the Microblaze? I know I can't touch the existing SPI since it belongs to the PS, and I'd also like plenty of storage. Thank you for your time
  16. Kampi

    Ethernet for Zybo Linux

    Hello, my ethernet for my Zybo doesn´t work with Linux. I use this linaro as my rootfs. Additional I follow these instructions to create my Design with all necessary files. My Linux boots up, but I got the message "no phy found". I´ve update my device tree with this: ZyboEthernet.dtsi &gem0 { #address-cells = <1>; #size-cells = <0>; clock-names = "ref_clk", "aper_clk"; clocks = <&clkc 13>, <&clkc 30>; compatible = "cdns,zynq-gem", "cdns,gem"; interrupt-parent = <&intc>; interrupts = <0 22 4>; local-mac-address = [00 0a 35 00 00 00]; phy-handle = <&phy0>; phy-mode = "rgmii-id"; status = "okay"; reg = <0xe000b000 0x1000>; xlnx,eth-mode = <0x1>; xlnx,has-mdio = <0x1>; xlnx,ptp-enet-clock = <111111115>; mdio { #address-cells = <1>; #size-cells = <0>; phy0: phy@1 { compatible = "realtek,RTL8211E"; device_type = "ethernet-phy"; reg = <1>; }; }; }; Bootargs.dts /include/ "system-top.dts" /include/ "ZyboEthernet.dtsi" / { chosen { bootargs = "console=ttyPS0,115200n8 consoleblank=0 root=/dev/mmcblk0p2 rw rootwait earlyprintk"; linux,stdout-path = "&uart1"; }; }; How can I get my ethernet running? Thank you for help!
  17. I would like to get a HDMI Video output working with Petalinux on the Zybo Z7-10, and would appreciate any pointers, links etc. I'm particularly interested in how you get Xilinx DRM working on the Zybo Z7-10. I've seen quite a few posts on the old (VGA) Zybo, and running Xillinux, and also designs using the Xylon video cores. My design will be based on zybo-z7-10-base-linux. Eventually, I'd like to get an Ubuntu installation running Xfce working. Thanks Andy
  18. deppenkaiser

    Linux Driver

    Hello, i made the following design: You can see two GPIO Ports: - GPIO_RGB_LED, 3 Bit, Output only - GPIO_SW, two data bits plus one interrupt bit (e.g. Input clk), this port should throw Interrupts into the Linux App. After i build that design with Vivado, i used petalinux to create a Linux image. Here you can see the "/dev"-Folder which contains the installed Drivers: You can see three GPIO-Drivers. Now my question: In former questions i ask for the Driver Support in Linux and how i can write or use them. You told me, that there is a simple way to access memory mapped ip-cores with the "uio"-Driver. First i was glad to see that the Drivers are automaticaly added to the image. But i'am missing the expected "uio"-Drivers. What must i do to get the "uio"-Drivers for my design with petalinux? Thank you...
  19. a.gamez

    Ethernet on ARTY with Linux

    Hi! I've implemented a Microblaze system on the ARTY board, which includes a Texas Instruments DP83848 PHY chip to manage ethernet communications. Xilkernel and example program 'echo server' works wonderfully, so any hardware issue is discarded. However, on linux (using both mainstream and xilinx' github repo), I can't get ethernetlite core to work. This is the info I can provide: axi_ethernetlite_0: ethernet@40e00000 { compatible = "xlnx,xps-ethernetlite-1.00.a"; device_type = "network"; interrupt-parent = <&microblaze_0_axi_intc>; interrupts = <1 0>; reg = <0x40e00000 0x10000>; xlnx,duplex = <0x1>; xlnx,include-global-buffers = <0x1>; xlnx,include-internal-loopback = <0x0>; xlnx,include-mdio = <0x1>; xlnx,rx-ping-pong = <0x1>; xlnx,s-axi-id-width = <0x1>; xlnx,tx-ping-pong = <0x1>; xlnx,use-internal = <0x0>; axi_ethernetlite_0_mdio: mdio { #address-cells = <1>; #size-cells = <0>; phy0: phy@0 { device_type = "ethernet-phy"; reg = <0>; }; }; }; phy0 section was written by me, as it was not provided by dts creation utility for the SDK. dmesg output: xilinx_emaclite 40e00000.ethernet: Device Tree Probing xilinx_emaclite 40e00000.ethernet: Failed to register mdio bus. xilinx_emaclite 40e00000.ethernet: error registering MDIO bus xilinx_emaclite 40e00000.ethernet: MAC address is now 00:0a:35:00:00:00 xilinx_emaclite 40e00000.ethernet: Xilinx EmacLite at 0x40E00000 mapped to 0xF0140000, irq=2 Relevant kernel config: CONFIG_NET_VENDOR_XILINX=y CONFIG_XILINX_EMACLITE=y CONFIG_PHYLIB=y CONFIG_DP83848_PHY=y CONFIG_XILINX_PHY=y eth0 interface appears, and ifconfig eth0 192.168.1.222 doesn't produce any error. However, no other host on the network can reach the ARTY nor viceversa, not by ping, nor by poking at any random port. Any ideas? Thanks!
  20. I am having a similar issue when running as a normal user under Ubuntu 16.04.4 LTS and have installed the following packages per the standard instructions for running the Analog Discovery 2 device. ii digilent.adept.runtime 2.17.1 amd64 Digilent Adept Runtime ii digilent.waveforms 3.7.5 amd64 Digilent WaveForms Currently I am only able to run waveforms under "sudo" and not as a standard user. As a standard user executing env LD_LIBRARY_PATH=/usr/lib/digilent/waveforms/qtlibs gdb /usr/lib/digilent/waveforms/waveforms Thread 10 "waveforms" received signal SIGSEGV, Segmentation fault 0x00007fffecce2fc6 in libusb_close () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 The Full Backtrace is as follows #0 0x00007fffecce2fc6 in libusb_close () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #1 0x00007fff375e492d in CloseDevice () from /usr/lib64/digilent/adept/libftd2xx.so #2 0x00007fff375e5c91 in OpenDevice () from /usr/lib64/digilent/adept/libftd2xx.so #3 0x00007fff375e61ed in FTCommonOpen () from /usr/lib64/digilent/adept/libftd2xx.so #4 0x00007fff375e633e in FT_OpenEx () from /usr/lib64/digilent/adept/libftd2xx.so #5 0x00007fffefd55cae in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #6 0x00007fffefd501b3 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #7 0x00007fffefd4c6f8 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #8 0x00007fffefd4a3d6 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #9 0x00007fffefd498dc in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2 #10 0x00007ffff395a6ba in start_thread (arg=0x7fffc4907700) at pthread_create.c:333 #11 0x00007ffff48b941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Running strace this line appears 3 times: open("/dev/bus/usb/002/004", O_RDWR) = -1 EACCES (Permission denied) At a glance this appears to be a permission issue for accessing the USB port/driver for this device; is there a recommended adjustment or fix for this at this time?
  21. Hi all, I m beginner in Fpga, actually i dont know anything in FPGA. Last week I bought a zybo z7-10 board from diligent store. I want to run a linux on this borad, for that i did everything as per the tutorial link:http://www.instructables.com/id/Setting-up-the-Zybot-Software/ And i installed linario in the sdcard. I only have a VGA monitor to connect to zybo, so that i used a vga to hdmi converter and boot the zybo. But i cant see nothing in the screen except the text "Input Not Supported". Three leds in the board is lighted up and glow still. I dont know , whats the actual problem with this? Can anyone help me... Thanks in advance
  22. I had a working Debian 8 production system using python2.7 to talk to an Analog Discovery 2. I decided to update the .deb packages to be current and now I get "Segmentation fault" "stack smashing detected" when I try to start my python program. I was using the amd64.deb files: digilent.adept.runtime 2.16.6 digilent.waveforms 3.5.4 (for the libdwf.so file) Upgraded to digilent.adept.runtime 2.17.1 digilent.waveforms 3.7.5 Also on the system is digilent.adept.utilities 2.2.1. I tested just upgrading the runtime package and my program works. Upgrading the waveforms package (and thus libdwf.so) causes the segfault. Any thoughts on how I might track down where the problem is?
  23. tekson

    Delay

    Hi all, How to implent delay in verilog code? I want to run a led blink code with one second delay using zynq zybo-7-z10 Thanks in advance
  24. Hi all, I m beginner in Fpga, actually i dont know anything in FPGA. Last week I bought a zybo z7-10 board from diligent store. I want to run a linux on this borad, for that i did everything as per the tutorial link:http://www.instructables.com/id/Setting-up-the-Zybot-Software/ And i installed linario in the sdcard. I only have a VGA monitor to connect to zybo, so that i used a vga to hdmi converter and boot the zybo. But i cant see nothing in the screen except the text "Input Not Supported". Three leds in the board is lighted up and glow still. I dont know , whats the actual problem with this? Can anyone help me... Thanks in advance