Posts by ForTest

I was talking about the fsvybrid v1.0

I've update my board with the new fsvybrid 1.2 and it works perfectly

Thank you

Hello

We have a problem with an EDT display running with a PicoCOMA5 board

With the Kernel installed when we've received the board the display worked well and the matchbox WM system start properly
We've updated the kernel with a customized one by following the procedure for fsvybrid and after this update the screen doesn't work

Here a screenshot of the display : <!-- m --><a class="postlink" href="http://oi60.tinypic.com/2ziwj9e.jpg">http://oi60.tinypic.com/2ziwj9e.jpg</a><!-- m -->

We had a similiar issue with a PicoCOM4 with the same display and the solution was to use some customized settings to recompile the Kernel : <!-- l --><a class="postlink-local" href="http://www.fs-net.de/phpBB2/viewtopic.php?f=46&t=3491">viewtopic.php?f=46&t=3491</a><!-- l -->

Can you give us the factory settings? (we thinks were different from the fsvybrid_defconfig )

/dev/mmcblk0p1 on /sdcard type vfat (ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

try

Ok, we know the pinout of that connector.
We need to know the connection between the PicoCOM4 CPU and the PicoCOM-startinf2 board

We have bought a PicoCOM4 starter kit with ETM070001ADH6 display.
What is the pinout from the touch screen connector to the PicoCOM-startintf2 board?

The touch screen connector i mean this

[IMG:http://s14.postimg.org/rf5u1nle9/DSC_0226.jpg]

I have some questions about SPI on the board PicoCOM4

- Where can i get an application demo (with source code if possible) for SPI?
- Can the SPI work like a slave device? (we have to connect a PicoCOM4 board with our embedded MCU and we would like to comunicate through SPI interface; so we would like to have the MCU as master and PicoCOM4 as slave)

Thank you

My problem is not on the target but it's in the host
I have installed Qwt with YUM and the Qt creator recognize it correctly and it work for i386 projects
But when i try to insert a Qwt widget and compile it for ARM i receive a lot of errors

I've read that the file qwtconfigure.pro must be compiled with the qmake generated from the buildroot but it never works
So , my question is if there's a procedure for installing Qwt in the host and make it ready for the cross compilation

I have some trouble when i try to run the qwtPlot inside my Qt IDE
Anyone know if is there a procedure for install Qwt for ARM ?

The i386 projects work properly and i can see the graph
When i try to cross compile for ARM i get a lot of errors

Thanks

Thank you for the suggests

I have only a last question
I'm trying to change the linux logo on startup (splash screen)
I've seen there are some F-S customized logo 80x80 in PPM format
I'd like to replace the linux logo with a customized splash screen in 800x480
Is it possibile?

I've seen that in kernel the logos are managed in /drivers/video/logo
What's the right way to insert a png or jpg image at startup?

Ok

Now i'm trying to speed up the boot sequence
For example showing a preloader screen after few seconds from the start
I think i have to remove lots of drivers that i will never use (my board should only have display, touch, serial comunication and the qt library)

What is the best way to increase the boot speed?

Yes i'm using 1.4

I've found the problem
Wrong virtual resolution size in picocom4 defconfig file
So the buffer were not initialized

The Qt examples works correctly and also the touch screen

Do you know if PicoCOM4 works with kernel version greather than 2.6.38 ?
Thank you

I have installed the Qt library but when i try to run a Qt application (qt demo and examples) i get the following message:

/dev/fb0 doesn't exist
what could be the problem?

Hello

I'm trying to develop a very simple GUI interface for a PicoCOM4 board using Qt (qt-everywhere-opensource) under Linux
I have no experience about Qt programming and i'm trying to understand if this board is good for develop our industrial applications
I've read the PC_PM_Developing_and_Debugging_LINUX.pdf relased by f-s and many articles about cross compilation of Qt applications for ARM

Exist a document or a procedure to follow for draw a simple dialog box or a window and test the display and touchscreen?

Thank you

Thank you for the answer

ok, i've edited the ft5x06 driver and when i touch the display i see the coordinates in the console

in /sys/class/i2c-dev/i2c-0/device i have s3c2410-i2c

into the folder 0-0038 i have gain , thold and offs files for change the gain threshold and offset parameters and it work fine

i would to change these values programmatically and i've written a very simple program in C but it fails on i2c_smbus_read_word_data returning <0 value and i get the error "Failed to set slave address: Device or resource busy"

Can anyone help me?

#include "i2c-dev.h"
#include <linux/types.h>
#include <stdio.h>
#include <fcntl.h>

#define ADDRESS 0x38
#define REGIST 0x30

int main(int argc, char *argv[])
{

int adapter_nr = 0;

snprintf(filename, 19, "/dev/i2c-%d", adapter_nr); /* The I2C adapter to use */
file = open(filename, O_RDWR);
if (file < 0) {
printf("\nADAPTER ERROR\n");
return -1;
}
if (ioctl(file, I2C_SLAVE, ADDRESS) < 0) {
fprintf( stderr, "Failed to set slave address: %m\n" );
return -1;
}
res = i2c_smbus_read_word_data(file, REGIST);
if (res < 0) {
printf("\nERROR SMBUS %d\n",res);
return -1;
} else {
/* res contains the read word */
}
}

Hi, i have two problems with my touchscreen :

- I want to get the x,y,z coordinates
- I want to increase the threshold and gain of the touch

During the initializations phase i get the folowing message:

With the command cat /dev/input/event1 i get binary data when i touch the screen so the device is mapped with the handler event1 and the driver seems to be the ft5x06_ts.c

Is this correct?
How can i do what i want?

Thank you in advance

Thank you
It work perfectly!

I've bought a PicoCOM4 board with EDT ETM070001ADH6 display.
After the boot procedure the display show just an half of the Linux logo
How can i fix this problem?

This is the kernel's configuration file :