element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
ZedBoard Hardware Design AD-FMCOMMS1-EBZ Zedboard problems with a custom design
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 352 subscribers
  • Views 485 views
  • Users 0 members are here
Related

AD-FMCOMMS1-EBZ Zedboard problems with a custom design

Former Member
Former Member over 12 years ago

Hi,

I'm working with a Zedboard and I have correctly implemented the reference design from here:
http://wiki.analog.com/resources/eval/user-guides/ad-fmcomms1-ebz/reference_hdl

Now I'm interested in creating my own design from the reference design. I have just removed the modules HDMI, spdif, GPIO and modified the DTS file but I still cannot communicate with the board AD-FMCOMMS1-EBZ. I attach the response I get when booting Linaro Linux OS through a SD card:



U-Boot 2012.04.01 (Jun 26 2013 - 11:27:41)

DRAM:  512 MiB
WARNING: Caches not enabled
MMC:   SDHCI: 0
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   zynq_gem
Hit any key to stop autoboot:  0
Copying Linux from SD to RAM...
Device: SDHCI
Manufacturer ID: 73
OEM: 4247
Name: NCard
Tran Speed: 25000000
Rd Block Len: 512
SD version 2.0
High Capacity: Yes
Capacity: 7.5 GiB
Bus Width: 4-bit
reading zImage

2795528 bytes read
reading devicetree.dtb

8646 bytes read
reading ramdisk8M.image.gz

** Unable to read "ramdisk8M.image.gz" from mmc 0:1 **
## Starting application at 0x00008000 ...
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Linux version 3.6.0 (srivas@PW7I-4-D-367) (gcc version 4.6.3 (Sourcery CodeBench Lite 2012.03-79) ) #1 SMP PREEMPT Wed Jun 26 11:11:09 CEST 2013
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Xilinx Zynq Platform, model: Xilinx Zynq ZC702
bootconsole [earlycon0] enabled
cma: CMA: reserved 40 MiB at 1d800000
Memory policy: ECC disabled, Data cache writealloc
PERCPU: Embedded 7 pages/cpu @c0e59000 s7872 r8192 d12608 u32768
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyPS0,115200 root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext4 rootwait devtmpfs.mount=0
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 468060k/468060k available, 56228k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc04cc1b8   (4881 kB)
      .init : 0xc04cd000 - 0xc04f4ec0   ( 160 kB)
      .data : 0xc04f6000 - 0xc05466a0   ( 322 kB)
       .bss : 0xc05466c4 - 0xc0a4d750   (5149 kB)
Preemptible hierarchical RCU implementation.
tRCU lockdep checking is enabled.
tDump stacks of tasks blocking RCU-preempt GP.
tRCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
NR_IRQS:512
MIO pin 11 not assigned(00001760)
xslcr mapped to e0802000
Zynq clock init
timer #0 at e0804000, irq=43
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
Console: colour dummy device 80x30
Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
... MAX_LOCKDEP_SUBCLASSES:  8
... MAX_LOCK_DEPTH:          48
... MAX_LOCKDEP_KEYS:        8191
... CLASSHASH_SIZE:          4096
... MAX_LOCKDEP_ENTRIES:     16384
... MAX_LOCKDEP_CHAINS:      32768
... CHAINHASH_SIZE:          16384
memory used by lock dependency info: 3695 kB
per task-struct memory footprint: 1152 bytes
Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
Setting up static identity map for 0x360ec0 - 0x360ef4
L310 cache controller enabled
l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72360000, Cache size: 524288 B
CPU1: Booted secondary processor
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Brought up 2 CPUs
SMP: Total of 2 processors activated (2664.03 BogoMIPS).
devtmpfs: initialized
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.25.
Switching to clocksource xttcps_clocksource
NET: Registered protocol family 2
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 7, 589824 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP: reno registered
UDP hash table entries: 256 (order: 2, 20480 bytes)
UDP-Lite hash table entries: 256 (order: 2, 20480 bytes)
NET: Registered protocol family 1
msgmni has been set to 994
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
xuartps e0001000.uart: failed to get alias id, errno -19
e0001console [ttyPS0] enabled, bootconsole disabled
console [ttyPS0] enabled, bootconsole disabled
xdevcfg f8007000.devcfg: ioremap f8007000 to e080e000 with size 1000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
libphy: XEMACPS mii bus: probed
xemacps e000b000.eth: pdev->id -1, baseaddr 0xe000b000, irq 54
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
xusbps-dr e0002000.usb: Unable to init USB phy, missing?
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
at24 0-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write
at24 0-0054: 256 byte 24c02 EEPROM, writable, 1 bytes/write
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: Invalid maximum block size, assuming 512 bytes
mmc0: SDHCI controller on e0100000.sdhci [e0100000.sdhci] using ADMA
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
mmc0: new high speed SDHC card at address b368
mmcblk0: mmc0:b368 NCard 7.48 GiB
cf_axi_adc 79020000.cf-ad9643-core-lpc: Device Tree Probing 'cf-ad9643-core-lpc'
platform 79020000.cf-ad9643-core-lpc: Driver cf_axi_adc requests probe deferral
spi spi32766.1: Driver ad9467 requests probe deferral
mmcblk0: p1 p2
spi_master spi32766: failed to transfer one message from queue
iio iio:device0: write failed (-110)
ad8366: probe of spi32766.6 failed with error -110
spi_master spi32766: failed to transfer one message from queue
ad9548: probe of spi32766.2 failed with error -110
spi_master spi32766: failed to transfer one message from queue
iio iio:device0: write failed (-110)
ad9523: probe of spi32766.3 failed with error -110
ERROR: could not get clock /amba@0/i2c@41600000/spi_xcomm0@58/adf4351-rx-lpc@4:clkin(0)
spi spi32766.4: Driver adf4350 requests probe deferral
ERROR: could not get clock /amba@0/i2c@41600000/spi_xcomm0@58/adf4351-tx-lpc@5:clkin(0)
spi spi32766.5: Driver adf4350 requests probe deferral
cf_axi_dds 74200000.cf-ad9122-core-lpc: Device Tree Probing 'cf-ad9122-core-lpc'
platform 74200000.cf-ad9122-core-lpc: Driver cf_axi_dds requests probe deferral
spi_master spi32766: failed to transfer one message from queue
ad9122 spi32766.0: Unrecognized CHIP_ID 0xFFFFFF92
TCP: cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Registering SWP/SWPB emulation handler
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
cf_axi_adc 79020000.cf-ad9643-core-lpc: Device Tree Probing 'cf-ad9643-core-lpc'
platform 79020000.cf-ad9643-core-lpc: Driver cf_axi_adc requests probe deferral
spi spi32766.1: Driver ad9467 requests probe deferral
ERROR: could not get clock /amba@0/i2c@41600000/spi_xcomm0@58/adf4351-rx-lpc@4:clkin(0)
spi spi32766.4: Driver adf4350 requests probe deferral
ERROR: could not get clock /amba@0/i2c@41600000/spi_xcomm0@58/adf4351-tx-lpc@5:clkin(0)
spi spi32766.5: Driver adf4350 requests probe deferral
cf_axi_dds 74200000.cf-ad9122-core-lpc: Device Tree Probing 'cf-ad9122-core-lpc'
platform 74200000.cf-ad9122-core-lpc: Driver cf_axi_dds requests probe deferral
ALSA device list:
  No soundcards found.
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:2.
Freeing init memory: 156K
init: ureadahead main process (717) terminated with status 5
Last login: Thu Jan  1 00:00:10 UTC 1970 on tty1
Welcome to Linaro 12.09 (GNU/Linux 3.6.0 armv7l)

How can I solve the problem of the SPI communication?
How does it affect my design when removing any hardware module from the reference design?

Thanks.

  • Sign in to reply
  • Cancel
  • Former Member
    0 Former Member over 12 years ago

    In response to your question 'How does it affect my design when removing any hardware module from the reference design?'

    1) DeviceTree

    Generally you must remove DTS nodes for the cores you removed from the PL. Furthermore, XPS will reorder the IRQ numbers when you remove a peripheral, and you will need to ensure the updated IRQ numbers for the remaining peripherals match those in the the DTS file. You can see the IRQ numbers in XPS when you click on the block above the 'IRQ' label on the Zynq pane. Finally, the IRQ values in the DTS need to have 32 subtracted from numbers shown in the XPS dialog. For example, 91 becomes 59, 90 becomes 58, etc. After updating the DTS, generate an updated DTB and copy it to the FAT32 partition on the SD card as 'devicetree.dtb', overwriting the previous version.

    2) BOOT.BIN

    The SD card contains the Linux zimage, devicetree.dtb and BOOT.BIN in it's FAT32 partition. When modifying the PL, you must re-generate BOOT.BIN with an updated bitstream. It isn't clear from your post whether you did this. If not, then you can take a look at the Intro and Linux trainings here on zedboard.org for instructions on generating BOOT.BIN and updating the SD card.

    http://www.zedboard.org/trainings-and-videos

    Luc

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 12 years ago

    Thank you so much DSP_1!!!
    The problem was the IRQ numbers in the DTS file. I was going crazy, I could not see that detail before. So thank you very much for showing me the light ;).

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube