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
    • FRC
    • 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 112 results

  1. Hello, I am fairly new to linux and I am trying to program a cerebot nano. I have the JTAG-USB cable with SPI, rev. b. I have downloaded wine and the AVR programmer but I don't see the device when I enumerate in the AVR programmer. If I use djtgcfg enum, from the terminal: chris@chris-T510 ~ $ djtgcfg enum Found 2 device(s) Device: DCabUsb Product Name: DCabUsb1 V2.0 User Name: DCabUsb Serial Number: 50003C003874 I did install the usb drivers that came with the AVR programmer, using wine. Any ideas?
  2. I am following the instructions in the Embedded Linux Hands-on Tutorial and got stuck at step #3 in section 4.2. The step #2 is successful with the following output : make ARCH=arm CROSS_COMPILE=arm-xilinx-linux-gnueabi- xilinx_zynq_defconfig HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c SHIPPED scripts/kconfig/zconf.hash.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf # # configuration written to .config # The command in step #3 gives the following error : make ARCH=arm CROSS_COMPILE=arm-xilinx-linux-gnueabi- scripts/kconfig/conf --silentoldconfig Kconfig make: unrecognized option '--silentoldconfig' Usage: make [options] [target] ... Options: I am using ubuntu 14.04 LTS, with Xilinx SDK version 2015.1. Please help!
  3. Hi. I managged to run both Linaro and ArchLinux on the Zybo board, with HDMI output (but i'm gonna remove it after). But I'm having some troubles to comunicate with my custom hardware. I'm used to programming in Hardware, and I made several real time high performance applications like face recognition and real time video processing on pure verilog (Nexys 3, Nexys 4, Atlys boards), but I'm kind of new to cross-compiling, linux kernels, and drivers. I have a few master AXI modules that directly communicates with the DDR3 memory using the HP ports (no DMA, VDMA or similiars), and I just reserve a fraction of the DDR3 memory to work with them. Now in Linux, all the address are virtual, so I must write a driver, or find a way to allocate physicall contiguous memory in software. -My IP usually work this way (e.g this is a sobel filter): It receives the base address where the image to process is located (usually is XRGB888 format), the resolution of the image, several arguments like threshold, and it outputs directly the result on the VGA port or HDMI port or a touchscreen that I have (all of them are custom IP) or it write the output on the DDR3 memory. If the flow requires SW interventions, It triggers a interrupt. Now that I'm using Linux, I have 3 options: Use DMA: I kind of know how to use DMA on baremetal on the software side, but I have no idea how to make a custom IP that comunicates with the DMA modules. I have a decent understanding how master and slave AXI full interfaces works tough.Write a custom driver that works the way my IP needs.Hack with things like dma-mapping, contiguous memory allocations, memory maps, etc.Make a "don't touch" region of ram for Linux, so the HW can work with it.With simple AXI peripherals that are mapped to a fixed address (0x4XXXXXXX) and doesnt communicate with the DDR3, I use mmap and to access the registers, and it work well, but I can't use interrupts. With peripherals that use the DDR3, the configuration parts is done the same way that the regular AXI peripherals, but the RAM buffer, needs to be reserved so Linux doesn't write to it, or it only do it on my command. Also I need the physicall address of that reserverd ram region to pass it to the peripheral. I'd like some highlights on how to make a custom DMA module (hardware side please), but any of the 4 options works. PS: Also, some of these modules that work with RAM doesn't even have an slave axi interface, so they won't appear on the automatic generated device tree. Any information would be usefull. Best regards. Alejandro Wolf.
  4. odougs

    Basys2 Corrupted Device ID

    Hello, I have successfully programmed my Basys2 using the 'djtgcfg' utility under Linux dozens of times, but I'm no longer able to do so. When I attempted to program the board yesterday, I got some unusual results: > djtgcfg enum Device: 3.....O......<. Product Name: Digilent Basys2-100 User Name: 3.....O......<. Serial Number: 210155528315 > djtgcfg init -d 'Basys2' ERROR: unable to open device "Basys2" > djtgcfg init -d '3.....O......<.' ERROR: unable to open device "3.....O......<." *I used the '.' character in the strings above to represent non-printable characters, because the replacement character used by my terminal won't display properly on this page. Using the product name or serial number yields a similar result. It appears that I can't communicate with the device due to a corrupted device ID. However, my computer has no trouble recognizing the Basys2 board: > lsusb ... Bus 003 Device 011: ID 1443:0007 Digilent Development board JTAG ...For what it's worth, here is the hexdump of the djtgcfg result above: > djtgcfg enum | xxd 0000000: 466f 756e 6420 3120 6465 7669 6365 2873 Found 1 device(s 0000010: 290a 0a44 6576 6963 653a 2033 fbbb b0df )..Device: 3.... 0000020: e04f a81f bdff bbf9 ec3c ad0a 2020 2020 .O.......<.. 0000030: 5072 6f64 7563 7420 4e61 6d65 3a20 2020 Product Name: 0000040: 4469 6769 6c65 6e74 2042 6173 7973 322d Digilent Basys2- 0000050: 3130 300a 2020 2020 5573 6572 204e 616d 100. User Nam 0000060: 653a 2020 2020 2020 33fb bbb0 dfe0 4fa8 e: 3.....O. 0000070: 1fbd ffbb f9ec 3cad 0a20 2020 2053 6572 ......<.. Ser 0000080: 6961 6c20 4e75 6d62 6572 3a20 2032 3130 ial Number: 210 0000090: 3135 3535 3238 3331 350a 155528315.So it appears the device ID as seen by djtgcfg is 33fb bbb0 dfe0 4fa8 1fbd ffbb f9ec 3cad 0aA couple of other details that might be helpful: I succesfully programmed a friend's Basys2 multiple times using djtgcfg after having this problem with my board. When using his board, the output from djtgcfg was normal (all printable characters).After experiencing this problem under Linux, I sucessfully programmed my Basys2 from a Windows machine. When using Adept2 under Windows, the device ID string still appears corrupted, but I am able to program it anyways. I don't have regular access to a Windows machine, so I'd really like to get this working under Linux again. I'm hoping this is just an issue of some corrupted Flash or EEPROM in the AT90USB that could be fixed by reprogramming it... but I'm not sure what to try next. Any ideas? Thanks for reading!
  5. Hello. I am working with an Atlys board. I am trying to transfer a bitstream file and a linux image to the SPI flash. In windows I remember doing it from the flash tab in the Adept application. Now I am working on a linux computer and I've installed the Adept 2 runtime and utilities. I've read the man pages for the 3 utilities (dadutil, djtgcfg and dsumecfg) but it is still not clear to me if it is posible to transfer to SPI flash using these utilities. Is it?
  6. endluri.ram

    How does the Zynq system works?

    Hi, I am currently using Zybo board. I have followed the " Embedded Linux® Hands-on Tutorial for the ZYBO™ " tutorial. My question is how does the Zynq system works? Is it similar to Microblaze soft processor or is it just FPGA? I have done the same work in the tutorial using Microblaze processor and XIlinx ISE. I find in the specs that Zynq hosts 2 ARM cortex processors, I want to know when we run above the above tutorial are we using any soft processor or if we are using the ARM Cortex processor? My point is if any soft processor is involved we can eliminate it and use the ARM processors so that we can achieve more speed. Thank you in advance.
  7. I was wondering if anyone could guide me in the right direction for troubleshooting a USB peripheral connection with the Zybo board running embedded Digilent Linux. My boot is as follows, which shows the USB root device (not OTG - the title is a mistake) appears to be loaded properly but no USB devices show: U-Boot 2014.01-00005-gc29bed9 (Feb 01 2015 - 22:39:09) I2C: ready Memory: ECC disabled DRAM: 512 MiB MMC: zynq_sdhci: 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 Out: serial Err: serial Net: Gem.e000b000 Hit any key to stop autoboot: 0 Device: zynq_sdhci Manufacturer ID: 27 OEM: 5048 Name: SD04G Tran Speed: 50000000 Rd Block Len: 512 SD version 3.0 High Capacity: Yes Capacity: 3.7 GiB Bus Width: 4-bit reading uEnv.txt ** Unable to read file uEnv.txt ** Copying Linux from SD to RAM... reading uImage 3819360 bytes read in 340 ms (10.7 MiB/s) reading devicetree.dtb 7374 bytes read in 18 ms (399.4 KiB/s) reading uramdisk.image.gz 3694172 bytes read in 329 ms (10.7 MiB/s) ## Booting kernel from Legacy Image at 03000000 ... Image Name: Linux-3.14.0-xilinx-13567-g906a2 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3819296 Bytes = 3.6 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 02000000 ... Image Name: Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3694108 Bytes = 3.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 02a00000 Booting using the fdt blob at 0x2a00000 Loading Kernel Image ... OK Loading Ramdisk to 1f7a9000, end 1fb2ee1c ... OK Loading Device Tree to 1f7a4000, end 1f7a8ccd ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.14.0-xilinx-13567-g906a2c9 (Squirrel@centos6-6-i386) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #1 SMP PREEMPT Sun Feb 1 23:13:26 EST 2015 [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: Xilinx Zynq [ 0.000000] bootconsole [earlycon0] enabled [ 0.000000] cma: CMA: reserved 128 MiB at 17400000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] PERCPU: Embedded 8 pages/cpu @dfb9e000 s10752 r8192 d13824 u32768 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [ 0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/ram rw earlyprintk [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 371800K/524288K available (5133K kernel code, 319K rwdata, 1888K rodata, 206K init, 5339K bss, 152488K reserved, 0K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB) [ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc06e3a0c (7023 kB) [ 0.000000] .init : 0xc06e4000 - 0xc0717a00 ( 207 kB) [ 0.000000] .data : 0xc0718000 - 0xc0767d40 ( 320 kB) [ 0.000000] .bss : 0xc0767d4c - 0xc0c9eb88 (5340 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] RCU lockdep checking is enabled. [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] ps7-slcr mapped to e0802000 [ 0.000000] zynq_clock_init: clkc starts at e0802100 [ 0.000000] Zynq clock init [ 0.000016] sched_clock: 64 bits at 325MHz, resolution 3ns, wraps every 3383112499200ns [ 0.008513] ps7-ttc #0 at e0804000, irq=43 [ 0.013583] Console: colour dummy device 80x30 [ 0.017925] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar [ 0.026005] ... MAX_LOCKDEP_SUBCLASSES: 8 [ 0.030023] ... MAX_LOCK_DEPTH: 48 [ 0.034195] ... MAX_LOCKDEP_KEYS: 8191 [ 0.038612] ... CLASSHASH_SIZE: 4096 [ 0.042966] ... MAX_LOCKDEP_ENTRIES: 16384 [ 0.047438] ... MAX_LOCKDEP_CHAINS: 32768 [ 0.051939] ... CHAINHASH_SIZE: 16384 [ 0.056383] memory used by lock dependency info: 3695 kB [ 0.061828] per task-struct memory footprint: 1152 bytes [ 0.067275] Calibrating delay loop... 1292.69 BogoMIPS (lpj=6463488) [ 0.110963] pid_max: default: 32768 minimum: 301 [ 0.116272] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.122815] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.137416] CPU: Testing write buffer coherency: ok [ 0.143727] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.149367] Setting up static identity map for 0x4deb20 - 0x4deb78 [ 0.155737] L310 cache controller enabled [ 0.159695] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB [ 0.240373] CPU1: Booted secondary processor [ 0.328288] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.329286] Brought up 2 CPUs [ 0.342149] SMP: Total of 2 processors activated. [ 0.346849] CPU: All CPU(s) started in SVC mode. [ 0.354942] devtmpfs: initialized [ 0.365684] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.380025] regulator-dummy: no parameters [ 0.393190] NET: Registered protocol family 16 [ 0.401863] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.415505] cpuidle: using governor ladder [ 0.419488] cpuidle: using governor menu [ 0.446479] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered [ 0.458166] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.466285] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.472549] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xe0880000 [ 0.544156] bio: create slab <bio-0> at 0 [ 0.553161] vgaarb: loaded [ 0.557675] SCSI subsystem initialized [ 0.563866] usbcore: registered new interface driver usbfs [ 0.569764] usbcore: registered new interface driver hub [ 0.575516] usbcore: registered new device driver usb [ 0.582260] media: Linux media interface: v0.10 [ 0.587089] Linux video capture interface: v2.00 [ 0.592334] pps_core: LinuxPPS API ver. 1 registered [ 0.597169] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.606720] PTP clock support registered [ 0.611712] EDAC MC: Ver: 3.0.0 [ 0.617963] Advanced Linux Sound Architecture Driver Initialized. [ 0.634062] DMA-API: preallocated 4096 debug entries [ 0.638903] DMA-API: debugging enabled by kernel config [ 0.644867] Switched to clocksource arm_global_timer [ 0.708238] NET: Registered protocol family 2 [ 0.715250] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [ 0.722338] TCP bind hash table entries: 4096 (order: 5, 147456 bytes) [ 0.730569] TCP: Hash tables configured (established 4096 bind 4096) [ 0.737032] TCP: reno registered [ 0.740170] UDP hash table entries: 256 (order: 2, 20480 bytes) [ 0.746333] UDP-Lite hash table entries: 256 (order: 2, 20480 bytes) [ 0.753847] NET: Registered protocol family 1 [ 0.759760] RPC: Registered named UNIX socket transport module. [ 0.765613] RPC: Registered udp transport module. [ 0.770279] RPC: Registered tcp transport module. [ 0.775041] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.782471] Trying to unpack rootfs image as initramfs... [ 0.789428] rootfs image is not initramfs (no cpio magic); looks like an initrd [ 0.820701] Freeing initrd memory: 3604K (df7a9000 - dfb2e000) [ 0.826926] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available [ 0.840797] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.854401] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 0.862054] msgmni has been set to 989 [ 0.867470] io scheduler noop registered [ 0.871278] io scheduler deadline registered [ 0.875743] io scheduler cfq registered (default) [ 0.898146] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208 [ 0.905152] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16 [ 0.917201] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3125000) is a xuartps [ 0.926628] console [ttyPS0] enabled [ 0.926628] console [ttyPS0] enabled [ 0.933683] bootconsole [earlycon0] disabled [ 0.933683] bootconsole [earlycon0] disabled [ 0.945191] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to e0866000 [ 0.955067] [drm] Initialized drm 1.1.0 20060810 [ 0.993196] brd: module loaded [ 1.015640] loop: module loaded [ 1.031437] m25p80 spi0.0: found s25fl128s1, expected n25q128 [ 1.037538] m25p80 spi0.0: s25fl128s1 (16384 Kbytes) [ 1.042563] 4 ofpart partitions found on MTD device spi0.0 [ 1.048028] Creating 4 MTD partitions on "spi0.0": [ 1.052776] 0x000000000000-0x000000400000 : "qspi-fsbl-uboot" [ 1.066957] 0x000000400000-0x000000900000 : "qspi-linux" [ 1.076913] 0x000000900000-0x000000920000 : "qspi-device-tree" [ 1.087381] 0x000000920000-0x000001000000 : "qspi-user" [ 1.106651] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 1.112402] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 1.124122] libphy: XEMACPS mii bus: probed [ 1.130924] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54 [ 1.141681] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.148901] ehci-pci: EHCI PCI platform driver [ 1.156590] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing? [ 1.164005] usbcore: registered new interface driver usb-storage [ 1.172938] mousedev: PS/2 mouse device common for all mice [ 1.180566] i2c /dev entries driver [ 1.193029] zynq-edac f8006000.ps7-ddrc: ecc not enabled [ 1.199256] cpufreq_cpu0: failed to get cpu0 regulator: -19 [ 1.207779] Xilinx Zynq CpuIdle Driver started [ 1.214034] sdhci: Secure Digital Host Controller Interface driver [ 1.220346] sdhci: Copyright(c) Pierre Ossman [ 1.224626] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.230854] mmc0: no vqmmc regulator found [ 1.234961] mmc0: no vmmc regulator found [ 1.274795] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA [ 1.293987] usbcore: registered new interface driver usbhid [ 1.301630] usbhid: USB HID core driver [ 1.318453] TCP: cubic registered [ 1.321696] NET: Registered protocol family 17 [ 1.326698] Registering SWP/SWPB emulation handler [ 1.333921] regulator-dummy: disabling [ 1.338378] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 1.355963] mmc0: new high speed SDHC card at address 0007 [ 1.364071] mmcblk0: mmc0:0007 SD04G 3.70 GiB [ 1.371979] ALSA device list: [ 1.375373] No soundcards found. [ 1.375572] mmcblk0: p1 [ 1.383186] RAMDISK: gzip image found at block 0 [ 1.798555] EXT2-fs (ram0): warning: mounting unchecked fs, running e2fsck is recommended [ 1.807032] VFS: Mounted root (ext2 filesystem) on device 1:0. [ 1.813650] devtmpfs: mounted [ 1.817039] Freeing unused kernel memory: 204K (c06e4000 - c0717000) Starting rcS... ++ Mounting filesystem ++ Setting up mdev ++ Configure static IP 192.168.1.10 ++ Starting telnet daemon ++ Starting http daemon ++ Starting ftp daemon ++ Starting dropbear (ssh) daemon [ 2.584661] random: dropbear urandom read with 8 bits of entropy available ++ Starting OLED Display insmod: can't read '/lib/modules/3.14.0-xilinx-13567-g906a2c9/pmodoled-gpio.ko': No such file or directory ++ Exporting LEDs & SWs rcS Complete zynq> lsusb zynq> However, with any device I have sitting around (some requiring power from the host USB, others not) I can't get the "lsusb" command to show them (and Linux does not print out anything stating it found anything new). I have a suspect there is something I need to do to my design, but I can't figure out what. I have USB0 in the PS7 block enabled for MIO 28-39, but the actual output from the PS7 does not currently connect to anything... (doesn't the MIO bank take care of all that?). I have JP1 shorted as required. Thanks in advance!
  8. Alex

    Waveforms For Linux

    Here is a good question from customer. Can you anyone help on this? My question then is. Since you ship the SDK for Linux. Is there any possibility/roadmap for a Linux port of the WaveForms application, making the device useful also on Linux workstations?
  9. stein

    Adept installation under Linux Mint

    Hello, I'm trying to run my Basys2 board under Linux mint. I installed both the Adept runtime and the utilities for x64 using the .deb packages. Everything worked fine. If I run bar@foo ~ $ dpkg --get-selections | grep adep digilent.adept.runtime install digilent.adept.utilities install both packages seem to be installed fine. However I can not find them in the menu and I couldn't guess the konsole command so start them either. This might be a very simple question: How do I start Adpet under Linux? Thanks Matthias
  10. dffish63

    Zedboard Can Mio Pin Routing

    Hi all, I've got can4linux installed and apparently working. I'm using the Digilent linux kernel, and cannot figure out how to route the CAN_H and CAN_L out to pins I can access. Apparently you can reroute the CAN pins with a GUI in Vivado, but I can't see the comparable way in linux. Anyone know how to do this? Example? Thanks Dave
  11. math

    U-boot.elf For Zybo Zynq

    Hi, I tried to compile u-boot.elf with the instructions provided in the ZYBO-Embedded_Linux_Hands-on_Tutorial.pdf but without success. Some system setups are missing. I think some information are not updated .... Therefore, if it is possible, I would like to know if you can provide me the u-boot.elf compiled for the Zynq Zybo eval board. Thank you
  12. kypropex

    Zybo Linux

    Hi, I'm fairly new to embedded linux and I thought I'd start using my Zybo at it's full potential. So I've been following Kaitlyn Franz's tutorial on instructables and I got stuck at step 36, where you create the uramdisk.image. I can't find the initial ramdisk8M image nowhere. Could you please show me where I could find it?