[#5302] ad7877 touchscreen fails to be probed on bf527 ezkit
Submitted By: Mingquan Pan
Open Date
2009-07-01 02:22:14 Close Date
2009-07-03 06:13:30
Priority:
Medium High Assignee:
Graf Yang
Michael Hennerich
Status:
Closed Fixed In Release:
N/A
Found In Release:
N/A Release:
Category:
N/A Board:
N/A
Processor:
BF527 Silicon Revision:
Is this bug repeatable?:
Yes Resolution:
Rejected
Uboot version or rev.:
Toolchain version or rev.:
09r1-rc7
App binary format:
N/A
Summary: ad7877 touchscreen fails to be probed on bf527 ezkit
Details:
ad7877 touchscreen fails to be probed on bf527 ezkit.
bfin> bootm
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-2.6.28.10-ADI-2009R1-svn68
Created: 2009-07-01 4:14:48 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 4581568 Bytes = 4.4 MB
Load Address: 00001000
Entry Point: 001e16cc
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting Kernel at = 001e16cc
Linux version 2.6.28.10-ADI-2009R1-svn6870 (test@linux) (gcc version 4.1.2 (ADI svn)) #8 Wed Jul 1 12:14:35 GMT-8 2009
console [early_BFuart0] enabled
early printk enabled on early_BFuart0
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
fixedcode = 0x00000400-0x00000490
text = 0x00001000-0x00141830
rodata = 0x00141830-0x001a7988
bss = 0x001a8000-0x001bca10
data = 0x001bca10-0x001d4000
stack = 0x001d2000-0x001d4000
init = 0x001d4000-0x008b4000
available = 0x008b4000-0x03eff000
DMA Zone = 0x03f00000-0x04000000
Hardware Trace Active and Enabled
Boot Mode: 3
Blackfin support (C) 2004-2009 Analog Devices, Inc.
Compiled for ADSP-BF527 Rev 0.0
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 525 MHz core clock and 131 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: 16001
Kernel command line: root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x25
console [tty0] enabled
Linux version 2.6.28.10-ADI-2009R1-svn6870 (test@linux) (gcc version 4.1.2 (ADI svn)) #8 Wed Jul 1 12:14:35 GMT-8 2009
console [early_BFuart0] enabled
early printk enabled on early_BFuart0
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
fixedcode = 0x00000400-0x00000490
text = 0x00001000-0x00141830
rodata = 0x00141830-0x001a7988
bss = 0x001a8000-0x001bca10
data = 0x001bca10-0x001d4000
stack = 0x001d2000-0x001d4000
init = 0x001d4000-0x008b4000
available = 0x008b4000-0x03eff000
DMA Zone = 0x03f00000-0x04000000
Hardware Trace Active and Enabled
Boot Mode: 3
Blackfin support (C) 2004-2009 Analog Devices, Inc.
Compiled for ADSP-BF527 Rev 0.0
Blackfin Linux support by http://blackfin.uclinux.org/
Processor Speed: 525 MHz core clock and 131 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: 16001
Kernel command line: root=/dev/mtdblock0 rw clkin_hz=25000000 earlyprintk=serial,uart1,57600 console=tty0 console=ttyBF0,57600
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x25
console [tty0] enabled
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: 55024k/65536k RAM, (7040k init code, 1282k kernel code, 586k data, 1024k dma, 576k reserved)
Calibrating delay loop... 1046.52 BogoMIPS (lpj=2093056)
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 (42 KB free)
net_namespace: 288 bytes
NET: Registered protocol family 16
Blackfin DMA Controller
ezkit_init(): registering device resources
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, host, debug=0
musb_hdrc: USB Host mode controller at ffc03800 using DMA, IRQ 59
musb_hdrc musb_hdrc.0: MUSB HDRC host driver
musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
dma_alloc_init: dma_page @ 0x03e86000 - 256 pages at 0x03f00000
hub 1-0:1.0: 1 port detected
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 107
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
bfin-t350mcqb: 320x240 24-bit RGB FrameBuffer initializing...
Console: switching to colour frame buffer device 40x30
bfin-otp: initialized
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc02000 (irq = 31) is a BFIN-UART
brd: module loaded
bfin_mii_bus: probed
bfin_mac: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1, mdc_clk=2500000Hz(mdc_div=25)@sclk=131MHz)
bfin_mac bfin_mac.0: Blackfin on-chip Ethernet MAC driver, Version 1.1
Driver 'sd' needs updating - please use bus_type methods
m25p80 spi0.1: m25p16 (2048 Kbytes)
Creating 2 MTD partitions on "m25p80":
0x00000000-0x00040000 : "bootloader(spi)"
0x00040000-0x00200000 : "linux kernel(spi)"
bfin-spi bfin-spi.0: Blackfin on-chip SPI Controller Driver, Version 1.0, regs_base@ffc00500, dma channel@7
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ad7877 spi0.2: spi0.2: Failed to probe AD7877 Touchscreen
rtc-bfin rtc-bfin: rtc core: registered rtc-bfin as rtc0
bfin-wdt: initialized: timeout=20 sec (nowayout=0)
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
rtc-bfin rtc-bfin: setting system clock to 1970-01-13 07:02:39 UTC (1062159)
Freeing unused kernel memory: 7040k freed
_____________________________________
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| - http://blackfin.uclinux.org/
\ YP" `| 8P `. - http://docs.blackfin.uclinux.org/
/ \.___.d| .' - http://www.uclinux.org/
`--..__)8888P`._.' jgs/a:f - https://www.analog.com/blackfin
Have a lot of fun...
BusyBox v1.13.4 (2009-06-30 18:33:50 GMT-8) built-in shell (msh)
Enter 'help' for a list of built-in commands.
I have moved the chip select to 2 when connected to bf527-ezkit. The remain selection is the same as it is connected to bf537-stamp, in which case it can works ok.
It could be some jumpers on bf527 ezkit are not ready for touchscreen, but don't know which.
I have enabled JP3(STAMP enable),SW8 X.X.on.off,sw19 on.off.on.off.
Follow-ups
--- Michael Hennerich 2009-07-01 03:45:48
The BF527-EZKIT doesn't feature an onboard AD7877 touch screen digitizer.
We already test the AD7877 driver on the BF537-STAMP and BF548-EZKIT.
Do we really need to test it on the BF537-EZKIT as well?
If yes - try to also set:
SW11-2 OFF
SW18-1 OFF
And try again.
-Michael
--- Mingquan Pan 2009-07-01 06:51:37
I try with sw11.2 off and sw18.1 off on bf527 ezkit, still fails to probe the
ad7877.
?
--- Sonic Zhang 2009-07-02 04:45:21
This test case was passed in 2008R1.5 on bf527-ezkit.
--- Michael Hennerich 2009-07-02 06:32:23
If you can tell me that the same board with the 2008R1.5 works - I will take a
closer look.
I don't have an external AD7877 board I could test with.
And I know we had similar problems with the SPI MMC card on the BF527-EZKIT,
due to some pull down/up resistors attached to the SPI strobes connected to the
SPI-Flash on the BF527-EZKIT.
-Michael
--- Sonic Zhang 2009-07-02 22:03:54
OK. I will ask Graf to take a look in Shanghai as well.
--- Graf Yang 2009-07-03 05:08:25
The chip selector jumper on AD7877 board need not change on BF527-ezkit, it is
same as settings on BF537-stamp.
Updated ad7877 wiki,
https://docs.blackfin.uclinux.org/doku.php?id=linux-kernel:drivers:ad7877
--- Mingquan Pan 2009-07-03 06:13:30
Yeah, it can detect the ad7877 on bf527 ezkit board now after setting all these
jumpers. Close.
Files
Changes
Commits
Dependencies
Duplicates
Associations
Tags
File Name File Type File Size Posted By
config.touchscreen application/octet-stream 37859 Mingquan Pan