2008-02-12 07:44:43 Cannot open device ppi in bf561-ezkit..
soni shetty (INDIA)
Message: 50933 hi
After booting the image into board(bf561-ezkit),i can see the device "ppi" registerd by using the command "cat /proc/devices" and also interrupts.
root:~> cat proc/devices
Character devices:
1 mem
5 /dev/tty
5 /dev/console
5 /dev/ptmx
10 misc
29 fb
81 video4linux
128 ptm
136 pts
180 usb
189 usb_device
204 ttyBF
243 PPI0
root:~> cat proc/interrupts
6: 95535 BFIN Timer Tick
23: 0 BF561_PPI_DMA
35: 589 BFIN_UART_RX
36: 5632 BFIN_UART_TX
62: 0 Core B - DMA Destination
Err: 0
root:/dev> ls
can0 hdb11 mtd0 pf9 ram3 sg0 timer3
console hdb12 mtd1 port ram4 sg1 timer4
coreb hdb13 mtd2 ppi0 ram5 sg10 timer5
dpmc hdb14 mtd3 ppp ram6 sg11 timer6
dsp hdb2 mtdblock0 pppox0 ram7 sg12 timer7
fb0 hdb3 mtdblock1 pppox1 ram8 sg13 timer8
full hdb4 mtdblock2 pppox2 ram9 sg14 timer9
hda hdb5 mtdblock3 pppox3 random sg2 tty
hda1 hdb6 nfs psaux root sg3 tty0
hda10 hdb7 null ptmx rtc sg4 ttyBF0
hda11 hdb8 pf0 pts sda sg5 ttyS0
hda12 hdb9 pf1 pts0 sda1 sg6 ttyUSB0
hda13 i2c-0 pf10 pts1 sda10 sg7 ttyp0
hda14 input pf11 ptyp0 sda11 sg8 ttyp1
hda2 ircomm0 pf12 ptyp1 sda12 sg9 urandom
hda3 ircomm1 pf13 ptyp2 sda13 snd usb
hda4 kmem pf14 ram0 sda14 spi vout0
hda5 kmsg pf15 ram1 sda2 sport0 watchdog
hda6 log pf2 ram10 sda3 sport1 zero
hda7 mem pf3 ram11 sda4 time
hda8 mixer pf4 ram12 sda5 timer0
hda9 mmc pf5 ram13 sda6 timer1
hdb mmc1 pf6 ram14 sda7 timer10
hdb1 mmc2 pf7 ram15 sda8 timer11
hdb10 mmc3 pf8 ram2 sda9 timer2
But when iam trying to open the device through my application,it returns -1.Implicitly the device is not opened.Though i have given a printf statement in the first line of device-open function,i couldnt get any prints when iam executing.I dont know where the problem is...can anyone help me on this issue?
Note:
uClinux-dist :: 2007R1-RC3
Toolchain :: 07r1-rc9
thanks in advance
QuoteReplyEditDelete
2008-02-12 09:59:11 Re: Cannot open device ppi in bf561-ezkit..
Mike Frysinger (UNITED STATES)
Message: 50937 the existence of the device node is not indicative of anything
the PPI driver is not ported to the BF561 ... it only works on parts that have 1 PPI device
QuoteReplyEditDelete
2008-02-13 04:13:20 Re: Cannot open device ppi in bf561-ezkit..
soni shetty (INDIA)
Message: 50975
When i went through bfin-forum,i found out the code and associated
ppi driver files(i.e.bfin_capture.c, bfin_ppiin.c and ppiout.c)
given by Mr.zhe chen lee in
for ppi.But when i loaded the image after inclusions of
the corresponding exe, it returns -1,means device not opened..
Below the details of devices and interrupts registered..
root:~> cat proc/devices
Character devices:
1 mem
5 /dev/tty
5 /dev/console
5 /dev/ptmx
10 misc
29 fb
81 video4linux
128 ptm
136 pts
180 usb
189 usb_device
204 ttyBF
243 PPI0
root:~> cat proc/interrupts
6: 95535 BFIN Timer Tick
23: 0 BF561_PPI_DMA
35: 589 BFIN_UART_RX
36: 5632 BFIN_UART_TX
62: 0 Core B - DMA Destination
Err: 0
root:/dev> ls
can0 hdb11 mtd0 pf9 ram3 sg0 timer3
console hdb12 mtd1 port ram4 sg1 timer4
coreb hdb13 mtd2 ppi0 ram5 sg10 timer5
dpmc hdb14 mtd3 ppp ram6 sg11 timer6
dsp hdb2 mtdblock0 pppox0 ram7 sg12 timer7
fb0 hdb3 mtdblock1 pppox1 ram8 sg13 timer8
full hdb4 mtdblock2 pppox2 ram9 sg14 timer9
hda hdb5 mtdblock3 pppox3 random sg2 tty
hda1 hdb6 nfs psaux root sg3 tty0
hda10 hdb7 null ptmx rtc sg4 ttyBF0
hda11 hdb8 pf0 pts sda sg5 ttyS0
hda12 hdb9 pf1 pts0 sda1 sg6 ttyUSB0
hda13 i2c-0 pf10 pts1 sda10 sg7 ttyp0
hda14 input pf11 ptyp0 sda11 sg8 ttyp1
hda2 ircomm0 pf12 ptyp1 sda12 sg9 urandom
hda3 ircomm1 pf13 ptyp2 sda13 snd usb
hda4 kmem pf14 ram0 sda14 spi vout0
hda5 kmsg pf15 ram1 sda2 sport0 watchdog
hda6 log pf2 ram10 sda3 sport1 zero
hda7 mem pf3 ram11 sda4 time
hda8 mixer pf4 ram12 sda5 timer0
hda9 mmc pf5 ram13 sda6 timer1
hdb mmc1 pf6 ram14 sda7 timer10
hdb1 mmc2 pf7 ram15 sda8 timer11
hdb10 mmc3 pf8 ram2 sda9 timer2
thanks
QuoteReplyEditDelete
2008-02-13 15:36:02 Re: Cannot open device ppi in bf561-ezkit..
Mike Frysinger (UNITED STATES)
Message: 51002 you need to verify the device node that exists in /dev actually corresponds to the major/minor the device driver is listening on