Current Server Time: 08:40 (Central Europe)

#apertus IRC Channel Logs

2019/05/11

Timezone: UTC


00:05
johnathan
joined the channel
00:08
johnatha_
joined the channel
00:09
johnathan
left the channel
00:11
Bertl
off to bed now ... have a good one everyone!
00:11
Bertl
changed nick to: Bertl_zZ
00:12
johnatha_
left the channel
00:14
johnathan
joined the channel
00:22
Nira
changed nick to: Nira|away
00:23
johnathan
left the channel
01:18
futarisIRCcloud
left the channel
02:57
Spirit532
left the channel
02:57
Spirit532
joined the channel
03:19
Spirit532
left the channel
03:22
Spirit532
joined the channel
04:59
futarisIRCcloud
joined the channel
05:16
rahul-
joined the channel
05:17
rahul|
left the channel
06:41
niemand
joined the channel
06:41
niemand
left the channel
06:41
niemand
joined the channel
06:45
johnathan
joined the channel
07:08
futarisIRCcloud
left the channel
07:36
se6astian|away
changed nick to: se6astian
07:40
se6astian
good day
07:46
BAndiT1983|away
changed nick to: BAndiT1983
07:56
se6astian
vup is there a way to download the entire https://files.niemo.de/axiom_pdfs/HARDWARE/AXIOM/ archive?
08:25
blakec[m]
left the channel
08:25
cryteno[m]
left the channel
08:25
WalterZimmermann
left the channel
08:25
a13b
left the channel
08:25
elkos
left the channel
08:25
apurvanandan[m]
left the channel
08:25
abeljj[m]
left the channel
08:35
WalterZimmermann
joined the channel
08:39
abeljj[m]
joined the channel
08:40
apurvanandan[m]
joined the channel
08:40
apurvanandan[m]
Hi everyone, will we have two meetings this week? On Monday and Tuesday?
08:42
elkos
joined the channel
08:42
mrohit[m]
joined the channel
08:42
a13b
joined the channel
08:42
cryteno[m]
joined the channel
08:42
blakec[m]
joined the channel
08:46
se6astian
apurvanandan[m]: Monday is the big meeting indeed, what meeting did you schedule for tuesday?
08:47
apurvanandan[m]
With Bertl, felix and florent
08:49
se6astian
right, then indeed you have two meetings :)
08:52
apurvanandan[m]
^^'
08:58
se6astian
gotta go
08:58
se6astian
changed nick to: se6astian|away
09:21
johnathan
left the channel
09:22
johnathan
joined the channel
09:27
Nira|away
changed nick to: Nira
09:27
johnathan
left the channel
10:08
Bertl_zZ
changed nick to: Bertl
10:08
Bertl
morning folks!
10:08
Bertl
apurvanandan[m]: at least two meetings ;-)
10:10
Bertl
aSobhy: you got all the schematics you need?
11:01
anuejn
se6astian|away: wget -r --no-parent https://files.niemo.de/axiom_pdfs/HARDWARE/AXIOM/
11:17
Nira
changed nick to: Nira|away
12:16
Nira|away
changed nick to: Nira
12:17
Bertl
apurvanandan[m]: you around?
12:32
BAndiT1983
changed nick to: BAndiT1983|away
12:51
Y_G
joined the channel
13:02
BAndiT1983|away
changed nick to: BAndiT1983
13:03
apurvanandan[m]
Yes , i have read the material you sent that day ( only the migen codes are left), currently sorting out the openocd thing for xup usb jtag, and after that will go to schematics
13:08
Bertl
great! we have a decision to make!
13:10
Bertl
I'm currently populating the USB plugin boards, and I have two MachXO2 available, the LCMXO2-1200 and the LCMXO2-2000
13:11
Bertl
they are basically pin compatible (the 2000 has more banks but on the same pins) https://www.latticesemi.com/view_document?document_id=43047
13:12
Bertl
they differ regarding the cells and memory though https://www.latticesemi.com/view_document?document_id=38834
13:14
Bertl
the question now is: do we want to have both (FT601 and FT602) with the 1200 or the 2000 or do we want one of each, and if so, which one :)
13:17
aSobhy
yeah a last question for the East MachXO2 should we use the second LVDS ?
13:19
Bertl
it would definitely make sense to use it and not have it sit there unused :)
13:19
aSobhy
for example clock sync. or it has another function
13:20
Bertl
we can decide on what to do with it ... it would be a good start to make a list of connections and protocol each routing fabric potentially has to handle
13:22
Bertl
note that both routing fabrics have a clock capable input connected to a zynq pin
13:23
Bertl
BANK13 SE_0 (RFW) and JX1 SE_0 (RFW)
13:24
Bertl
so it would be an option to use that to provide a synchronous clock (25-100 MHz) to the RFs
13:24
Bertl
which then can drive a PLL to generate higher phase related clock rates
13:25
Bertl
as we want bidirectional data transfer, the RFE could use one LVDS in each direction, while the RFW has to allow for direction changes
13:27
aSobhy
so they can be different protocols on the two sides ?
13:27
Bertl
at least the lower layer has to be somewhat different
13:28
Bertl
but it would also be possible to use a bidirectional protocol on both RFE LVDS and just double the bandwidth
13:29
Bertl
i.e. send half the bits over each LVDS connection
13:29
Bertl
but I presume that switching direction has more problems than dedicating an LVDS connection to each direction
13:30
Bertl
in any case, something which needs some more investigation
13:31
aSobhy
concerning to the packet protocol what kind of data I'll send ?
13:33
aSobhy
I have a lot of questions about it
13:36
Bertl
I can imagine ... basically we want to 'transport' data from various other protocols, ideally transparently, like I2C, SPI, JTAG, etc
13:37
Bertl
we do not know what protocols will be used/active, as this depends on the plugins, shields and otherwise available hardware
13:44
aSobhy
what in my mind is: the ZYNQ will send the MachXO2 a command to do (for example read from a sensor of address ... with that I2C ) and the MachXO2 will handle that command and return the value again to the ZYNQ
13:46
apurvanandan[m]
Hey Bertl isn't the 2000 better than 1200?
13:46
Nira
changed nick to: Nira|away
13:47
apurvanandan[m]
Is the 2000 costlier than 1200?
13:55
Bertl
both is true
13:55
Bertl
the 1200 costs about 6 EUR in quantities and the 2000 about 11 EUR each
13:55
BAndiT1983
changed nick to: BAndiT1983|away
13:56
BAndiT1983|away
changed nick to: BAndiT1983
14:01
apurvanandan[m]
Hmm,almost double, and what is the price estimate of USB module as whole?
14:12
Bertl
we don't have a price yet but about 60 EUR retail I guess
14:13
Bertl
but we can still decide to 'downgrade' the MachXO2 if we do not need the resources, the question is more for the current test/devel boards
14:13
Nira|away
changed nick to: Nira
14:13
Bertl
naturally we can go for the 2000 for those, but then we cannot test with the 1200 at all
14:13
Bertl
so we do not know if it actually works there
14:14
Bertl
if we decide for the 1200 for both (FT601 and FT602) then we have a problem if it isn't good/large enough :)
14:14
Bertl
so my gut tells me to use one of each as the FTDIs are quite similar
14:15
Bertl
leaves the question which one gets the 'larger' one :)
14:31
aSobhy
Bertl: Am I wrong ?
14:41
Bertl
no, for many protocols this will be the way it goes
14:41
Bertl
the catch is for example with GPIO pins
14:42
Bertl
(specifically for input pins which are like 'interrupts' to the system)
14:43
Bertl
polling those all the time might not be a good approach
14:44
Bertl
SPI and JTAG also shift in as many bits as they shift out, so a generic 'request-response' approach might kill the latency there
14:44
Bertl
(really depends on the data rate of course)
14:45
Bertl
off for now ... bbl
14:45
Bertl
changed nick to: Bertl_oO
16:15
illwieckz
left the channel
16:16
illwieckz
joined the channel
16:18
apurvanandan[m]
I think 2000 can go with ft601q and 1200 can go with ft602 as once we have a working module with 2000, we can try optimising the same for 1200 (stretch goal). I would choose the best bet when I don't know the limits.
16:26
Y_G
Hi BAndiT1983 , when I run scripts like zynq
16:27
Y_G
When I run scripts like the zynq_info.sh in axiom_beta build,I get errors like these : "/sys/devices/soc0/amba/.adc/iio/in_temp0_offset': No such file or directory"
16:28
Y_G
why that happens ?
16:31
BAndiT1983
changed nick to: BAndiT1983|away
16:38
vup
Y_G: are you running them on actual hardware or in qemu?
16:42
Bertl_oO
also what does 'bash -x zynq_info.sh' give as output (use a pastebin service or similar)
16:43
Bertl_oO
apurvanandan[m]: good argument, but wouldn't the FT602Q be more likely to need more resources because of color conversion or similar?
16:43
Nira
changed nick to: Nira|away
16:48
Nira|away
changed nick to: Nira
16:49
vup
but even in qemu it should work
16:49
vup
atleast is does for me
16:50
Bertl_oO
could be that the ADC is not emulated or (more likely) that the path is different
16:50
Bertl_oO
or that it is simply missing from the device tree
16:53
vup
i don't know how Y_G runs the image, but if they use https://github.com/apertus-open-source-cinema/axiom-beta-firmware
16:53
vup
it should work
16:53
vup
(even in qemu)
16:54
vup
you don't get any sensible values of course, but its emulated just fine
16:54
illwieckz
left the channel
16:55
illwieckz
joined the channel
16:56
vup
and on real hardware it works aswell (just tested it), so not sure what the problem is...
16:59
BAndiT1983|away
changed nick to: BAndiT1983
17:01
BAndiT1983
hi Y_G, see the questions already asked here, if you use emulated firmware or not
17:02
BAndiT1983
other than that, we could provide remote access to the beta, to be able to try live system, also there was a setup with live hdmi feed, e.g. for daemon testing
17:02
BAndiT1983
it worked rather good, i could see my changes applied immediately, e.g. from web UI
17:03
BAndiT1983
off for now
17:03
BAndiT1983
changed nick to: BAndiT1983|away
17:12
Y_G
left the channel
17:19
Y_G
joined the channel
17:21
Y_G
@vup I tried this command after building the image "docker-make.sh build-shell"
17:21
Y_G
I guess I should be using this "docker-make.sh qemu-shell"?
17:27
Y_G
@Bertl_oO : this is the output of "bash -x zynq_info.sh" "https://pastebin.com/19pZc7Kd"
17:32
vup
Yes you need to use qemu-shell
17:35
vup
build-shell is just a shell in the docker container used to build the actual image
17:40
Bertl_oO
Y_G: yeah, as you can see, the sysfs entries are missing and that is why the script fails
17:41
Bertl_oO
it might be a good improvement to the script to test for those entries first and report a meaningful error when they are missing
17:49
illwieckz_
joined the channel
17:53
illwieckz
left the channel
17:55
Y_G
Thanks ,I am running the "/usr/axiom/script/axiom-zynq-info.sh" which seems to give the correct output
17:56
Y_G
Bertl_oO:Yup something like that would be helpful,Will see if I can do something about it
17:56
vup
great
17:57
Y_G
Sorry for the trouble :)
17:57
Y_G
BAndiT1983 : yup That would help
17:59
illwieckz_
changed nick to: illwieckz
17:59
illwieckz
left the channel
18:00
illwieckz
joined the channel
18:06
se6astian|away
changed nick to: se6astian
19:17
Dev_
joined the channel
19:22
Dev_
Hello BAndiT1983|away : playsliders now appear in UI of OC ,
19:23
Dev_
we are using QtAV framework for handling video here. What was the problem u were mentioning for events
19:24
Dev_
I guess that's u have removed the code by commenting it
19:25
Dev_
--> https://github.com/apertus-open-source-cinema/opencine/blob/dev/Source/OCui/Controls/PlaybackSlider.cpp
19:30
Dev_
left the channel
19:31
RexOrCine|away
changed nick to: RexOrCine
20:21
Dev_
joined the channel
20:42
Dev_
left the channel
20:52
niemand
left the channel
21:11
se6astian
off to bed
21:11
se6astian
good night
21:11
se6astian
changed nick to: se6astian|away
21:53
RexOrCine
changed nick to: RexOrCine|away
22:19
Bertl_oO
off to bed now ... have a good one everyone!
22:19
Bertl_oO
changed nick to: Bertl_zZ
22:45
BAndiT1983|away
changed nick to: BAndiT1983
22:46
BAndiT1983
Dev_, QtAV is not really used and was only added for first tests, don't know which problem with events you mean
22:47
BAndiT1983
also QtAV wouldn't be of much help, as we have to handle special formats, like MLV, which are not supported that well, look at ffmpeg, there was some basic implementation of MLV decoder, but had also several problems
23:01
Nira
changed nick to: Nira|away
23:18
BAndiT1983
changed nick to: BAndiT1983|away