Analog.com Analog Dialogue Wiki 简体中文
EngineerZone
EngineerZone
  • Log In
  • Site
  • Search
  • User
  • Support

    Popular Forums

    • RF and Microwave
    • Power Management
    • Video
    • FPGA Reference Designs
    • Precision ADCs
    • Linux Software Drivers
    • SigmaDSP Processors & SigmaStudio Dev. Tool

    Product Forums

    • A2B
    • Amplifiers
    • Analog Microcontrollers
    • Clock and Timing
    • Data Converters
    • Direct Digital Synthesis (DDS)
    • Energy Monitoring and Metering
    • Interface and Isolation
    • MEMS Inertial Sensors
    • Processors and DSP
    • Switches/Multiplexers
    • Temperature Sensors
    • Voltage References
    View All

    Application Forums

    • Audio
    • Automated Test Equipment (ATE)
    • Condition-Based Monitoring
    • Depth, Perception & Ranging Technologies
    • Embedded Vision Sensing
    • Optical Sensing
    • Precision Technology Signal Chains
    • Video
    • Wireless Sensor Networks Reference Library

    Design Center Forums

    • ACE Evaluation Software
    • ADEF System Platforms
    • Design Tools and Calculators
    • FPGA Reference Designs
    • Linux Software Drivers
    • Microcontroller no-OS Drivers
    • Reference Designs
    • Signal Chain Power (SCP)
    • Software Interface Tools
    • System Demonstration Platform (SDP) Support
  • Learn

    Recent Discussions

    • Pluto + GNURADIO frequency change
    • Pluto SDR
    • pluto sdr pyadi-iio continous iq recording
    • attribute error
    • gps-sdr-sim is not working with my ADALM-PLUTO

    Places

    • ADI Education Home
    • ADI Education China
    • ADI Education India
    • ADI Education Philippines
    • StudentZone (Analog Dialogue)
    • Virtual Classroom

    Latest Webinars

    • Optimizing GaN and GaAs RF Amplifier Performance Using Novel Biasing Techniques
    • Webinar Improving Switch-Mode Power Supplies Using Noise Cancelling Technology
    • Webinar Accelerate Your Design With a 2 to 24 GHz Wideband Transceiver Reference Design
    • How to Design an Optimized Motion Control System for Intelligent Edge Based Surveillance Camera
    • How to Enhance High Precision Current Sensing Systems
    View All
  • Community Hub

    Challenge Yourself!

      KCC's Quizzes: Buffers and Fan Out
    View All

    Places

    • Community Help
    • Logic Lounge

    Resources

    • EZ Code of Conduct
    • Getting Started Guide
    • ADI: Words Matter
    • Community Help Videos
    View All
  • Blogs

     

    How To Design Fieldbus Agnostic Smart Factory Sensors

     

    You Passed EMC Testing… But Wait, Is There More?

    Latest Blogs

    • The 5 Things You Need to Know about RF Matching Networks
    • Does Reliability Prediction Uncertainty Justify Mandating Two Channel Safety?
    • An Inside Look at 2022
    • Meet the Person Behind the Quizzes
    • Updates Required: Why Newer is Better
    Read All Blogs

    ADI Blogs

    • EZ Spotlight
    • The Engineering Mind
  • Partners

    Electronic Design Services - PartnerZone

    • Boston Engineering
    • Calian, Advanced Technologies
    • Colorado Engineering Inc. (DBA CAES AT&E)
    • Clockworks Signal Processing
    • Epiq Solutions
    • Fidus
    • PalmSens
    • Richardson RFPD
    • Tri-Star Design, Inc.
    • VadaTech
    • Vanteon
    • X-Microwave
    View All
Linux Bug Archive
  • Processors and DSP
  • Software and Development Tools
  • Linux Distribution for Blackfin
  • Linux Bug Archive
  • Cancel
Linux Bug Archive
Documents [#4997] ppitest fails for bfin_ppi driver on bf537
  • Q&A
  • Documents
  • Members
  • Tags
  • More
  • Cancel
  • +Documents
  • +ad1836: FAQ
  • +ad1938: FAQ
  • +ad1939: FAQ
  • +AD5280: FAQ
  • +ad73311: FAQ
  • +adau1361: FAQ
  • +adau1371: FAQ
  • +adau1373: FAQ
  • +adau1761: FAQ
  • +adp5588-gpio: FAQ
  • +adv7393: FAQ
  • +ADXL34x: FAQ
  • +bf518-ezbrd: FAQ
  • +bf518: FAQ
  • +bf51x: FAQ
  • +bf526-ezbrd: FAQ
  • +bf527-ezkit: FAQ
  • +bf533-stamp/ezkit: FAQ
  • +bf533: FAQ
  • +bf538-ezkit: FAQ
  • +bf548-ezkit: FAQ
  • +BF54x: FAQ
  • +bf561-ezkit: FAQ
  • +bf5xx: FAQ
  • +bfin-mac driver: FAQ
  • +bfin-uclinux-gdb: FAQ
  • +bfin_can.c: FAQ
  • +Blackfin: FAQ
  • +bluetooth: FAQ
  • +Build kernel: FAQ
  • +Build: FAQ
  • +cfcard test: FAQ
  • FAQ: [#6170] section mismatches in cifs code(2010)
  • FAQ: [#6173] linphone testing problem(2010)
  • FAQ: [#6190] BF561-EZKIT SMP kernel can not wake up by uart(2010)
  • FAQ: [#6194] libxenomai.so.0 can't be found in xenomai kernel with fdpic mode(2010)
  • FAQ: [#6207] Build error in CTS/RTS testing on board BF548-EZKIT(2010)
  • FAQ: [#6251] pread/pwrite arent decoded correctly by strace(2010)
  • FAQ: [#6253] strace build failed in trunk with outdated toolchain (missing asm/cachectl.h)(2010)
  • FAQ: [#6255] Busybox inetd crashes/rsh noconnet/ssh(2010)
  • FAQ: [#6265] libpng build fails due to not finding zlib(2010)
  • FAQ: [#6271] "nand unlock" is an unsupported command in u-boot update in nand flash(2010)
  • FAQ: [#6272] After update u-boot in spi flash, BF548-EZKIT can not boot from spi flash(2010)
  • +gadget fs bulk: FAQ
  • +gadget zero bulk: FAQ
  • +gadget zero control: FAQ
  • +Kernel xip: FAQ
  • +ltp test: FAQ
  • +microwin test: FAQ
  • +MPU kernel: FAQ
  • +Sl811-hcd.c USB: FAQ
  • +SPORT channel: FAQ
  • +trunk head kernel: FAQ
  • +usb otg driver: FAQ
  • +zlib: FAQ
  • +Illegal i2c: FAQ
  • +isp1362-hcd: FAQ
  • +Kernel: FAQ
  • +KGDBOE: FAQ
  • [#4646] Varittronix LCD driver mixes blue and Red
  • +serial driver: FAQ
  • +sigma firmware: FAQ
  • +spi transaction: FAQ
  • +strace FAQ
  • [#4787] [ltp] LTP test case shmctl01 failed in trunk for ltp-full-20081130
  • +tiff-4.0.0beta4: FAQ
  • [#5264] ping packet size test will fail for gadget ethernet test with DMA mode
  • +USBHOST: FAQ
  • +USB_EP_NI7_RXINTERVAL: FAQ
  • [#5257] Build usb gadget driver with DMA mode will fail
  • [#4708] Blackfin irda build fails for bf533-stamp
  • [#4735] unaligned accesses in qt webkit
  • [#5168] build cpufrequtils into fdpic format has error
  • [#5321] modprobe i2c lcd on bf533 stamp wait long time
  • [#4922] unwanted sound comes up after g_audio module is installed on BF548 and BF527
  • [#5176] app cpufrequtils in Blackfin app programs fails to build in FDPIC
  • [#5237] musb driver is broken after linux-2.6.30 update
  • [#5255] ping target board sometimes get wrong data byte for gadget ethernet pio mode
  • FAQ: [#6614] Kernel panic frequently when test sdio mmc on bf518-ezbrd(2011)
  • [#5336] canbus and ppifcd drivers can not be built on BF538-EZKIT
  • +SPI driver: FAQ
  • [#4714] the first time to build mtd-utils will fail in trunk
  • [#5524] drivers/video/bfin_adv7393fb.c build fails in 2.6.31 due to old i2c usage
  • [#5525] drivers/video/bf537-lq035.c build fails in 2.6.31 due to old i2c usage
  • [#5399] no sound when record in board and listen in PC for linphone test of ad1836 on bf533-stamp
  • [#5458] Drivers Serial:bfin_5xx:ttyBFx fails to generate resume from standby
  • [#4647] build samba fails on trunk now for redefinition in fcntl.h
  • [#5526] ip0x board has broken UART defines after resource reorganization
  • [#5527] drivers/media/video/blackfin/blackfin_cam.c build fails in 2.6.31 due to old i2c usage
  • [#5352] bfin_sport.c setup 2D DMA
  • [#5528] fs/binfmt_elf_fdpic.c build fails when CONFIG_ELF_CORE is enabled in 2.6.31
  • [#5464] isram_write() seems to be busted
  • [#5376] mmap05 sometimes can not pass when MPU
  • [#5534] run aplay/arecord will make system panic after kernel upgraded to 2.6.31
  • [#5361] Microwin (nanox) failed on trunk using AD7897 touch screen
  • [#5544] Sport uart TX stop waiting loop is too long to block RX interrupt in PIO mode when do duplex communication
  • [#5363] spi mmc is not supported in bf533-stamp
  • [#5550] fail to flash ubifs.img to nand
  • [#5470] build xenomai fails for no switchbench
  • [#5437] mathtest fails to compile
  • [#5551] SPI message lost when bus locked
  • [#5370] alsa tool fails to work after wake up from mem in bf537-stamp with ad1836 (can't resolve symbol)
  • [#5561] [ltp ]Kernel dump info when run ltp test cases access02, chown03, fchmod06, fchown03, fchown04
  • [#5377] amixer fail to run on ad1836 audio driver on BF537-STAMP
  • [#5475] build mkfs.ubifs on trunk head fails
  • [#5562] [ltp]some ltp test case is broken for getipckey and getcwd
  • [#5487] build usb.c fail in testsuites/usbdev/ test at asm/swab.h
  • [#5489] t2/t4 failed in gadget zero bulk test with dma mode
  • [#5567] build nand for bf537 fails on trunk
  • [#5494] Run tftlcd test case in bf548-ezkit, kernel crashed at the end
  • [#4879] traps test case 21 exception 0x3f: l1_instruction_access would make kernel panic on bf533 stamp
  • [#5568] Framebuffer DMA Error!!
  • [#5515] 4 more trap cases fails on bf533
  • [#5379] run scratchpad case sometimes would fail
  • [#5519] pushing Blackfin serial resources to boards broke many boards
  • [#5389] build pictureflow fails at branch head
  • [#5531] Usb SL811 failed on uclinux2009r1-rc6 on bf532 board.
  • [#5523] Blackfin MUSB build fails after update to 2.6.31
  • [#5391] For ad1836 and ad1981b, sometimes sound shakes at the end
  • [#5404] build kernel with 0x2000 as BOOT_LOAD address sometimes would fails at build-busybox-1.13.4
  • [#5469] CPU hardly idles anymore in svn trunk
  • [#5695] Build bf537-stamp fails at ad73322 for the latest trunk
  • [#5702] build xenomai into fdpic format fails for no libnative.so
  • [#5427] ircp failed on bf533-stamp
  • [#5708] Kernel can not boot up when spimmc driver is interrupt drivern in PIO mode
  • [#5711] gfortran case default_format_1.exe fails on 09r1 kernel but pass on trunk head
  • [#5712] I2C client drivers using dev_pm_ops fail to receive suspend/resume callbacks
  • [#5715] libpcap fails to compile in trunk
  • [#5589] STLport build fails
  • [#5724] SPORT driver crash on reload
  • [#5449] bfin_sdh doesn't save and restore peripheral context upon resume
  • [#5580] GPIO pin not reserved for CTS function on SPORT-UART driver
  • [#5521] trunk head build fails at ipc/shm.c
  • [#5636] generic gpio works on bf533 in the opposite way
  • [#5637] Kernel crashed when arecord and aplay on bf537-stamp with SoC I2S audio
  • [#5647] SPI driver bus_unlock() does not schedule postponed SPI messages
  • [#5683] build nand fails for format error
  • [#5689] while two or multi spi devices use gpio cs, spi setup will fail
  • [#5558] bfin mac multi-cast sending fails to work
  • [#5816] PREEMPT_RT: cyclic test stalls in some test mode
  • [#5824] some kernel modules fail to link due to losing strcpy in trunk head
  • [#5707] error in user/procps/Makefile
  • [#5841] [ltp] ltp test case shmctl01/semctl01 can not execute
  • [#5605] Build bf537-stamp fail at bf5xx-i2s.c in latest trunk
  • [#5614] With latest toolchain in trunk, fail to build some apps and libs at fork
  • [#5625] Build microwin app fails in trunk with 4.3 toolchain
  • [#5626] Build lib mad fail at option "-fforce-mem" with gcc 4.3
  • [#5722] bfin_sport_spi broken by cs_gpio changes
  • [#5627] fail to control gpio used by led and button through /sys/class/gpio/
  • [#5927] PR bit other than RAF bit in EMAC OPMODE register should be set for promisuous mode in bfin_mac driver
  • [#5727] build e2fsprogs-1.41.12 fail sometimes because of compiling order
  • [#5631] Build lib confuse failed with gcc 4.3 toolchain
  • [#5759] fix build for pwlib
  • [#5651] Build lirc failed at missing files
  • [#5931] Trying to compile CAN4LINUX for BF537-STAMP board but compilation is failing
  • [#5656] Build iproute2 fails at trunk for dlfcn.h when built as FLAT
  • [#5743] sound/soc/blackfin/bf5xx-ad1938.c build fails after 2.6.32 upgrade
  • [#5801] No interrupt occurs when reconnect gadget device in OTG mode.
  • [#5657] [ltp] ltp test case mount03/umount03 fail with error of "No such device"
  • [#5808] mmc configuration error in make config
  • [#5804] bf531: ethernet not working when switching to 2009R1
  • [#5810] initial sp is given wrong value and INIT_TASK_DATA is not linked into data
  • [#6335] Build xip failed in fdpic format when xenomai is enabled
  • [#7224] undifined variable x25_address in ./user/net-tools/lib/x25_src.c
  • [#5598] bluez-utils has parallel build issues with parser.h
  • [#5668] Fail to build app bluez-utils
  • [#7251] Blackfin SPI driver doesn't handle repeated changes in CPOL, CPHA and LSBF correctly
  • [#5767] In 09r1.1 branch, all ltp test cases show stack overflow in bf561 SMP kernel
  • [#5684] touching keypad on bf548 will make system dead and restart
  • [#7287] Can not build usb.c with libaio
  • [#5687] SPI read/write be wrong after suspend to memory and resume
  • [#7315] [ltp] ltp test case getrusage04 from ltp-full-20120903 fails in trunk
  • [#7328] Fail to compile pthread_test after toolchain update
  • [#5876] Repeating rsh/rcp causes error "poll: protocol failure in circuit setup"
  • [#7329] Fail to compile netperf after toolchain update
  • [#7333] Test dll fails to run after toolchain update
  • [#5741] adau1371 and adau1761 fail to build after 2.6.32 upgrade
  • [#7337] [ltp] ltp test case mount02 fails in ltp-full-20120903
  • [#7338] [ltp] ltp test case mount03 fails in ltp-full-20120903
  • [#5821] Fail to build pngview on regression machines with suse 10.2
  • [#5900] hardware single stepping in userspace does not handle syscalls correctly
  • [#5659] [ltp] ltp test case eventfd01 fail
  • [#7339] [ltp] can not apply patch of lchown02 in ltp-full-20101031 to ltp-full-20120903
  • [#7343] [ltp] LTP test case chdir04 fails in ltp-full-20120903
  • [#7396] build netperf fails for undefined reference to `___CPU_ZERO'
  • [#7483] bfin_sport driver does not work well in TDM DMA mode
  • [#7506] Dropbear does not build
  • [#5757] drop USER_SQUASHFS_MKSQUASHFS7Z as squashfs 4.0 does not support 7z anymore
  • [#5758] fix build for libopenh323
  • [#5833] trap test running on the second core of bf561 has serveral fails
  • [#5755] romfs target fails for lib/pwlib
  • [#5760] fix asterisk build
  • [#5756] romfs target fails for lib/libopenh323
  • [#5877] SPI transmit cs_change flag not properly handled
  • [#5939] bfin-can fails to build after linux-2.6.33 upgrade
  • [#5879] GPIO controlled slave request may fail when bfin_spi_setup() gets executed twice
  • [#5774] [ltp]ltp test case will be killed by oom-killer on bf533-ezkit in 09r1 branch occasionally
  • [#5894] BF527 uImage Flashing issue(Copy to Flash... Flash not Erased)
  • [#5941] links fails in trunk due to using fork()
  • [#5942] build usb host fail when remove anomaly 456 for BF526-EZBRD
  • [#7250] On bfin ppi test, it fails to quit from slave when send "q" from master
  • [#7379] Fail to build alsa lib in latest trunk with upgraded toolchain
  • [#5792] enc28j60 spi net fails to ping with host on trunk head kernel
  • [#4436] BF527-EZKIT unable to receive large files over UART in DMA mode
  • [#4764] Kernel prints warning when booting from jffs2 rootfs in nor flash on bf548-ezkit
  • [#5903] Impossible to work properly with two or more SPI slave devices using spi_bfin5xx driver.
  • FAQ: [#6386] build iproute2 may fail at ifstat.c sometimes in latest trunk(2010)
  • FAQ: [#6331] There is error in adau1371 audio testing on bf527-ezkit(2010)
  • [#5933] BF561-EZKIT SMP kernel can not wake up from standby mode by uart interrupt
  • FAQ: [#6564] dmacopy test on bf561-ezkit failed at sram_alloc in L1(2011)
  • [#4713] dmacopy tries to test L2 on BF537
  • [#4997] ppitest fails for bfin_ppi driver on bf537
  • [#5940] lynx fails in trunk due to using fork()
  • [#4104] Format usbdisk failed with mke2fs in trunk
  • FAQ: [#6578] iccutils build fails at scalar.c(2011)
  • [#3883] ftp server crash after connetion or chdir with MidnightCommander4.6.1
  • [#4697] kernel crash on bf533-stamp/bf533-ezkit after config IP for ethernet port
  • [#4050] xip test case failed in BF548-EZKIT
  • [#3991] mmc_spi not working out of the box.
  • [#3996] dhcpcd not stable on BF548-EZKIT
  • [#5136] Linphone: Can't hear each other and "Data access misaligned address violation"
  • [#5214] trunk applications don't build with trunk toolchain due to missing fork()
  • [#4055] top (busybox) crashs
  • [#5162] Linphone: Data access misaligned address
  • [#4992] bfin_sdh fails to build for BF514/BF516
  • [#5570] reboot on bf527-ezkit with nand and ubifs enabled fails
  • [#4955] 548 SDH: netperf, iperf triggers libertas error
  • [#5522] Lib DirectFB-1.4.0 crashes when run DirectFB demo on SVN trunk
  • [#3882] copy file function cp, after few times consume all memory
  • [#4773] BF527 usb-ide hard disk error

[#4997] ppitest fails for bfin_ppi driver on bf537

[#4997] ppitest fails for bfin_ppi driver on bf537

Submitted By: Vivi Li

Open Date

2009-03-18 00:12:31     Close Date

2009-07-13 00:47:56

Priority:

Medium High     Assignee:

Michael Hennerich

Status:

Closed     Fixed In Release:

N/A

Found In Release:

N/A     Release:

Category:

Tests     Board:

N/A

Processor:

BF537     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Fixed

Uboot version or rev.:

    Toolchain version or rev.:

gcc4.1_2009-01-19

App binary format:

N/A     

Summary: ppitest fails for bfin_ppi driver on bf537

Details:

ppitest fails on bf537 for bfin_ppi driver. Nothing is received from slave side. Config file is attached.

Bellow is the log for master:

--

Linux version 2.6.28.7-ADI-2009R1-pre-svn6180 (test@uboot34-bf537stamp) (gcc version 4.1.2 (ADI svn)) #47 Wed Mar 18 12:22:58 CS9

console [early_BFuart0] enabled

early printk enabled on early_BFuart0

Warning: limiting memory to 56MB due to hardware anomaly 05000263

Board Memory: 64MB

Kernel Managed Memory: 64MB

Memory map:

  fixedcode = 0x00000400-0x00000490

  text      = 0x00001000-0x001039d0

  rodata    = 0x001039d0-0x00152dc4

  bss       = 0x00152dd0-0x00161794

  data      = 0x00161794-0x00172000

    stack   = 0x00170000-0x00172000

  init      = 0x00172000-0x0045b000

  available = 0x0045b000-0x037ff000

  DMA Zone  = 0x03f00000-0x04000000

Hardware Trace Active and Enabled

Boot Mode: 0

Reset caused by Software reset

Blackfin support (C) 2004-2009 Analog Devices, Inc.

Compiled for ADSP-BF537 Rev 0.2

Blackfin Linux support by   blackfin.uclinux.org/

Processor Speed: 500 MHz core clock and 100 MHz System Clock

NOMPU: setting up cplb tables

Instruction Cache Enabled for CPU0

Data Cache Enabled for CPU0 (write-back)

Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 14223

Kernel command line: root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart0,57600 console=ttyBF0,57600 ip=10.100.4.50f

Configuring Blackfin Priority Driven Interrupts

PID hash table entries: 256 (order: 8, 1024 bytes)

console handover: boot [early_BFuart0] -> real [ttyBF0]

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory available: 52300k/65536k RAM, (2980k init code, 1034k kernel code, 442k data, 1024k dma, 7756k reserved)

Calibrating delay loop... 997.37 BogoMIPS (lpj=1994752)

Security Framework initialized

Mount-cache hash table entries: 512

Blackfin Scratchpad data SRAM: 4 KB

Blackfin L1 Data A SRAM: 16 KB (15 KB free)

Blackfin L1 Data B SRAM: 16 KB (16 KB free)

Blackfin L1 Instruction SRAM: 48 KB (41 KB free)

PDA for CPU0 reserved at 00153e00

net_namespace: 288 bytes

NET: Registered protocol family 16

Blackfin GPIO Controller

Blackfin DMA Controller

stamp_init(): registering device resources

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables configured (established 2048 bind 2048)

TCP reno registered

NET: Registered protocol family 1

msgmni has been set to 102

io scheduler noop registered

io scheduler anticipatory registered (default)

io scheduler cfq registered

Serial: Blackfin serial driver

bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 18) is a BFIN-UART

brd: module loaded

bfin_mii_bus: probed

bfin_mac: attached PHY driver [SMSC LAN83C185] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=19)@sclk=100MHz)

bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1

bfin-spi bfin-spi.0: Blackfin on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@7

rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0

bfin-wdt: initialized: timeout=20 sec (nowayout=0)

TCP cubic registered

NET: Registered protocol family 17

rtc-bfin rtc-bfin: setting system clock to 1970-12-23 10:41:15 UTC (30796875)

IP-Config: Complete:

     device=eth0, addr=10.100.4.50, mask=255.255.255.0, gw=10.100.4.174,

     host=bf537-stamp, domain=, nis-domain=(none),

     bootserver=10.100.4.174, rootserver=10.100.4.174, rootpath=

Freeing unused kernel memory: 2980k freed

dma_alloc_init: dma_page @ 0x00457000 - 256 pages at 0x03f00000

                           _____________________________________

        a8888b.           / Welcome to the uClinux distribution \

       d888888b.         /       _     _                         \

       8P"YP"Y88        /       | |   |_|            __  __ (TM)  |

       8|o||o|88  _____/        | |    _ ____  _   _ \ \/ /       |

       8'    .88       \        | |   | |  _ \| | | | \  /        |

       8`._.' Y8.       \       | |__ | | | | | |_| | /  \        |

      d/      `8b.       \      \____||_|_| |_|\____|/_/\_\       |

     dP   .    Y8b.       \   For embedded processors including   |

    d8:'  "  `::88b        \    the Analog Devices Blackfin      /

   d8"         'Y88b        \___________________________________/

  :8P    '      :888

   8a.   :     _a88P         For further information, check out:

._/"Yaa_:   .| 88P|            -   blackfin.uclinux.org/

\    YP"    `| 8P  `.          -   docs.blackfin.uclinux.org/

/     \.___.d|    .'           -   www.uclinux.org/

`--..__)8888P`._.'  jgs/a:f    -   www.analog.com/blackfin

Have a lot of fun...

BusyBox v1.13.3 (2009-03-18 12:21:15 CST) built-in shell (msh)

Enter 'help' for a list of built-in commands.

root:/> PHY: 0:01 - Link is Up - 100/Full

root:/>

root:/>

root:/> PHY: 0:01 - Link is Down

root:/> ls /dev/

console             ppi0                ram14               ram9

cpu_dma_latency     ptmx                ram15               random

full                pts                 ram2                rtc0

kmsg                ram0                ram3                tty

log                 ram1                ram4                ttyBF0

mem                 ram10               ram5                urandom

network_latency     ram11               ram6                watchdog

network_throughput  ram12               ram7                zero

null                ram13               ram8

root:/> ppitest m

fd(3) = open(/dev/ppi)

Enter Line length (default = 16):

Enter number of lines (default = 8):

beMaster()

Setting up master...new gImageSize( 35CA004 ) = 0x100 (256)

device ioctl error: Invalid argument

Master set up complete...further input is transmited to slave

Enter fill pattern [CcQqRrTtVvHh?]:  c

fillBuffer(35CA004, 16, 8, 'c', 0x0)

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F   10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F   10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F   10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F   10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F   10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F   10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F   10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F   10

--

Bellow is the log for slave:

--

root:/> ls/dev/

console             ppi0                ram14               ram9

cpu_dma_latency     ptmx                ram15               random

full                pts                 ram2                rtc0

kmsg                ram0                ram3                tty

log                 ram1                ram4                ttyBF0

mem                 ram10               ram5                urandom

network_latency     ram11               ram6                watchdog

network_throughput  ram12               ram7                zero

null                ram13               ram8

root:/> ppitest s

fd(3) = open(/dev/ppi)

Enter Line length (default = 16):

Enter number of lines (default = 8):

beSlave()

new gImageSize( 35F0004 ) = 0x100 (256)

device ioctl error: Invalid argument

Setting up slave...to read 256 bytesSlave set up complete...following output is received from master...

--

Follow-ups

--- Michael Hennerich                                        2009-03-18 05:05:04

Looks like you don't have a PPI clock connected.

Can you place a wire on the BF537-EZKIT from U4 (output of the 12MHz

oscillator) to PPI CLK?

-Michael

--- Vivi Li                                                  2009-03-18 07:01:31

We now connect pin 27 of PPI port on two 537 boards. Pin 27 of PPI should be

connected with PPI_CLK of U35.

What's the difference if we connect it to U4?

--- Michael Hennerich                                        2009-03-18 13:04:00

PPI CLK is an input on both boards/Blackfin Processors.

You need to connect PPI CLK also with a clock source.

U4 is a 12.288 MHz oscillator.

-Michael

--- Vivi Li                                                  2009-03-30 02:52:46

As I can not find U4 in bf537-stamp, so I use a bf537-ezkit board connecting to

a bf537-stamp, and in that ezkit board I connect R54(MCLK output) to pin 27 of

PPI.

PPI test still fails with the same error info.

--- Michael Hennerich                                        2009-04-16 04:27:19

>device ioctl error: Invalid argument

Sorry I just noticed that I forgot to commit necessary changes for the ppitest

application.

I just corrected my failure.

Can you try again?

-Michael

--- raghu mulagada                                           2009-04-27 00:26:57

hi Micheal,

i'am also facing the same problem

can you tell me what changes are to be made

and where to make them

thanks

raghu

--- Vivi Li                                                  2009-06-25 07:03:51

I found that the result of master and slave side is not exactly the same. I

think character 10 is missing in slave side.

master side:

--

root:/> ppitest m

fd(3) = open(/dev/ppi)

Enter Line length (default = 16):

Enter number of lines (default = 8):

beMaster()

Setting up master...new gImageSize( 34B8004 ) = 0x100 (256)

Master set up complete...further input is transmited to slave

Enter fill pattern [CcQqRrTtVvHh?]:  c

fillBuffer(34B8004, 16, 8, 'c', 0x0)PPI Error: PPI Status = 0x2000

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F 

10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F 

10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F 

10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F 

10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F 

10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F 

10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F 

10

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F 

10

--

slave side:

--

root:/> ppitest s

fd(3) = open(/dev/ppi)

Enter Line length (default = 16):

Enter number of lines (default = 8):

beSlave()

new gImageSize( 34B1004 ) = 0x100 (256)

Setting up slave...to read 256 bytesSlave set up complete...following output is

received from master...

PPI Error: PPI Status = 0x200

   1    2    3    4    5    6    7    8    9    A    B    C    D    E    F  

1

   2    3    4    5    6    7    8    9    A    B    C    D    E    F    1  

2

   3    4    5    6    7    8    9    A    B    C    D    E    F    1    2  

3

   4    5    6    7    8    9    A    B    C    D    E    F    1    2    3  

4

   5    6    7    8    9    A    B    C    D    E    F    1    2    3    4  

5

   6    7    8    9    A    B    C    D    E    F    1    2    3    4    5  

6

   7    8    9    A    B    C    D    E    F    1    2    3    4    5    6  

7

   8    9    A    B    C    D    E    F    F   10    F   10    F   10    F 

10

--

--- Michael Hennerich                                        2009-07-03 08:20:41

Good catch.

During my initial testing I used a slightly modified ppitest utility.

Which sets ioctl CMD_PPI_FS1_EOL_BLANKING to something > 0.

This is actually required in order to avoid line track errors.

Fixed on 2009R1 and trunk.

In case you still see PPI Error messages print.

Flip the priority of IRQ_ERROR and IRQ_PPI. 

(8) IRQ_ERROR: CAN MAC SPORT0 SPORT1 SPI UART0 UART1

(8) IRQ_RTC                                        

(7) IRQ_PPI                                        

-Michael

--- Vivi Li                                                  2009-07-07 06:12:34

The result is much better now.

But when I test it with fill pattern Q/q, it shows with following results.

At master side:

--

root:/> ppitest m

fd(3) = open(/dev/ppi)

Enter Line length (default = 16):

Enter number of lines (default = 8):

beMaster()

Setting up master...new gImageSize( 811004 ) = 0x100 (256)

Master set up complete...further input is transmited to slave

Enter fill pattern [CcQqRrTtVvHh?]:  q

fillBuffeP(811004, 16, 8, 'q', 0xDEAD)PI Error: PPI Status = 0x2000

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

Done

root:/>

--

At slave side:

--

root:/> ppitest s

fd(3) = open(/dev/ppi)

Enter Line length (default = 16):

Enter number of lines (default = 8):

beSlave()

new gImageSize( BCB004 ) = 0x100 (256)

Setting up slave...to read 256 bytesSlave set up complete...following output is

received from master...

E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D

E2D

E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D

E2D

E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D

E2D

E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D

E2D

E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D

E2D

E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D

E2D

E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D

E2D

E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D  E2D

E2D

PPI Error: PPI Status = 0x200

F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38

F38

F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38

F38

F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38

F38

F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38

F38

F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38

F38

F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38

F38

F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38

F38

F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38  F38

F38

--

Is it correct that F38 shows up at slave side?

--- Michael Hennerich                                        2009-07-07 11:20:45

Q stands for Quit and will send 0xEAD to the Slave.

In case the Slave receives this sequence it will quit.

Exactly this happens in my test setup.

So I bet your board wiring flipped some upper PPI Data Strobes.

Not a software bug.

See below -

On the MASTER board:

root:/> ppitest m

fd(3) = open(/dev/ppi)

Enter Line length (default = 16):

Enter number of lines (default = 8):

beMaster()

Setting up master...new gImageSize( 336004 ) = 0x100 (256)

Master set up complete...further input is transmited to slave

Enter fill pattern [CcQqRrTtVvHh?]:  Q

fillBuffPr(3PI Error: PPI Status = 0x2000

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD  EAD

EAD

Done

root:/>

On the SALVE board:

root:/> ppitest s

fd(3) = open(/dev/ppi)

Enter Line length (default = 16):

Enter number of lines (default = 8):

beSlave()

new gImageSize( 3786004 ) = 0x100 (256)

Setting up slave...to read 256 bytesSlave set up complete...following output is

received from master...

root:/>

--- Vivi Li                                                  2009-07-08 04:26:41

I need to set SW4.3 OFF, so PG7 can work.

It works alright between bf537-ezkit and bf537-stamp now.

--- Vivi Li                                                  2009-07-13 00:47:56

Close this bug.

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

File Name     File Type     File Size     Posted By

config.kernel    application/octet-stream    26328    Vivi Li

config.user    application/octet-stream    45592    Vivi Li

Attachments:
5736.config.user.zip
3073.config.kernel.zip
  • Share
  • History
  • More
  • Cancel
Related
Recommended
 
Social
Quick Links
  • About ADI
  • Partners
  • Analog Dialogue
  • Careers
  • Contact us
  • Investor Relations
  • News Room
  • Quality & Reliability
  • Sales & Distribution
  • Analog Garage
Languages
  • English
  • 简体中文
  • 日本語
  • Руccкий
Newsletters

Interested in the latest news and articles about ADI products, design tools, training and events? Choose from one of our 12 newsletters that match your product area of interest, delivered monthly or quarterly to your inbox.

Sign Up
Switch to mobile view
Analog Logo
© 1995 - 2023 Analog Devices, Inc. All Rights Reserved 沪ICP备09046653号-1
  • ©
  • 1995 - 2023 Analog Devices, Inc. All Rights Reserved
  • 沪ICP备09046653号-1
  • Sitemap
  • Privacy & Security
  • Privacy Settings
  • Terms of use
EngineerZone Uses cookies to ensure you get the best experience in our community. For more information on cookies, please read our Privacy & Security Statement.