#apertus IRC Channel Logs

morning folks!

i do have some questions about the PWM i2c fan controller

hi

Aha, so should i send an email to "*email address removed*" or post my question here anyway ?

when he sees it, he will reply

Hello

well, let's hear then ...

actually nothing will be connected on the i2c bus right now, it is the interface to control the PWM part

the temperature sensor(s) are distributed over the various boards and will be handled outside the FPGA

probably the most important sensor is on the Zynq itself which measures the die temperature

great, i started writing an early prototype of an i2c slave in verilog, with a testbench is it okay if i sent the github repo. now and maybe you give me your feedback or its too early for doing this ?

no problem with that ... note that all our designs so far are in VHDL, but verilog is not a problem per se, you just have to figure out how to make it work in a mixed design

Okay almost finished testing, uploading the repo. i will send the github link here once i am done

Great i will create an account now and post a comment under the idea page

no i am not, just requested joining the google group "https://groups.google.com/forum/#!forum/apertus-gsoc"

all pending requests have been accepted so not sure if you are in already

excellent!

@BAndiT1983 - Hey , Have you included the path to QtAV header files in the standard include paths while configuring ?

Hi, is django needed for the REST Interface project ? There is a resource link on that task leading to a O'reilly book "Test-Driven Development with Python", it is advised to read 1-4 chapters, it has py and django based app development content.

hi anuditverma, you should discuss it with maltefiala, post your question in the lab, we aggreed, that he is the main mentor for the task, i'm just providing additional support for the internal parts

no problem

Hey BAndit1983 , I did few changes in CMakeLists.txt of the root folder- http://pastebin.com/x24mPS8t , I changed the path . By doing this , that error was corrected but now i have an another error - http://pastebin.com/YMqmd0rB

it seems that your system does not build .so files

check if libqtav.so and libqtavwidgets is available after the build

still wondering that you need to adjust cmakelists.txt, qtav_project is a name which is used internally in the cmake settings, but the main folder is still called QtAV on my machine

also check if ffmpeg dev libs are available, as the errors also suggest that undefined references are belonging to ffmpeg

that's the cause of undefined reference

this line in cmakelists.txt of OCui should output the location -> message(WARNING "QtAV BINARY_DIR: ${BINARY_DIR}")

i've marked most messages with warning, so they stand out while terminal spits out a ton of messages

both libqtav.so and libqtavwidgets

is this the output of QtAV_BINARY_DIR?

Roopal08, you should get a real IRC client

funny thing, you are right about extending from qt to qtavproject, but what's more funny, it still builds without a change, now in qtcreator :D

i will adjust the paths for future use

are you using x64 or x86 machine? as undefined reference can also occur if the lib is not binary compatible

I am using x64 machine

there should be 6 .so files for QtAV, under /home/dev/Source/OpenCine_build/3rdParty/QtAV/src/QtAV_project-build/lib

have you installed ffmpeg dev libs?

Is this fine?

also retested it several times afterwards

yes

it is possible that the libs there are older

as the methods it's complaining about are very similar to ffmpeg ones

just a moment, have to take a look how to find the version

libswscale-dev:amd64 7:2.8.11-0ubuntu0.16.04.1 amd64

yeah i have 6:9.20-0ubuntu0.14.04.1 amd64

linuxmint has proved itself worthy over years as ubuntu seems to be bloating over years

very good, congratulations

as you wanted to do debayering you should look through ProcessingTest, it's a mess, but should be still usable

there are some debayering methods implemented in there, it was planned that for gsoc OC will be extended by different algorithms, for example SHOODAK which we got from a guy who is also interested in apertus cameras