Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. [solved] why the Qt program is used libts-0.0.so.0 in mini2440?

[solved] why the Qt program is used libts-0.0.so.0 in mini2440?

Scheduled Pinned Locked Moved Installation and Deployment
libts-0.0.so.0mini2440
26 Posts 3 Posters 13.8k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    morkia
    wrote on 29 Aug 2015, 23:15 last edited by morkia
    #17

    @SGaist Yes but in my personal experience It's better to use a window manager like tiny X. Also since Qt is usually compiled from source for such cases, it's difficult for new and inexperienced users to get it to work right i.e. supplying proper configurations etc.

    This is the reason I'm continuously asking her to tell me how she has built the Linux for her device. If she uses X, then she won't have to worry about input device handling. It simply becomes transparent to her.

    by that statement I meant the way Linux is usually built and deployed on devices like hers.

    1 Reply Last reply
    0
    • M Offline
      M Offline
      MhM93
      wrote on 30 Aug 2015, 05:12 last edited by
      #18

      @morika : Hi and thanks. I really want to know how to enable touch and understand the ARM structure.

      I could help you better if you would tell me what kind of Linux you are using

      [root@FriendlyARM /]# uname -a
      Linux FriendlyARM 2.6.32.2-FriendlyARM #16 Tue Dec 23 15:08:43 CST 2014 armv4tl unknown

      how you installed it on your board

      like the other website says : connect it with serial port and usb. in DNW set the port . press the key :
      x
      f
      v->supervivi128
      q
      ->change the kernel size and root size and set param to mtdblock3
      k->load zImage_T35(the screen type)
      y->rootf about 85MB
      b->boot the Linux.
      the the Linux is installed.

      @SGaist : really thanks.
      by that topic link :
      [root@FriendlyARM /]# ls -la /dev/input
      drwxr-xr-x 2 root root 0 Jan 1 08:00 .
      drwxr-xr-x 7 root root 0 Jan 1 08:00 ..
      crw-rw---- 1 root root 13, 64 Jan 1 08:00 event0
      crw-rw---- 1 root root 13, 63 Jan 1 08:00 mice

      I changed them by the last code in that topic : chmod a+rw /dev/input/mouse0 ( i have mice instead of mouse0 so edit it)
      [root@FriendlyARM /udisk]# ls -la /dev/input
      drwxr-xr-x 2 root root 0 Jan 1 08:00 .
      drwxr-xr-x 7 root root 0 Jan 1 08:00 ..
      crw-rw-rw- 1 root root 13, 64 Jan 1 08:00 event0
      crw-rw-rw- 1 root root 13, 63 Jan 1 08:00 mice

      but no touch again. ( ts_calibrate worked but my application touch not work)

      Part of the problem is here is that just saying -qws doesn't tell Qt that you have a touch screen at hand.

      I think I don't understand it !!the device demo is worked with this parameter./fluidluncher -qws -> this is worker completely even touch work.

      H.Ghassami

      1 Reply Last reply
      0
      • S Offline
        S Offline
        SGaist
        Lifetime Qt Champion
        wrote on 30 Aug 2015, 21:45 last edited by
        #19

        ARM is just a processor architecture, you can find yourself having the exact same problem on x86. What matters more is the distribution you use as well as the kernel.

        Did you compile fluidlauncher yourself ?

        Interested in AI ? www.idiap.ch
        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply
        0
        • M Offline
          M Offline
          MhM93
          wrote on 31 Aug 2015, 04:11 last edited by
          #20

          @SGaist : Did you compile fluidlauncher yourself ? No . this demo is in device and worked. you mean my compiler is wrong? but i compile my project as the same as some sites guide.

          H.Ghassami

          1 Reply Last reply
          0
          • S Offline
            S Offline
            SGaist
            Lifetime Qt Champion
            wrote on 31 Aug 2015, 21:45 last edited by
            #21

            No, not your compiler, just trying to narrow down the sources of your problem. Are you using a custom compiled Qt or the same provided on your board ?

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply
            0
            • M Offline
              M Offline
              MhM93
              wrote on 1 Sept 2015, 07:16 last edited by
              #22

              @SGaist : I used arm-linux-gcc4.4.3 and qt4.6.3. I downloaded from internet.
              In most sites i saw for tiny6410 at first install tslib( and also mini2440) but in tiny6410 pdf does not do that. I install everything exactly like pdf. and everything is worked ( without tslib installation ). and my app is worked perfectly over tiny6410 ( the touch is work too). I wanna to say is it possible my device (mini2440) have problem or another problem ? I am so confused. O.o

              H.Ghassami

              1 Reply Last reply
              0
              • S Offline
                S Offline
                SGaist
                Lifetime Qt Champion
                wrote on 1 Sept 2015, 21:49 last edited by
                #23

                You should check for the differences between the two hardware and software wise

                Interested in AI ? www.idiap.ch
                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                1 Reply Last reply
                0
                • M Offline
                  M Offline
                  morkia
                  wrote on 2 Sept 2015, 01:44 last edited by morkia 9 Feb 2015, 01:50
                  #24

                  @MhM93 I suggest you build yourself a Linux using buildroot. The pdf file supplied with the board might not be accurate and/or complete. Are you using the demo root file system image supplied with your board or you have compiled it yourself? It should be a rootfs.yaffs or something similar. Don't use the demo rootfs supplied. Compile it yourself. Check buildroot out. I suggest using the versions below 2013 and also select CodeSourcery tool chain because the GCC compiler didn't produce the correct binaries (probably due to some incorrect configurations either within buildroot make files or something else.). If you wanted a more detailed howto then let me know.

                  1 Reply Last reply
                  0
                  • M Offline
                    M Offline
                    MhM93
                    wrote on 2 Sept 2015, 04:20 last edited by
                    #25

                    @SGaist : thanks. i should do that.
                    @morkia : thanks. Yes. i like to know every thing about the embedded system and all you said. If you help me, become me so Glad. thanks ( this is my email : haniyeh.ghassami A T gmail D O T com)

                    H.Ghassami

                    1 Reply Last reply
                    0
                    • M Offline
                      M Offline
                      morkia
                      wrote on 24 Sept 2015, 16:06 last edited by
                      #26

                      for starters search "buildroot" in google. Go to their website or go here directly. pick a version you like but I recommend the ones below 2013 because the higher versions didn't work for me. Download and extract it then go in the directory in which you extracted the archive and type make menuconfig (it might complain about ncurses in that case install libncurses I installed it using this command: sudo apt-get install libncurses5). Choose the packages and configurations and then press Escape key untill you are prompted to save changes then say yes and simply do a make. Remember to choose proper toolchain and compiler before. If you have any further questions feel free to ask here.

                      1 Reply Last reply
                      0

                      • Login

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Users
                      • Groups
                      • Search
                      • Get Qt Extensions
                      • Unsolved