Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Matom

Pages: [1] 2
1
Software Dev / Re: Building Qt-creator
« on: November 22, 2018, 11:23:50 PM »
Dear Foobar,

Thank you! That sounds probable. And even when I manually add the few ones that are missing to begin with, I get a bunch of new error messages about undefined references and missing files.

I will try to re-copy everything from the sd-card. The manual way might become very tedious.

Hopefully it works. Have a great weekend.

2
Software Dev / Re: Building Qt-creator
« on: November 22, 2018, 08:27:31 AM »
It worked with linking the libraries :) (at least the error messages are gone).

Can you send me the OMX_Core library? I cannot seem to find it online.

Thank you in advance.

3
Software Dev / Re: Building Qt-creator
« on: November 21, 2018, 06:46:59 AM »
I did set the Sysroot path..


When I look in /home/majtom/Work/chronos-sdk/targetfs/usr/lib I can see that the versions of the libraries are different. For example the libxml2.so.2 in my folder is libxml2.so.2.7.8. I will try to link the versions.

But, there is no OMX_Core library at all.

4
Software Dev / Re: Building Qt-creator
« on: November 15, 2018, 08:03:01 AM »
Thank you very much. This helped a lot. And I am so sorry to keep bothering you.

I found out that my libts.so was a different version, so I made a symbolic link from <path to sysroot>/usr/lib/libts.so to the version in my <path to sysroot>/usr/lib folder.
 
After doing that I got a new error message when making the tslib config fest

undefined reference to `dlsym@GLIBC_2.4'
 undefined reference to `dlopen@GLIBC_2.4'
 undefined reference to `dlclose@GLIBC_2.4'


I avoided this error by adding -ldl to the qmake file (QMAKE_LIBS += '-lts -ldl').

Now, I could configure and install Qt. Wuhuu! However, after following all the steps on github about the settings of Qt, I tried to build the camApp but got these errors about missing libraries:

  /usr/lib/gcc-cross/arm-linux-gnueabi/5/../../../../arm-linux-gnueabi/bin/ld: cannot find -lOMX_Core
/usr/lib/gcc-cross/arm-linux-gnueabi/5/../../../../arm-linux-gnueabi/bin/ld: cannot find -lgmodule-2.0
/usr/lib/gcc-cross/arm-linux-gnueabi/5/../../../../arm-linux-gnueabi/bin/ld: cannot find -lgobject-2.0
/usr/lib/gcc-cross/arm-linux-gnueabi/5/../../../../arm-linux-gnueabi/bin/ld: cannot find -l:libxml2.so.2
/usr/lib/gcc-cross/arm-linux-gnueabi/5/../../../../arm-linux-gnueabi/bin/ld: cannot find -lgthread-2.0
/usr/lib/gcc-cross/arm-linux-gnueabi/5/../../../../arm-linux-gnueabi/bin/ld: cannot find -lglib-2.0
/usr/lib/gcc-cross/arm-linux-gnueabi/5/../../../../arm-linux-gnueabi/bin/ld: cannot find -lgstapp-0.10


I am wondering if this is a sign that there is something completely wrong with my libraries or if there is an easy way to get all of them?

I really appreciate the help!

5
Software Dev / Re: Building Qt-creator
« on: November 13, 2018, 06:04:26 AM »
Thank you for all the info.

Quote
Wonderful, that sounds like you have successfully applied the v0.3.1 update to your targetfs. You will probably need to run qtconfig.sh again after that to make sure that Qt is setup correctly.

I did do that, several times, but the error keeps popping up. Therefore I tried to configure the earlier Qt version following the instructions in your link, but here I get the “good old” :

The tslib functionality test failed!
 You might need to modify the include and library search paths by editing
 QMAKE_INCDIR and QMAKE_LIBDIR in
 /home/majtom/Work/qt-everywhere-opensource-src-4.8.7/mkspecs/qws/linux-omap2-g++.


BUT, I do have the tslib.h file in  ~/Work/chronos-sdk/targetfs/usr/include directory and I did add the paths to the qmake file in ~/Work/qt-everywhere-opensource-src-4.8.7/mkspecs/qws/linux-omap2-g++. The last four lines of the qmake.conf now look like this:

#defines for tslib
QMAKE_INCDIR += ~/Work/chronos-sdk/targetfs/usr/include
QMAKE_LIBDIR += ~/Work/chronos-sdk/targetfs/usr/lib

load(qt_config)

I am not completely sure about the QMAKE_LIBDIR += ~/Work/chronos-sdk/targetfs/usr/lib. Because there are actually no tslib files in this folder. They are in some of the sub-directories like opkg/info. Should I link directly to that one?
Maybe it is some kind of conflict between the tslib.h from the camera microUSB (I have camApp version 0.3.0) and the qt version?

I hope you are able to help me again.

6
Software Dev / Re: Building Qt-creator
« on: November 12, 2018, 02:13:37 AM »
Dear Foobar,

Thank  you very much for the answer. I am really keen on starting to play around with the new software, so I appreciate the help with getting Qt up and running.

I tried the second resolution but I get almost the same error message after I run the qtconfig.sh script.

You have not explicitly asked to use pkg-config and are cross-compiling.
pkg-config will not be used to automatically query cflag/lib parameters for
dependencies

The QtDBus module cannot be enabled because libdbus-1 version 0.93 was not found.

 Turn on verbose messaging (-v) to /home/majtom/Work/chronos-sdk/qt-everywhere-opensource-src-4.8.7/configure to see the final report.
 If you believe this message is in error you may use the continue
 switch (-continue) to /home/majtom/Work/chronos-sdk/qt-everywhere-opensource-src-4.8.7/configure to continue.


And when I try to make from ~/Work/chronos-sdk/qt4-install/qmake I get the following error message:
make: Nothing to be done for 'first'.

I do get a bunch of dbus header files in my targetfs after extracting the update.tgz.

In <path to targetfs>/usr/include/dbus-1.0/dbus I have 22 different header files and in <path to targetfs>/usr/lib/dbus-1.0/include/dbus I only get one: dbus-arch-deps.h. The folder that is referred to in the end of the qtconfig.sh script ( <path to targetfs>/usr/lib/arm-linux-gnueabi/dbus-1.0/include) does not exist. Could this have something to do with it? Or something about the pkg-config?

Otherwise, is there a way to deploy the camApp V0.2.5 on a camera with FPGA version 3.6?



7
Software Dev / Building Qt-creator
« on: November 09, 2018, 02:48:24 AM »
Dear Krontech,

I am trying to build Qt 4.8.7  on an Ubuntu 16.04 OS.
But the configuration fails and I cant make && make install . The error message I get when running the qtconfig.sh script is the following:

"Creating qmake. Please wait...
make: Nothing to be done for 'first'.

You have not explicitly asked to use pkg-config and are cross-compiling.
pkg-config will not be used to automatically query cflag/lib parameters for
dependencies

The QtDBus module cannot be enabled because libdbus-1 version 0.93 was not found."


I followed the steps from the github rep. Do have any experience with this error?

I have tried google, but many different solutions come up.

Cheers,
Maja

8
Software Dev / Re: Monitoring value on IO trigger
« on: August 09, 2018, 08:08:52 AM »
Okay, thank you very much.

The answer might be the same to the following question, but is there a way to access the DAC?

I see some mentioning of io1DAC and io2DAC, but I cant find the exact address. So far we have tried to read from map_base+offset but the values there are always the same. I would really like to read an analog signal somehow. 

Do you have any suggestions?

9
Chronos User Discussion / Re: NTP for precise timing
« on: August 03, 2018, 07:51:50 AM »
Thank you both for the answers.

NiNeff, do you have experience with the delay/accuracy with this method?

10
Software Dev / Monitoring value on IO trigger
« on: August 02, 2018, 05:36:22 AM »
Hi Krontech,

Is there a way to monitor the value on the trigger inputs in the software?

I would like to constantly monitor the value (low/high or 0/1) on the trigger inputs, like you can do on e.g. a GPIO pin. The idea is to send this value to a pixel on the image, thereby knowing if the given trigger input was low/high during that specific frame.

Cheers,
Maja

11
Chronos User Discussion / NTP for precise timing
« on: August 01, 2018, 12:22:21 AM »
Dear All,

I am using the camera for scientific purposes and I need precise timing. Ideally I would like to install ntp (network time protocol) and use it to synchronize the camera time to my computer which is connected to a GPS. I am trying to find a ntp package already compiled for the camera processor type (armv7l), but so far, no luck.

Do any of you have experience with this or other methods for precise timing on the camera?

Cheers, Maja

12
Software Dev / Re: Deploying camApp from Qt Creator
« on: June 13, 2018, 09:09:11 AM »
I also timed the routine without including my algorithm and in this case the cpu-time was around 2 seconds for 1000 frames, whereas the real time was still 16 seconds. Therefore, I think that there must be a delay or a set frame-rate somewhere. Maybe in the OMX files? I just can't seem to find the one that does the trick.

13
Software Dev / Re: Deploying camApp from Qt Creator
« on: June 06, 2018, 12:54:21 AM »
Dear David,

Thank you,  I'll try that.

I'm working in the VIL_ClientCbFilledBufferDone function. Here I do a bit of image analysis on each buffer, before it is passed on in the code. My algorithm is very light and is not the limiting factor when is comes to processing time. I have timed the function using clock() and time() and I can see that the CPU time (from clock()) is much lower (8 seconds to process 1000 frames) than the actual time (16 seconds for 1000 frames). The 16 seconds make me think that there is a value of 60 fps set somewhere in the code, maybe because the buffer is used display on the LCD. I don't use the display, but just want as many frames as possible to be processed in order to catch events of a few ms duration. I hope this makes sense ;)

Cheers,
Maja


14
Software Dev / Re: Deploying camApp from Qt Creator
« on: June 05, 2018, 01:46:02 AM »
Dear David,

I am starting to get problems that I did't have before. I have had to restore the microSD card 3 times within a week (when I was working out of the qt folder before, this only happened 1 time in 3 months). It happens when I work in Qt for a while and keep updating the camApp. Once in a while a connection error happens and I can't access the camera with ssh or Qt and a hard reboot is the only option. However the reboot can't open the camApp, so I have to restore the SD card. Is there a way to avoid this? If not, I can live with it, because I am almost done with the trigger.

However, I have another question:
There is a big difference between the CPU time and the real time of my trigger function i video.cpp. My guess is that there is a frame-rate set or delay/sleep/wait somewhere in the code that limits the frame-rate. Where is this?  I have changed the definition of MAX_LIVE_FRAMERATE in camera.h but this does not change it.

Thank you in advance, Maja.

15
Software Dev / Re: Deploying camApp from Qt Creator
« on: June 04, 2018, 08:51:10 AM »
Thank you David, I just backed up the original app, and so far there are  no problems.

Pages: [1] 2