2008-08-26 22:14:47 touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61141
I try to use the touchscreen with pictureflow (and QT library).
In the BF548 the LCD and touchscreen is already on the board, need i follow this documentation :http://docs.blackfin.uclinux.org/doku.php?id=touchscreen#build_kernel1 ?
I have try to build the kernel with TSlib but i need to use FDPIC binary format and i have always built with FAT format.
when i compil the kernel I have this error, sorry it's in french that said
it's not possible to do a link between an executable fdpic and an object file no fdpicErronnée value: failure of fusion of the target specific data of the inffast.o file
Compress.o: in the function "compress2":
/home/dam/blackfin-sources/uClinux/lib/zlib / compress.c:46: WARNING: relocations between various segments are not supported
final edition of link in failure: section can't be shown in a form on the exit
Collect2: ld returned 1 code of execution order
make[5]: entrant dans le répertoire « /home/dam/blackfin-sources/uClinux/lib/tslib-1.0/build/src »
make[6]: entrant dans le répertoire « /home/dam/blackfin-sources/uClinux/lib/tslib-1.0/build/src »
test -z "/usr/lib" || mkdir -p -- "/home/dam/blackfin-sources/uClinux/staging/usr/lib"
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: adler32.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier adler32.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: compress.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier compress.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: crc32.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier crc32.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: gzio.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier gzio.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: uncompr.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier uncompr.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: deflate.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier deflate.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: trees.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier trees.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: zutil.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier zutil.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: inflate.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier inflate.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: infback.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier infback.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: inftrees.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier inftrees.o
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: inffast.o : impossible de lier un fichier objet non-fdpic dans un exécutable fdpic
valeur erronnée: échec de fusion des données spécifiques cibles du fichier inffast.o
compress.o: dans la fonction « compress2 »:
/home/dam/blackfin-sources/uClinux/lib/zlib/compress.c:46: AVERTISSEMENT: les relocalisations entre différents segments ne sont pas supportées
/home/dam/blackfin-sources/build/bfin-linux-uclibc/lib/gcc/bfin-linux-uclibc/4.1.2/../../../../bfin-linux-uclibc/bin/ld: édition de lien finale en échec: Section non-représentable sur la sortie
collect2: ld a retourné 1 code d'état d'exécution
make[3]: *** [libz.so.1.2.3] Erreur 1
make[3]: quittant le répertoire « /home/dam/blackfin-sources/uClinux/lib/zlib »
make[2]: *** [zlib] Erreur 2
make[2]: *** Attente des tâches non terminées....
QuoteReplyEditDelete
2008-08-27 01:16:09 Re: touchscreen BF548
Mike Frysinger (UNITED STATES)
Message: 61143
please read the documentation ... you cannot mix FDPIC and FLAT format ... whenever you change file formats, you need to clean the build by doing `make clean`
QuoteReplyEditDelete
2008-08-27 12:18:47 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61180
All the software part looks good but when i execute the test, the touchscreen detect nothing and the calibrate don't working also.
I don't know where is the error.
SW5 is all off, SW4 : 1-2-3 on and 4 off
during the boot :
ad7877 spi0.2: touchscreen, irq 258
input: AD7877 Touchscreen as /class/input/input1
I have :
root:/> cat /sys/class/input/input1/name
AD7877 Touchscreen
root:/> ls -al /dev/input/
drw-r--r-- 2 root root 0 Jan 1 06:59 .
drwxr-xr-x 5 root root 0 Jan 1 06:59 ..
crw-rw-r-- 1 root root 13, 64 Jan 1 06:59 event0
crw-rw-r-- 1 root root 13, 65 Jan 1 06:59 event1
crw-rw-r-- 1 root root 13, 128 Jan 1 06:59 ts0
root:/> cat /proc/interrupts
6: 47787 BFIN Timer Tick
9: 0 PPI ERROR
10: 0 SPORT err
16: 0 SPORT RX Data
17: 0 SPORT TX Data
48: 0 BFIN_UART_RX
49: 99 BFIN_UART_TX
53: 0 i2c-bfin-twi
68: 3 pata-bf54x
74: 0 BF5XX NFC driver
76: 0 bf54x-keys
82: 1 musb_hdrc.0
85: 0 musb_hdrc.0
175: 0 smsc911x
258: 0 ad7877
Err: 0
root:/> ts_calibrate
xres = 480, yres = 272
signal 2 caught
root:/> event_test /dev/input/event1
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "AD7877 Touchscreen"
Supported events:
Event type 0 (Reset)
Event code 0 (Reset)
Event code 3 (Absolute)
Event type 3 (Absolute)
Event code 0 (X)
Value 0
Min 0
Max 4095
Event code 1 (Y)
Value 0
Min 0
Max 4095
Event code 24 (Pressure)
Value 0
Min 0
Max 1000
Testing ... (interrupt to exit)
QuoteReplyEditDelete
2008-08-27 12:26:43 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61181
if you have an idea about my problem, that could help me.
I don't know from where the problem come (and where i must search)
QuoteReplyEditDelete
2008-08-27 14:05:07 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61184
I have this in the file
arch/blackfin/mach-bf548/boards/ezkit.c :
#if defined(CONFIG_TOUCHSCREEN_AD7877) || defined(CONFIG_TOUCHSCREEN_AD7877_MODULE)
static struct bfin5xx_spi_chip spi_ad7877_chip_info = {
.cs_change_per_word = 0,
.enable_dma = 0,
.bits_per_word = 16,
};
static const struct ad7877_platform_data bfin_ad7877_ts_info = {
.model = 7877,
.vref_delay_usecs = 50, /* internal, no capacitor */
.x_plate_ohms = 419,
.y_plate_ohms = 486,
.pressure_max = 1000,
.pressure_min = 0,
.stopacq_polarity = 1,
.first_conversion_delay = 3,
.acquisition_time = 1,
.averaging = 1,
.pen_down_acc_interval = 1,
};
#endif
#if defined(CONFIG_TOUCHSCREEN_AD7877) || defined(CONFIG_TOUCHSCREEN_AD7877_MODULE)
{
.modalias = "ad7877",
.platform_data = &bfin_ad7877_ts_info,
.irq = IRQ_PJ11,
.max_speed_hz = 12500000, /* max spi clock (SCK) speed in HZ */
.bus_num = 0,
.chip_select = 2,
.controller_data = &spi_ad7877_chip_info,
},
#endif
arch/blackfin/mach-bf537/boards/stamp.c
#if defined(CONFIG_TOUCHSCREEN_AD7877) || defined(CONFIG_TOUCHSCREEN_AD7877_MODULE)
{
.modalias = "ad7877",
.platform_data = &bfin_ad7877_ts_info,
.irq = IRQ_PF6,
.max_speed_hz = 12500000, /* max spi clock (SCK) speed in HZ */
.bus_num = 0,
.chip_select = 1,
.controller_data = &spi_ad7877_chip_info,
},
#endif
I need to change the chip select to 7? (http://docs.blackfin.uclinux.org/doku.php?id=touchscreen#build_kernel1) To what that is use?
I need to have :
CS: SPI-CS7
DAV: GPIO PF6
ENIRQ: Unused
where can I found that?
Thanks
QuoteReplyEditDelete
2008-08-27 16:11:09 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61189
I think that the problem is the configuration of the SPI in the kernel in the Switch of the board or in the file stamp.c
I have
SW14 all on
SW5 all off
i haven't changed the file stamp.c
and all looks ok for the kernel, all the application run well exept that the touchscreen do nothing
QuoteReplyEditDelete
2008-08-27 16:29:46 Re: touchscreen BF548
Mike Frysinger (UNITED STATES)
Message: 61198
there is no BF548-STAMP, thus there is no stamp.c file for the BF548
QuoteReplyEditDelete
2008-08-27 16:34:08 Re: touchscreen BF548
Mike Frysinger (UNITED STATES)
Message: 61199
SW4/SW5 is not for the touchscreen, so those settings do not matter. review the board documentation:
QuoteReplyEditDelete
2008-08-27 17:36:01 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61203
thanks,
i have try all that's it's writting in this documentation without any problem:
http://docs.blackfin.uclinux.org/doku.php?id=touchscreen
http://docs.blackfin.uclinux.org/doku.php?id=ad7877_touchscreen_input_device_driver&s[]=tslib
according this document that should run.
all working exepte that the programs don't receive information from the touchscreen (i have chec with a scop, it send a signal when i tuch it)
have you information or documentation about the touchscreen that help me to find the problem.
please
QuoteReplyEditDelete
2008-08-28 03:43:53 Re: touchscreen BF548
Michael Hennerich (GERMANY)
Message: 61228
Can you do touch the screen and then do a cat /proc/interrupts
Are you getting interrupts?
I bet not -
This is where you should start looking at -
-Michael
root:~> modprobe ad7877
ad7877 spi0.2: touchscreen, irq 258
input: AD7877 Touchscreen as /class/input/input0
root:~> cat /proc/interrupts
6: 7584 BFIN Timer Tick
9: 0 PPI ERROR
10: 0 SPORT err
16: 0 SPORT RX Data
17: 0 SPORT TX Data
48: 55 BFIN_UART_RX
49: 1942 BFIN_UART_TX
53: 0 i2c-bfin-twi
68: 1312 pata-bf54x
74: 0 BF5XX NFC driver
82: 1 musb_hdrc.0
175: 0 smsc911x
258: 36 ad7877
Err: 0
root:~> modprobe evdev
root:~> event_test /dev/input/event0
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "AD7877 Touchscreen"
Supported events:
Event type 0 (Reset)
Event code 0 (Reset)
Event code 3 (Absolute)
Event type 3 (Absolute)
Event code 0 (X)
Value 3315
Min 0
Max 4095
Event code 1 (Y)
Value 1736
Min 0
Max 4095
Event code 24 (Pressure)
Value 0
Min 0
Max 1000
Testing ... (interrupt to exit)
Event: time 56.841325, type 3 (Absolute), code 0 (X), value 2287
Event: time 56.841332, type 3 (Absolute), code 1 (Y), value 2094
Event: time 56.841335, type 3 (Absolute), code 24 (Pressure), value 263
Event: time 56.841338, type 0 (Reset), code 0 (Reset), value 0
Event: time 56.884463, type 3 (Absolute), code 0 (X), value 2283
Event: time 56.884470, type 3 (Absolute), code 1 (Y), value 2084
Event: time 56.884473, type 3 (Absolute), code 24 (Pressure), value 248
Event: time 56.884475, type 0 (Reset), code 0 (Reset), value 0
Event: time 56.927598, type 3 (Absolute), code 0 (X), value 2319
Event: time 56.927604, type 3 (Absolute), code 1 (Y), value 2197
Event: time 56.927607, type 3 (Absolute), code 24 (Pressure), value 254
Event: time 56.927609, type 0 (Reset), code 0 (Reset), value 0
Event: time 56.970728, type 3 (Absolute), code 0 (X), value 2326
Event: time 56.970734, type 3 (Absolute), code 1 (Y), value 2215
Event: time 56.970736, type 3 (Absolute), code 24 (Pressure), value 256
Event: time 56.970738, type 0 (Reset), code 0 (Reset), value 0
Event: time 57.013865, type 3 (Absolute), code 0 (X), value 2327
Event: time 57.013871, type 3 (Absolute), code 1 (Y), value 2211
Event: time 57.013874, type 3 (Absolute), code 24 (Pressure), value 269
Event: time 57.013876, type 0 (Reset), code 0 (Reset), value 0
Event: time 57.057001, type 3 (Absolute), code 1 (Y), value 2198
Event: time 57.057007, type 3 (Absolute), code 24 (Pressure), value 432
Event: time 57.057010, type 0 (Reset), code 0 (Reset), value 0
Event: time 57.105194, type 3 (Absolute), code 24 (Pressure), value 0
Event: time 57.105201, type 0 (Reset), code 0 (Reset), value 0
Event: time 57.240557, type 3 (Absolute), code 0 (X), value 1338
Event: time 57.240564, type 3 (Absolute), code 1 (Y), value 2863
Event: time 57.240567, type 3 (Absolute), code 24 (Pressure), value 252
Event: time 57.240570, type 0 (Reset), code 0 (Reset), value 0
Event: time 57.283689, type 3 (Absolute), code 0 (X), value 1329
Event: time 57.283695, type 3 (Absolute), code 1 (Y), value 2866
Event: time 57.283697, type 3 (Absolute), code 24 (Pressure), value 248
Event: time 57.283700, type 0 (Reset), code 0 (Reset), value 0
Event: time 57.326831, type 3 (Absolute), code 0 (X), value 1318
Event: time 57.326837, type 3 (Absolute), code 1 (Y), value 2903
Event: time 57.326839, type 3 (Absolute), code 24 (Pressure), value 250
Event: time 57.326842, type 0 (Reset), code 0 (Reset), value 0
Event: time 57.369960, type 3 (Absolute), code 0 (X), value 1320
Event: time 57.369966, type 3 (Absolute), code 1 (Y), value 2896
Event: time 57.369969, type 3 (Absolute), code 24 (Pressure), value 251
Event: time 57.369971, type 0 (Reset), code 0 (Reset), value 0
Event: time 57.413095, type 3 (Absolute), code 0 (X), value 1321
Event: time 57.413101, type 3 (Absolute), code 1 (Y), value 2873
Event: time 57.413103, type 3 (Absolute), code 24 (Pressure), value 356
Event: time 57.413106, type 0 (Reset), code 0 (Reset), value 0
Event: time 57.505194, type 3 (Absolute), code 24 (Pressure), value 0
Event: time 57.505200, type 0 (Reset), code 0 (Reset), value 0
QuoteReplyEditDelete
2008-08-28 09:21:51 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61254
Thanks to your help
I think that looks well :
root:/> cat /proc/interrupts | grep ad7877
258: 0 ad7877
root:/> cat /sys/class/input/input1/name
AD7877 Touchscreen
root:/> event_test /dev/input/event1
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "AD7877 Touchscreen"
Supported events:
Event type 0 (Reset)
Event code 0 (Reset)
Event code 3 (Absolute)
Event type 3 (Absolute)
Event code 0 (X)
Value 0
Min 0
Max 4095
Event code 1 (Y)
Value 0
Min 0
Max 4095
Event code 24 (Pressure)
Value 0
Min 0
Max 1000
Testing ... (interrupt to exit)
This ezkit.c
" .chip_select = 2," what is this chip select, it correspond to what?
there is an error in this file?
#if defined(CONFIG_TOUCHSCREEN_AD7877) || defined(CONFIG_TOUCHSCREEN_AD7877_MODULE)
static struct bfin5xx_spi_chip spi_ad7877_chip_info = {
.cs_change_per_word = 0,
.enable_dma = 0,
.bits_per_word = 16,
};
static const struct ad7877_platform_data bfin_ad7877_ts_info = {
.model = 7877,
.vref_delay_usecs = 50, /* internal, no capacitor */
.x_plate_ohms = 419,
.y_plate_ohms = 486,
.pressure_max = 1000,
.pressure_min = 0,
.stopacq_polarity = 1,
.first_conversion_delay = 3,
.acquisition_time = 1,
.averaging = 1,
.pen_down_acc_interval = 1,
};
#endif
#if defined(CONFIG_SPI_SPIDEV) || defined(CONFIG_SPI_SPIDEV_MODULE)
static struct bfin5xx_spi_chip spidev_chip_info = {
.enable_dma = 0,
.bits_per_word = 8,
};
#endif
static struct spi_board_info bf54x_spi_board_info[] __initdata = {
#if defined(CONFIG_MTD_M25P80) \
|| defined(CONFIG_MTD_M25P80_MODULE)
{
/* the modalias must be the same as spi device driver name */
.modalias = "m25p80", /* Name of spi_driver for this device */
.max_speed_hz = 25000000, /* max spi clock (SCK) speed in HZ */
.bus_num = 0, /* Framework bus number */
.chip_select = 1, /* SPI_SSEL1*/
.platform_data = &bfin_spi_flash_data,
.controller_data = &spi_flash_chip_info,
.mode = SPI_MODE_3,
},
#endif
#if defined(CONFIG_TOUCHSCREEN_AD7877) || defined(CONFIG_TOUCHSCREEN_AD7877_MODULE)
{
.modalias = "ad7877",
.platform_data = &bfin_ad7877_ts_info,
.irq = IRQ_PJ11,
.max_speed_hz = 12500000, /* max spi clock (SCK) speed in HZ */
.bus_num = 0,
.chip_select = 2,
.controller_data = &spi_ad7877_chip_info,
},
#endif
#if defined(CONFIG_SPI_SPIDEV) || defined(CONFIG_SPI_SPIDEV_MODULE)
{
.modalias = "spidev",
.max_speed_hz = 3125000, /* max spi clock (SCK) speed in HZ */
.bus_num = 0,
.chip_select = 1,
.controller_data = &spidev_chip_info,
},
#endif
};
/* SPI (0) */
static struct resource bfin_spi0_resource[] = {
[0] = {
.start = SPI0_REGBASE,
.end = SPI0_REGBASE + 0xFF,
.flags = IORESOURCE_MEM,
},
[1] = {
.start = CH_SPI0,
.end = CH_SPI0,
.flags = IORESOURCE_IRQ,
}
};
/* SPI (1) */
static struct resource bfin_spi1_resource[] = {
[0] = {
.start = SPI1_REGBASE,
.end = SPI1_REGBASE + 0xFF,
.flags = IORESOURCE_MEM,
},
[1] = {
.start = CH_SPI1,
.end = CH_SPI1,
.flags = IORESOURCE_IRQ,
}
};
QuoteReplyEditDelete
2008-08-28 09:36:06 Re: touchscreen BF548
Michael Hennerich (GERMANY)
Message: 61255
root:/> cat /proc/interrupts | grep ad7877
258: 0 ad7877
This means IRQ NUMBER: IRQ COUNT , NAME
So you didn't recive an interrupt ... !
-Michael
QuoteReplyEditDelete
2008-08-28 10:26:42 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61259
thanks,
I don't receive interupt how can i change this? if you have an idea
thank you
QuoteReplyEditDelete
2008-08-28 10:41:04 Re: touchscreen BF548
Michael Hennerich (GERMANY)
Message: 61261
Did you make changes to the default BF548-EZKIT kernel config?
What is your EZKIT Hardware revision?
-Michael
QuoteReplyEditDelete
2008-08-28 11:04:04 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61265
i have the
2008R1.5
I have changed
Library Configuration -> tslib
Blackfin build Options -> (FDPIC) Binary Format
graphics support
[*] Backlight & LCD device support ---> │ │
│ │ Display device support ---> │ │
│ │ <*> Support for frame buffer devices │ │
│ │ [*] Enable firmware EDID │ │
│ │ [ ] Enable Video Mode Handling Helpers │ │
│ │ [ ] Enable Tile Blitting Support │ │
│ │ --- Frame buffer hardware drivers │ │
│ │ < > Blackfin ADV7393 Video encoder on uClinux │ │
│ │ <*> SHARP LQ043 TFT LCD (BF548 EZKIT) │ │
│ │ < > Varitronix COG-T350MCQB TFT LCD display (BF527 EZKIT) │ │
│ │ < > Epson S1D13XXX framebuffer support │ │
│ │ < > Virtual Frame Buffer support (ONLY FOR TESTING!) │ │
│ │ Console display driver support ---> │ │
│ │ [*] Bootup logo ---> │ │
│ │ │ │
│ │
driver
<*> Touchscreen interface │ │
│ │ (240) Horizontal screen resolution │ │
│ │ (320) Vertical screen resolution │ │
│ │ <*> Event interface │ │
│ │ <M> Event debugging │ │
│ │ --- Input Device Drivers │ │
│ │ [*] Keyboards ---> │ │
│ │ [ ] Mice ---> │ │
│ │ [ ] Joysticks/Gamepads ---> │ │
│ │ [ ] Tablets ---> │ │
│ │ [*] Touchscreens --->
--------> --- Touchscreens │ │
│ │ < > ADS7846/TSC2046 and ADS7843 based touchscreens │ │
│ │ <*> AD7877 based touchscreens │ │
│ │ < > Gunze AHL-51S touchscreen │ │
│ │ < > Elo serial touchscreens │ │
│ │ < > MicroTouch serial touchscreens │ │
│ │ < > ICS MicroClock MK712 touchscreen │ │
│ │ < > Penmount serial touchscreen │ │
│ │ < > Touchright serial touchscreen │ │
│ │ < > Touchwin serial touchscreen │ │
│ │ < > Philips UCB1400 touchscreen │ │
│ │ < > USB Touchscreen Driver │ │
│ │
this have to use for activate the touch screen ? :
Bitbanging SPI master?
[*] SPI support │ │
│ │ --- SPI Master Controller Drivers │ │
│ │ <*> SPI controller driver for ADI Blackfin5xx │ │
│ │ < > Bitbanging SPI master │ │
│ │ --- SPI Protocol Masters │ │
│ │ < > SPI EEPROMs from most vendors │ │
│ │ < > User mode SPI device driver support │ │
│ │ │ │
│ │ │ │
│ │
Blackfin BF53x ADSP SPI ADC support
in device drivers
in Character devices
│ [ ] AD9960 chip driver │ │
│ │ [ ] Blackfin BF53x ADSP SPI ADC support │ │
│ │ [ ] Blackfin BF5xx PPI Camera frame capture driver │ │
│ │ [ ] Blackfin General Purpose Timers char device interface │ │
│ │ [ ] Blackfin BF5xx PPI Driver │ │
│ │ <*> Blackfin On-Chip OTP Memory Support │ │
│ │ [ ] Enable writing support of OTP pages │ │
│ │ [ ] Blackfin BF53x SPORT support │ │
│ │ [ ] Blackfin 5xx interrupt latency test │ │
│ │ < > TWI/I2C LCD support for HD44780 based LCD modules │ │
│ │ < > AD5304 chip support │ │
│ │ <M> Simple GPIO char interface │ │
│ │ [*] Virtual terminal │ │
│ │ [*] Support for console on virtual terminal │ │
│ │ [ ] Support for binding and unbinding console drivers │ │
│ │ [ ] Non-standard serial port support │ │
│ │ Serial drivers ---> │ │
│ │ [*] Unix98 PTY support │ │
│ │ [ ] Legacy (BSD) PTY support
thanks
QuoteReplyEditDelete
2008-08-28 11:22:30 Re: touchscreen BF548
Michael Hennerich (GERMANY)
Message: 61267
I asked - What is your EZKIT Hardware revision?
ADSP-BF548 EZ-KIT Lite Rev 1.1?
ADSP-BF548 EZ-KIT Lite Rev 1.3?
ADSP-BF548 EZ-KIT Lite Rev 1.4?
-Michael
QuoteReplyEditDelete
2008-08-28 11:35:24 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61268
sorry it's a rev 1.4
QuoteReplyEditDelete
2008-08-28 11:58:39 Re: touchscreen BF548
Michael Hennerich (GERMANY)
Message: 61270
This explains a lot ...
Rev 1.4 is brand new -
They changed the AD7877 /DAV IRQ to IRQ_PB4
in arch/blackfin/mach-bf548/boards/ezkit.c
change .irq = IRQ_PB4,
#if defined(CONFIG_TOUCHSCREEN_AD7877) || defined(CONFIG_TOUCHSCREEN_AD7877_MODULE)
{
.modalias = "ad7877",
.platform_data = &bfin_ad7877_ts_info,
.irq = IRQ_PB4,
.max_speed_hz = 12500000, /* max spi clock (SCK) speed in HZ */
.bus_num = 0,
.chip_select = 2,
.controller_data = &spi_ad7877_chip_info,
},
#endif
you should then get:
root:/> modprobe ad7877
ad7877 spi0.2: touchscreen, irq 123
input: AD7877 Touchscreen as /class/input/input2
-Michael
QuoteReplyEditDelete
2008-08-28 12:17:08 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61271
Thank you very much you save my life.
the touch screen is calibrate. (event_test and ts_config are ok)
I have a
root:/> export QWS_MOUSE_PROTO=auto:$TSLIB_TSDEVICE
root:/> env
QWS_MOUSE_PROTO=auto:/dev/input/event1
TSLIB_PLUGINDIR=/mnt/nfs/t/lib/ts
QTDIR=/usr/local/qt-embedded/
TSLIB_TSDEVICE=/dev/input/event1
TSLIB_CALIBFILE=/tslib/etc/pointercal
TSLIB_CONFFILE=/tslib/etc/ts.conf
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
HOME=/
SHELL=/bin/sh
PATH=/bin:/usr/bin:/etc:/sbin:/usr/sbin
TERM=linux
root:/> ./pictureflow -qws
[9;0] [9;0]Creating mouse: auto
but the touch screen don't workink with pictureflow
I have a problem with my plunging directory i think, I need to mount nfs file in mnt directory.
I want to know if it's my problem or if i can do without it
QuoteReplyEditDelete
2008-08-28 16:37:17 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61279
thanks
QuoteReplyEditDelete
2008-08-28 17:36:24 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61280
export QWS_MOUSE_PROTO=Auto:/dev/input/event1
don't working, picture flow don't take the touchscreen. how can I use the touch screen with qt applications.
QuoteReplyEditDelete
2008-08-28 17:52:23 Re: touchscreen BF548
Mike Frysinger (UNITED STATES)
Message: 61282
i dont think we've tested QT + touchscreen ... you should consult the upstream qt documentation to see how they interface touchscreens
QuoteReplyEditDelete
2008-08-28 18:13:30 Re: touchscreen BF548
Michael Hennerich (GERMANY)
Message: 61283
I know QT works with tslib and the ad7877 -
can you try someting like this .... in your QT app startup script ?
#
# Setup the environment for the touch screen.
#
export TSLIB_CONFFILE=$YOURDIR/tslib/etc/ts.conf
export TSLIB_TSDEVICE=/dev/input/event0
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_CONSOLEDEVICE=none
export TSLIB_CALIBFILE=$YOURDIR/tslib/etc/pointercal
#
# Setup the qt server stuff.
#
export QWS_DISPLAY=LinuxFb:0
export QWS_MOUSE_PROTO="tslib:$TSLIB_TSDEVICE"
#
# Set the library path to execute the application.
#
export LD_LIBRARY_PATH=$QTDIR/lib
QuoteReplyEditDelete
2008-08-28 18:37:38 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61284
thanks to answer.
root:/> env
lib=
LD_LIBRARY_PATH=usr/local/qt-embedded/lib
QWS_DISPLAY=LinuxFb:0
QWS_MOUSE_PROTO=tslib:/dev/input/event1
TSLIB_PLUGINDIR=/lib/
QTDIR=/usr/local/qt-embedded/
TSLIB_TSDEVICE=/dev/input/event1
TSLIB_CALIBFILE=/etc/pointercl
TSLIB_CONFFILE=/etc/ts.conf
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
HOME=/
SHELL=/bin/sh
PATH=/bin:/usr/bin:/etc:/sbin:/usr/sbin
TERM=linux
root:/> ./pictureflow -qws
[9;0] [9;0]
root:/>
root:/>
the touch screen don't working.
QuoteReplyEditDelete
2008-08-28 18:53:34 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61286
I should not apply a patch on qt and to recompile?
QuoteReplyEditDelete
2008-08-28 19:20:42 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61287
i have found this export TSLIB_PLUGINDIR=/usr/lib/ts in http://lists.trolltech.com/qt-embedded-interest/2005-10/thread00014-0.html
but in my board
root:/usr/lib> ls
libpng.so.3 libpng12.so.0
that's why i have tried :
export TSLIB_PLUGINDIR=/lib/libts
there is libts-0.0.so.0 libts.so in it
root:/lib> ls
dejitter.so libmudflap.so.0.0.0 libstdc++.so.6.0.8
input.so libmudflapth.so.0 libthread_db-0.9.29.so
ld-uClibc-0.9.29.so libmudflapth.so.0.0.0 libthread_db.so.1
ld-uClibc.so.0 libnsl-0.9.29.so libts-0.0.so.0
libc.so.0 libnsl.so.0 libts.so
libcrypt-0.9.29.so libpthread-0.9.29.so libuClibc-0.9.29.so
libcrypt.so.0 libpthread.so.0 libutil-0.9.29.so
libdl-0.9.29.so libqte-mt.so libutil.so.0
libdl.so.0 libqte-mt.so.3 libz.so.1
libgcc_s.so.1 libqte-mt.so.3.3 libz.so.1.2.3
libgfortran.so.1 libqte-mt.so.3.3.5 linear.so
libgfortran.so.1.0.0 libresolv-0.9.29.so modules
libjpeg.so.62 libresolv.so.0 pthres.so
libm-0.9.29.so librt-0.9.29.so variance.so
libm.so.0 librt.so.0
libmudflap.so.0 libstdc++.so.6
and also compile qt with tslib support. See ./configure --help
but i don't know how i can do that
./configure -shared -depths 24 -no-cups -no-ipv6 -embedded bfin -little-endian -thread
if you could said me what you think about this
QuoteReplyEditDelete
2008-08-28 19:21:29 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61288
nobody have an idea for ending this thread?
QuoteReplyEditDelete
2008-08-29 00:17:15 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61303
i have to finish it tomorow
QuoteReplyEditDelete
2008-08-29 02:20:54 Re: touchscreen BF548
Andras Szemzo (HUNGARY)
Message: 61309
hi,
Pictureflow (and other Qt apps ) is working with the touchscreen definetly on my custom BF532 board.
Try this:
export QWS_MOUSE_PROTO=Tslib:/dev/input/event0
Regards,
Andras
QuoteReplyEditDelete
2008-08-29 03:07:15 Re: touchscreen BF548
Michael Hennerich (GERMANY)
Message: 61311
You need to make sure that QT during build really finds and knows about tslib.
-Michael
QuoteReplyEditDelete
2008-08-29 10:28:41 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61379
hi thanks
just specify the driver don't working, i don't know why
export QWS_MOUSE_PROTO="tslib:/dev/input/event1
So i try to configure QT with the -qt-mouse-tslib
i need also to specify the location of the library and its headers:
./configure -L <path to tslib library> -I <path to tslib headers>
but this part i don't know do it
i am sure it's not the better think to do but i have install a new tslib 1.0 to build QT with
damien
QuoteReplyEditDelete
2008-08-29 11:07:44 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61380
I think i have to specify this export TSLIB_PLUGINDIR I have this 2 file in :/lib/
libts-0.0.so.0
libts.so
I this it's i need put in PLUNGINDIR
root:/> env
QWS_DISPLAY=LinuxFb:0
QWS_MOUSE_PROTO=tslib:/dev/input/event1
TSLIB_TSDEVICE=/dev/input/event1
LD_LIBRARY_PATH=/usr/local/qt-embedded//lib
TSLIB_FBDEVICE=/dev/fb0
TSLIB_CONSOLEDEVICE=none
TSLIB_CONFFILE=etc/ts.conf
TSLIB_CALIBFILE=/etc/pointercal
QTDIR=/usr/local/qt-embedded/
HOME=/
SHELL=/bin/sh
PATH=/bin:/usr/bin:/etc:/sbin:/usr/sbin
TERM=linux
I have configure QT with
./configure -shared -depths 4,16,24,32 -no-cups -no-ipv6 -embedded bfin -little-endian -thread -qt-mouse-tslib -L~/blackfin-sources/tslib-1.0/ -I~/blackfin-sources/tslib-1.0/src/
My touch screen isn't found by my QT applications
QuoteReplyEditDelete
2008-08-29 12:18:27 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61383
How can i check if QT know TSLIB?
please
QuoteReplyEditDelete
2008-08-29 14:32:54 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61386
I have an ADSP BF548 EZKIT LITE REV 1.4
I try to use pictureflow (QT app) with the touchscreen.
i can calibrate the Touchscreen but it don't run with the QT applications.
my env is
root:/> env
TSLIB_PLUGINDIR=/lib/
QWS_DISPLAY=LinuxFb:0
QWS_MOUSE_PROTO=Tslib:/dev/input/event1
TSLIB_TSDEVICE=/dev/input/event1
LD_LIBRARY_PATH=/usr/local/qt-embedded/lib
TSLIB_FBDEVICE=/dev/fb0
TSLIB_CONSOLEDEVICE=none
TSLIB_CONFFILE=/etc/ts.conf
TSLIB_CALIBFILE=/etc/pointercal
QTDIR=/usr/local/qt-embedded/
HOME=/
SHELL=/bin/sh
PATH=~/blackfin-sources/build/bfin-elf/bin:~/blackfin-sources/build/bfin-uclinux/bin:~/blackfin-sources/build/bfin-linux-uclibc/bin:/bin:/usr/bin:/etc:/sbin:/usr/sbin
TERM=linux
root:/>
how can i do for that the QT work this the TSLIB?
i have build the kernel with TSLIB maibe i need to also install tslib for the qt ( or can i just patch it?)
i have tried to install tsli-1.0 but i have this error
dam@dam-laptop:~/blackfin-sources/tslib-1.0$ patch -p1 < /home/dam/blackfin-sources/tslib-1.0/bfin_tslib_configure_ac.patch
patching file configure.ac
dam@dam-laptop:~/blackfin-sources/tslib-1.0$ ./autogen.sh
configure.ac:7: installing `./install-sh'
configure.ac:7: installing `./missing'
plugins/Makefile.am: installing `./depcomp'
dam@dam-laptop:~/blackfin-sources/tslib-1.0$ patch -p1 < /home/dam/blackfin-sources/tslib-1.0/bfin_tslib.patch
patching file configure
Hunk #1 FAILED at 7172.
Hunk #2 FAILED at 8394.
Hunk #3 FAILED at 10864.
Hunk #4 FAILED at 12350.
Hunk #5 FAILED at 17532.
5 out of 5 hunks FAILED -- saving rejects to file configure.rej
patching file tests/fbutils.c
dam@dam-laptop:~/blackfin-sources/tslib-1.0$ ./configure --host=bfin-uclinux --disable-h2200-linear --disable-ucb1x00 --disable-corgi --disable-collie --disable-h3600 --disable-mk712 --disable-arctic2 --prefix=$TS_INSTALL CFLAGS='-mfdpic -DUSE_INPUT_API'
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for bfin-uclinux-strip... bfin-uclinux-strip
checking for bfin-uclinux-g++... bfin-uclinux-g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... yes
...
config.status: creating Makefile
config.status: creating etc/Makefile
config.status: creating plugins/Makefile
config.status: creating src/Makefile
config.status: creating tests/Makefile
config.status: creating tslib-0.0.pc
config.status: creating config.h
config.status: executing depfiles commands
dam@dam-laptop:~/blackfin-sources/tslib-1.0$ make
make all-recursive
make[1]: entrant dans le répertoire « /home/dam/blackfin-sources/tslib-1.0 »
Making all in etc
make[2]: entrant dans le répertoire « /home/dam/blackfin-sources/tslib-1.0/etc »
make[2]: Rien à faire pour « all ».
make[2]: quittant le répertoire « /home/dam/blackfin-sources/tslib-1.0/etc »
Making all in src
make[2]: entrant dans le répertoire « /home/dam/blackfin-sources/tslib-1.0/src »
/bin/bash ../libtool --tag=CC --mode=compile bfin-uclinux-gcc -DHAVE_CONFIG_H -I. -I.. -DPLUGIN_DIR=\"/lib/ts/\" -DTS_CONF=\"/etc/ts.conf\" -DTSLIB_INTERNAL -mfdpic -DUSE_INPUT_API -MT ts_attach.lo -MD -MP -MF .deps/ts_attach.Tpo -c -o ts_attach.lo ts_attach.c
bfin-uclinux-gcc -DHAVE_CONFIG_H -I. -I.. -DPLUGIN_DIR=\"/lib/ts/\" -DTS_CONF=\"/etc/ts.conf\" -DTSLIB_INTERNAL -mfdpic -DUSE_INPUT_API -MT ts_attach.lo -MD -MP -MF .deps/ts_attach.Tpo -c ts_attach.c
ts_attach.c:1: erreur: -mfdpic is not supported, please use a bfin-linux-uclibc target
make[2]: *** [ts_attach.lo] Erreur 1
make[2]: quittant le répertoire « /home/dam/blackfin-sources/tslib-1.0/src »
make[1]: *** [all-recursive] Erreur 1
make[1]: quittant le répertoire « /home/dam/blackfin-sources/tslib-1.0 »
make: *** [all] Erreur 2
dam@dam-laptop:~/blackfin-sources/tslib-1.0$
could you help me
QuoteReplyEditDelete
2008-08-30 00:41:40 Re: touchscreen BF548
Mike Frysinger (UNITED STATES)
Message: 61393
the error already tells you the problem:
ts_attach.c:1: erreur: -mfdpic is not supported, please use a bfin-linux-uclibc target
QuoteReplyEditDelete
2008-09-02 13:12:53 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61552
I have
BF548 rev1.4
QT 3.3.5
touchscreen AP7877
I have build the kernel with the configuration to use the touchscreen.
I can calibrate it so I think it working.
Ihave build QT (in FDPIC dynamic loadable shared library) and the kernel,
I can execute qt application like drawlines and picture flow.
but this tow don't working together.
I have to say to the QT library that i want to use the tslib.
I have try to set this environment :
QWS_MOUSE_PROTO=tslib:/dev/input/event1
TSLIB_TSDEVICE=/dev/input/event1
TSLIB_CALIBFILE=/etc/pointercl
TSLIB_CONFFILE=/etc/ts.conf
TSLIB_CONSOLEDEVICE=none
TSLIB_FBDEVICE=/dev/fb0
QTDIR=/usr/local/qt-embedded/
HOME=/
SHELL=/bin/sh
PATH=/bin:/usr/bin:/etc:/sbin:/usr/sbin
TERM=linux
but that's is not enough. how i have to do to learn the tslib to the qt applications.
could you help me please
QuoteReplyEditDelete
2008-09-02 14:56:11 Re: touchscreen BF548
Robin Getz (UNITED STATES)
Message: 61555
Damien:
You might get better response on the QT forums - since most people here have not used that it alot of detail.
http://lists.trolltech.com/qt-interest/
-Robin
QuoteReplyEditDelete
2008-09-05 15:44:29 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61714
i need the patch of TSlib for QTembedded 3.3.5 where can i find it?
I have search in the QT websites but i haven't found it.
could you help me
QuoteReplyEditDelete
2008-09-10 15:02:34 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61907
I haven't solved my problem, Robin, there is application that can i run to test my Toush screen, but without QT, to be sure that it is running well in my board.
Please
QuoteReplyEditDelete
2008-09-11 03:05:50 Re: touchscreen BF548
Mike Frysinger (UNITED STATES)
Message: 61927
you've already seen the documentation in our wiki that shows you how to test a touchscreen using only low level utilities
QuoteReplyEditDelete
2008-09-11 07:43:24 Re: touchscreen BF548
Robin Getz (UNITED STATES)
Message: 61980
Damien:
As Mike said - there is an example at:
https://docs.blackfin.uclinux.org/doku.php?id=touchscreen#test_touch_screen_hardware
QuoteReplyEditDelete
2008-09-11 09:22:44 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 61990
hello Robin
I have already run event_test and ts_calibrate and they working.
but the other test of TSlib are not found like ts_test or ts_print...
I search to be sure that my TS is well install in my board because I don't find what can i do more with QT. that's why i have asked if i can test it with other aplication.
To install TSlib in QT, can i use the Tslib file in my uCLinux kernel or I have to install a new source of TSlib?
because i need to configure and build the TSlib if i do that with the kernel lib, maybe it don't like it.
I need to have a lib directory and header directory of TSlib to give to QT
best regards
QuoteReplyEditDelete
2008-09-11 10:41:42 Re: touchscreen BF548
Robin Getz (UNITED STATES)
Message: 61993
Damien:
If event test works - the hardware and the driver/kernel are working, and the problem is in userspace somewhere.
QuoteReplyEditDelete
2008-09-16 02:21:13 Re: touchscreen BF548
Klaus Hachmeister (GERMANY)
Message: 62203
----------
I asked - What is your EZKIT Hardware revision?
ADSP-BF548 EZ-KIT Lite Rev 1.1?
ADSP-BF548 EZ-KIT Lite Rev 1.3?
ADSP-BF548 EZ-KIT Lite Rev 1.4?
-Michael
----------
1.)
What is/are the difference(s) between Rev 1.3 to Rev 1.4?
2.)
Ist there a changelog available?
3.)
Do you/anybody know why they changed the schematic?
4.)
In Rev 1.3 this pin is connected to PJ11. This is what they use in "uClinux-dist-2008R1.5-RC3".
So i guess this uclinux is 100% compatible to Rev 1.3 ???
5.)
Is there a notice inside uClinux about the related EZKIT Hardware revision ?
thanks,
Klaus Hachmeister
TranslateQuoteReplyEditDelete
2008-09-16 02:58:04 Re: touchscreen BF548
Mike Frysinger (UNITED STATES)
Message: 62206
read the EZKit manuals if you want to know about EZKits. we dont maintain that board information. if the manual doesnt contain the info you want, you'll have to ask at analog.com.
the documentation wiki and source code was updated a while ago to note the PJ11 change.
we only validate hardware that existed when a release was made. if hardware changes are made after a point, you cant expect old software to continue to work.
QuoteReplyEditDelete
2008-09-16 05:03:02 Re: touchscreen BF548
Klaus Hachmeister (GERMANY)
Message: 62235
read the EZKit manuals if you want to know about EZKits. we dont maintain that board information. if the manual doesnt contain the info you want, you'll have to ask at analog.com.
the documentation wiki and source code was updated a while ago to note the PJ11 change.
we only validate hardware that existed when a release was made. if hardware changes are made after a point, you cant expect old software to continue to work.
------------------------------
Thank you Mike,
i agree with you. On
http://docs.blackfin.uclinux.org/doku.php?id=hw:boards:bf548-ezkit
i found that this is the only difference i should pay attention to when using board 1.4 (or later). Right?
Wouldn`t it be nice if the file "release_notes" inside the uClinux-dist would contain a note for the hardware-revision of the supported (or tested) boards?
Klaus Hachmeister
TranslateQuoteReplyEditDelete
2008-09-16 06:59:35 Re: touchscreen BF548
Robin Getz (UNITED STATES)
Message: 62238
Klaus:
That is a great idea. We will try to do that.
-Robin
QuoteReplyEditDelete
2008-09-16 14:12:48 Re: touchscreen BF548
Mike Frysinger (UNITED STATES)
Message: 62262
we havent tracked these things in the past because there isnt supposed to be a hardware difference that affects software, but since that is clearly not the case, keeping track of that information would be pretty useful for many people
as far as we know, that is the only difference for rev 1.4 bf548-ezkits ... but we havent done an exhaustive analysis ... after all, these things arent *supposed* to change
QuoteReplyEditDelete
2008-09-18 11:47:42 Re: touchscreen BF548
damien OLLIVE (UNITED STATES)
Message: 62390
ok my problem was that i have download a TSLib but i have to use the TSLib that i had in my uClinux distribution
./configure -shared -depths 4,16,24,32 -no-cups -no-ipv6 -embedded bfin -little-endian -thread -qt-mouse-tslib -L/home/dam/blackfin-sources/uClinux/staging/usr/lib -I/home/dam/blackfin-sources/uClinux/staging/usr/include -lts -qvfb
that working well now
thank you very mutch for your help