Current Server Time: 13:56 (Central Europe)

#apertus IRC Channel Logs

2021/07/19

Timezone: UTC


05:13
Bertl_oO
off to bed now ... have a good one everyone!
05:13
Bertl_oO
changed nick to: Bertl_zZ
08:28
se6astian
good day
11:04
anuejn
tpw_rules: we have the new shiny fatbitstream generation :)
11:04
anuejn
including super fast rebuild caching in case of only driver changes
11:49
mixfix41
joined the channel
11:58
danieel
left the channel
12:00
danieel
joined the channel
12:16
Bertl_zZ
changed nick to: Bertl
12:16
Bertl
morning folks!
12:44
se6astian
hello!
13:47
Dest321
changed nick to: Dest123
13:48
Dest123
Good Morning!
13:59
Bertl
off for now ... bbl
13:59
Bertl
changed nick to: Bertl_oO
16:52
aombk2
joined the channel
16:56
aombk
left the channel
17:00
Bertl_oO
changed nick to: Bertl
17:00
se6astian
MEETING TIME, who is here?
17:00
Bertl
is here ...
17:00
Dest123
is here
17:00
vnksnkr
is here
17:01
tpw_rules
is here
17:01
se6astian
Dest123: would you like to start?
17:01
Dest123
yeah sure
17:01
Dest123
so last week I had the channels ready for testing
17:02
Dest123
I integrated them with the existing hardware, where some problems occurred but I managed to solve them with Bertl
17:03
Dest123
the channels passed the training phase successfully, but I encountered a problem whilst capturing an image
17:03
vup
is here
17:03
Dest123
right now I'm working on using the sequencer trigger signals which hopefully would solve the problem
17:04
Bertl
note here: the channels are connected at the parallel interface and generate a 'fixed' pattern
17:04
Dest123
yes
17:05
aombk3
joined the channel
17:05
Dest123
that's it for me this week, thank you :)
17:05
se6astian
many thanks!
17:05
se6astian
vnksnkr go ahead
17:05
vnksnkr
Hi
17:06
vnksnkr
last week i didnt have much progress..as I was facing a few issues with the remote hardware
17:07
vnksnkr
I initially was using the driver developed last year to upload my bitstream on the MachXO2
17:07
vnksnkr
I was'nt able to decode and send back any commands from the fabric
17:08
vnksnkr
and as discussed earlier in the chat, the machXO2 was being reset, when the driver was being unloaded
17:08
vnksnkr
which I should have found out earlier
17:09
aombk2
left the channel
17:09
vnksnkr
so now I've shifted to using the python scripts to load the bitstream
17:10
vnksnkr
hopefully I can get it uploaded succesfully and finalize my gateware by this week
17:11
vnksnkr
that's it from my side
17:11
Bertl
did you work with bluez to get this sorted?
17:11
vnksnkr
yes there are 2 options right now to work with the jtag interface
17:12
Bertl
I think it would be good to remove the reset from the driver unload or at least make it optional (e.g. via driver option)
17:12
Bertl
so that you can use the driver to upload gateware and then free up the pic registers
17:13
vnksnkr
ok, another option bluez suggested was to use svf files to generated the commands since the driver supports openocd
17:13
Bertl
also bluez was using/testing a python script for burst upload to the MachXO2 before he wrote the driver, which should work with the bitstream IIRC
17:14
Bertl
okay, that would be the third option then, to use the openocd interface the driver provides to send/receive the jtag data
17:15
Bertl
okay, thanks!
17:16
se6astian
right, tpw_rules is next, please go ahead
17:16
tpw_rules
alright so i have good news, i got the prototype of the link training working for the cmv12k on the beta
17:17
Bertl
yay!
17:17
tpw_rules
it's not quite finished yet, i have some improvements to the training algorithm to make still and documentation to finish up. but i hope to address those today or tomorrow and get it merged
17:17
tpw_rules
then the next step is porting Bertl's pixel remapper from verilog and we should be able to see some images from the sensor soon :D
17:17
vup
*vhdl
17:17
tpw_rules
yes, sorry
17:18
Bertl
and it is not mine ;)
17:18
tpw_rules
but it does seem to work well on anuejn's beta. i want to try it on the others when they have sensors just to make sure it is robust
17:18
tpw_rules
also i heard anuejn fixed some complains i had with the pydriver compilation speed so work should be easier now. thank you!
17:19
tpw_rules
that should be it from me this week
17:19
Bertl
looking forward to the new gateware!
17:20
se6astian
many thanks
17:20
se6astian
anuejn are you there?
17:21
se6astian
BAndiT1983 shared some news but excused himself from the meeting
17:21
se6astian
he has been working on browser based remote "emulator"
17:21
se6astian
https://i2.paste.pics/82e0a2098b5f7ce278a7532cc469abe9.png
17:22
se6astian
this is related to https://lab.apertus.org/T1178
17:22
se6astian
eppisai: are you here?
17:22
se6astian
quick updates from me: I returned from vacation just 2 days ago so not much to report
17:23
se6astian
we might be able to collaborate with the technical university vienna on CNC manufacturing on camera related metal parts
17:23
se6astian
a meeting will happen probably at the end of august when manfred is back from tokio
17:23
eppisai
hi..i don't have much progress to report
17:23
eppisai
i am having some issues with remote hardware.. so trying to work that out
17:23
se6astian
right
17:24
se6astian
anyone else who wants to report?
17:24
Bertl
eppisai: what kind of issues?
17:24
eppisai
the mini module is not working..
17:24
eppisai
:(
17:24
eppisai
its not broken.. i am sure
17:25
se6astian
did you try it on another laptop as planned?
17:25
Bertl
did you switch the cables?
17:25
eppisai
i have switched the cables, tried on another laptop.. showed nothing..
17:26
se6astian
very weird
17:27
se6astian
right Bertl please share your closing words/progress with us?
17:27
Bertl
okay
17:27
Bertl
well, last week, some of our students touched the remote hardware the very first time ;)
17:28
Bertl
(probably related to the first evaluation ...)
17:28
Bertl
and some issues were found which resulted in me reworking one of the betas to make it work as intended
17:28
Bertl
and rearranging the order so that the beta-c is nearby the remote
17:29
Bertl
I also spent some time on further testing of the Axiom Beta PCBs and will hopefully get this week to actually assembling new Betas
17:29
tpw_rules
yay
17:30
se6astian
great!
17:30
vup
nice
17:30
Bertl
the video stream is still an open issue, I investigated youtube and twitch but both require a quite complicated setup and have huge delays
17:31
tpw_rules
what do you consider "huge"?
17:31
Bertl
5-15 seconds
17:31
se6astian
what about jitsi?
17:32
Bertl
maybe an option, haven't considered it yet
17:32
vup
hmm I have certainly managed to get the yt latency to go under that
17:32
vup
also what about just a basic nginx + rtmp plugin setup?
17:32
se6astian
yt can go down to slightly below 5s
17:33
Bertl
I'm open for all solutions, the best performance/ease of use I had so far was with a server at the university of vienna
17:33
Bertl
which basically got a fixed stream connect and then re-distributed the data on a per user base
17:34
tpw_rules
i think that time is probably fine?
17:34
Bertl
this way we had about a second delay and almost no load
17:34
Bertl
unfortunately we cannot use the server for our streaming purpose
17:35
Bertl
so, I'm open to all suggestions, as long as I do not have to waste too much time on it ;)
17:36
Bertl
that's it from my side for this week
17:36
se6astian
many thanks
17:36
se6astian
anyone else who wants to report/share anything?
17:41
vup
Bertl: do you know what software they are running on that server of the university vienna?
17:42
Bertl
I should be able to figure that out, it is likely some rtsp proxy
17:43
se6astian
ok, MEETING CONCLUDED, many thanks everyone!
17:44
Bertl
thanks for the moderation!
17:44
tpw_rules
thank you!
17:45
Dest123
thank you :)
18:43
Bertl
off for now ... bbl
18:43
Bertl
changed nick to: Bertl_oO
21:13
Bertl_oO
vup: rtsp-simple-server was the software used
21:14
vup
I see
21:15
vup
and you were streaming to that server using ffmpeg?
21:15
vup
what was used on the viewing / receiving side?
21:15
vup
rtsp aswell, or rtmp or hls?
21:15
Bertl_oO
yes, it was an rtsp stream with ffmpeg
21:17
vup
so ffmpeg on both sides?
21:48
Bertl_oO
client can use whatever app they want
21:49
Bertl_oO
was tested with vlc, mpv and ffplay IIRC
22:00
vup
sure, but the client can also affect the latency, if I understand the server right, it has the ability to "transcode" from rtsp to hls for example, which will probably add some latency compared to just listening to the rtsp stream
22:02
Bertl_oO
probably
22:49
vup
Bertl_oO: did the rtsp-simple-server work behind nat?
22:50
Bertl_oO
no idea
00:10
anuejn
so here is my report (a little late to the party):
00:10
anuejn
I did some rather large rework of the pydriver generation in naps
00:11
anuejn
now we produce zip files that can be executed via python and are self unpacking
00:11
anuejn
they behave much like the last iteration where we had self extracting shell scripts with a bunch of base64 in them
00:12
anuejn
this fixes some issues with to long arguments and is generally much more hackable after building the bitstream
00:12
anuejn
also I rewrote much of the infrastructure that _generates_ the logic and runs the build process
00:13
anuejn
we now have better caching (does not rebuild the bitstream if only driver code changed)
00:14
anuejn
also if we have cache hits, the system is able to find that out earlier resulting in a much smoother development experience :)
00:14
anuejn
thats it from my side
00:18
Dest123
left the channel
00:19
Dest123
joined the channel
00:34
vup
Nice