Current Server Time: 01:56 (Central Europe)

#apertus IRC Channel Logs

2021/01/04

Timezone: UTC


00:39
davidak[m]
left the channel
01:48
Bertl_oO
off to bed now ... have a good one everyone!
01:48
Bertl_oO
changed nick to: Bertl_zZ
02:18
anuejn
se6ast1an: could you create a collection of different raw frames from the beta somewhere
02:18
anuejn
I need one to tweak the parameters of the wavelet compressor
02:19
anuejn
best would be one image per scene as the compression scheme does not do inter frame compression
02:19
anuejn
off to bed now
02:19
anuejn
good night everyone :)
02:53
futarisIRCcloud
joined the channel
05:17
BAndiT1983|away
changed nick to: BAndiT1983
05:29
eppisai
joined the channel
06:14
RexOrCine
left the channel
06:15
RexOrCine1
joined the channel
06:17
RexOrCine1
left the channel
06:17
RexOrCine
joined the channel
06:59
eppisai_
joined the channel
07:01
eppisai
left the channel
07:01
eppisai_
changed nick to: eppisai
07:39
se6ast1an
anuejn: did you see https://wiki.apertus.org/index.php/AXIOM_Beta/Video ?
07:45
BAndiT1983
se6ast1an: but where are the RAW files? seeing only MP4, MOV and DNG
07:45
se6ast1an
Timelapse footage from AXIOM Belgium - Nextcloud | RAW12 and HD 1080 MP4.
07:46
se6ast1an
but we have more :)
07:46
se6ast1an
anuejn: see http://files.apertus.org/AXIOM-Beta/snapshots/
07:46
BAndiT1983
ah, now i see, thanks
07:47
BAndiT1983
this one is also interesting -> http://files.apertus.org/AXIOM-Beta/samples/reschart/
08:16
se6ast1an
hi eppisai!
08:16
eppisai
hello!
08:17
se6ast1an
I added a comment to https://lab.apertus.org/T1202 and would like to talk to you if you could take over that task as it also evolves around your checkbox icon
08:18
eppisai
yes, Ofcourse!
08:18
se6ast1an
great, please take a look
08:18
eppisai
I'll look into it. Thanks!
08:18
se6ast1an
if anything is unclear let me know then we can discuss it
08:19
se6ast1an
I used the home icon for testing https://lab.apertus.org/file/data/57jqrnw3ipuoc4o4o36e/PHID-FILE-qo5uf5lqryypqdwdrxt5/image.png
08:19
BAndiT1983
hi eppisai, please also check the task https://lab.apertus.org/T1193 before that, as the icon needs slight adjustment
08:20
eppisai
ok, I will see it!ðï¸
08:34
Bertl_zZ
changed nick to: Bertl
08:34
Bertl
morning folks!
08:34
BAndiT1983
hi
08:36
mumptai
joined the channel
08:36
se6ast1an
good day!
08:47
LordVan
joined the channel
09:38
eppisai
left the channel
10:37
anuejn
se6ast1an: thanks
11:35
eppisai
joined the channel
11:59
eppisai
left the channel
12:44
EmilJ
hi all
12:48
anuejn
hi
12:48
anuejn
just as a reference re earlier: I collected interesting frames here: inverse_multi_stage_wavelet2d(transformed, 3)
12:48
EmilJ
anuejn: I'm looking into hooking up an EDID reading setup from the HDMI DDC, I'm seeing some traces of bit-banged I2C in camera_usb3.py but not the software side
12:49
anuejn
whoops wrong clipboard
12:49
anuejn
https://files.niemo.de/axiom_sample_dng/
12:49
anuejn
EmilJ: the software side is the linux kernel
12:50
EmilJ
ohhh cool
12:50
anuejn
we load kernel modules with devicetree overlays
12:50
anuejn
see https://github.com/apertus-open-source-cinema/nmigen-gateware/blob/master/src/lib/peripherals/mmio_gpio.py and https://github.com/apertus-open-source-cinema/nmigen-gateware/blob/master/src/lib/peripherals/i2c/bitbang_i2c.py
12:51
anuejn
the overlay generation is - eh - a bit ad hoc ;)
12:51
anuejn
basically we load a gpio driver and then plug the i2c driver into that
13:03
anuejn
for the overlays to work you need some things
13:03
anuejn
we have a patched kernel (https://github.com/apertus-open-source-cinema/axiom-firmware/blob/master/patches/linux/overlay.patch)
13:27
EmilJ
thanks, I'll try to replicate that
13:27
EmilJ
oh no, a kernel patch
13:29
EmilJ
well the pynq has its own machinery, I'll see what I can do
13:31
xthenode
joined the channel
13:33
xthenode
happy Monday...
13:34
anuejn
EmilJ: you can try to just use the axiom-firmware images
13:34
anuejn
maybe that is easier to get started with
13:34
xthenode
what cad system is used for axiom hardware?
13:35
xthenode
camera body etc...
13:37
BAndiT1983
onshape
13:56
xthenode
thanks, ill check it out...
14:11
LordVan
left the channel
14:23
EmilJ
hmmm, can't figure out what framebuffer *driver* does axiom-firmware use
14:24
EmilJ
my devicetree is set, the kernel config of pynq definitely is configured for framebuffer work
14:24
EmilJ
but I don't get `/dev/fb0`
14:26
Bertl
anything in dmesg?
14:29
xthenode
left the channel
14:37
vup2
is uses the simple-framebuffer driver
14:41
vup2
EmilJ: how is your devicetree looking?
14:47
eppisai
joined the channel
14:54
EmilJ
Bertl: that was a good idea, apparently it is refusing to create the overlay. The error I'm getting (create_overlay: Failed to create overlay (err=-22)) typically is due to problems with devicetree symbols
14:55
EmilJ
either caused by the overlay lacking symbols, or the device tree lacking them
14:55
EmilJ
I'm in neither of those situations though
14:55
EmilJ
yeah I think it's time to switch to axiom-firmware
14:57
vup2
EmilJ: you need to compile your devicetree with the '-@' option to get symbols
14:57
vup2
both the overlay and the one loaded at boot time
14:58
EmilJ
I did that
14:59
vup2
that is ... curious
14:59
EmilJ
well, the overlay, at least, but I verified the `__symbols__` directory exists in the device tree directory
14:59
vup2
hmm
14:59
vup2
ahh
15:00
vup2
did you create the overlay yourself or did you use the one created by the gateware?
15:00
EmilJ
I used the emitted overlay
15:00
vup2
I see
15:01
vup2
do you have the source for your devicetree available?
15:01
EmilJ
well, yes, split into these .dtsi source fiels
15:02
EmilJ
it's not super transparent since xilinx assumes you're using their tools and abstracting everything, probably
15:02
vup2
because the overlay created by the gateware wants a part named `amba`
15:02
EmilJ
I do have that
15:02
vup2
maybe its not called amba for you
15:02
vup2
hmm
15:04
vup2
maybe its time to use axiom-firmware :P
15:26
EmilJ
Welp, that didn't boot
15:26
EmilJ
no UART either
15:27
vup2
well what did you do?
15:27
EmilJ
flashed a release for the micro onto a microSD card using um
15:29
EmilJ
gnome-disks
15:30
vup2
well
15:32
vup2
you probably need to use a proper u-boot and a proper devicetree
15:33
vup2
ie you need a pnyq folder that contains files similar to these: https://github.com/apertus-open-source-cinema/axiom-firmware/tree/master/boot/axiom-micro
15:33
vup2
(fsbl.elf is not needed anymore, bitstream.bit is not needed aswell)
15:34
vup2
if u-boot does not already support your board you need to add support for it using a patch aswell: https://github.com/apertus-open-source-cinema/axiom-firmware/blob/master/patches/u-boot/z_turn_lite_support.patch
15:34
vup2
the ps7_init_gpl.c thing can be extracted from vivado if you create a fsbl project targeting your board
15:55
Shohei
joined the channel
16:00
se6ast1an
MEETING TIM!
16:00
se6ast1an
who is here?
16:00
metal_dent[m]
is present
16:00
se6ast1an
*TIME :)
16:00
bluez
* bluez is here
16:00
Shohei
*Shohei is her
16:00
Shohei
e
16:00
se6ast1an
my keyboard tends to eat letters or double them recently...
16:01
se6ast1an
great, metal_dent[m] would you like to start the reporting?
16:01
metal_dent[m]
yeah sure!
16:01
metal_dent[m]
last week i worked on the image button PR (haven't pushed the changes yet)
16:02
metal_dent[m]
we also discussed about the desaturation shader task (T1215)
16:03
metal_dent[m]
today i was going through the code and learning more about FBO and shaders
16:03
anuejn
is here
16:03
vup2
is here aswell :)
16:03
Bertl
too ...
16:04
metal_dent[m]
other work was related to the USB code but i haven't tested that yet so waiting for the remote to come ':D
16:04
metal_dent[m]
i think that's it from me!
16:04
se6ast1an
great metal_dent[m], many thanks
16:05
se6ast1an
lets coordinate about the remaining imagebutton steps as I also started to work again on that area
16:05
metal_dent[m]
yes, sure
16:05
se6ast1an
bluez: your turn
16:05
bluez
yep!
16:06
bluez
so last week... as final task of my 'vhdl training', I translated an existing implementation of axi lite slave in verilog to vhdl
16:07
bluez
https://github.com/Swaraj1998/axi-lite-slave
16:07
bluez
code can be found here ^
16:08
bluez
i used the axi verification ip for verification using simple reads and writes
16:08
bluez
hit quite a few bumps.. mostly because of sparce documentation about some parts of vivado and all.. but did learn a lot
16:09
Bertl
would be nice to have the full project with the verification IP as well
16:09
bluez
i'll now run it in remote beta and do furter tests
16:09
Bertl
(online I mean :)
16:09
bluez
yep yep sure
16:10
bluez
i just did the verification today.. will add the tcl part on the repo so it can be reproduced
16:10
Bertl
perfect!
16:10
bluez
thats all from me i guess!
16:11
bluez
:)
16:11
se6ast1an
many thanks bluez!
16:11
se6ast1an
Shohei: your turn!
16:11
Shohei
Thank you :) I bought a MicroZed board, and tried I tried serial communication from my Linux laptop, and read this link (https://wiki.apertus.org/index.php/AXIOM_Beta/Enclosures) up to around "5."
16:11
se6ast1an
great
16:11
Shohei
I will do my best to catch up.
16:12
se6ast1an
point 6 is were it becomes really intersting :)
16:12
Shohei
Thank you! I will read it carefully : )
16:12
se6ast1an
many thanks for the report!
16:12
se6ast1an
vup2: your turn!
16:13
vup2
Ok sure, first of all, I did a quick fix for the axiom-firmware CI, for some reason it did not like the opennic dns server anymore, so I switched the dns server and the CI build of the firmware are working again :)
16:13
se6ast1an
nice!
16:14
vup2
Now furthermore, anuejn and I have been working on the wavelet compression some more. We have finally gotten lossless forward and backward transformation to work!
16:14
vup2
(in the python implementation)
16:14
vup2
you can find that here: https://github.com/apertus-open-source-cinema/nmigen-gateware/blob/3540c01/src/lib/video/wavelet/py_wavelet.py
16:15
vup2
now we are starting to experiment with different quantization parameters for the different wavelet parts to find a sweet spot of image size and image quality
16:16
vup2
If there are no questions, thats it from the this week
16:17
se6ast1an
what is the issue with image size vs speed vs quality ?
16:17
se6ast1an
how does it affect the process I mean
16:17
vup2
so the compression works by throwing away some bits of the high frequency components of the image
16:18
vup2
throwing away more of them makes the image compress better
16:18
vup2
but obviously lowers the image quality
16:19
se6ast1an
but it does not affect compression speed if I understood correctly?
16:19
anuejn
yup it doesnt
16:19
se6ast1an
image size would I assume (number of total pixels to compress)
16:20
anuejn
that does affect the runtime obviously
16:20
anuejn
almost linear
16:20
se6ast1an
would an FPGA implementation be able to work with arbitraray resolutions or would that make it hard to parallelize the process?
16:20
BAndiT1983
changed nick to: BAndiT1983|away
16:21
anuejn
the paralelization is not a big problem there
16:21
anuejn
(the algorithm is very well paralelizable)
16:22
anuejn
(currently there is no paralelization in the fpga implementation)
16:22
anuejn
the main problem with arbitrary resolutions is that you cant allocate buffers dynamically in an fpga
16:22
anuejn
so we can set an upper bound during synthesis and then support everythnig that is lower than that
16:23
anuejn
however dynamic resolutions are also not yet implemented
16:23
se6ast1an
great, that should do, as the image sensor max resolution is "static" but reading smaller windows would increase FPS
16:23
se6ast1an
but less pixels of a smaller window would then also compress faster
16:24
anuejn
yup
16:24
se6ast1an
very nice
16:24
se6ast1an
are the next steps already the step onto the FPGA?
16:24
anuejn
hm... not yet really
16:25
anuejn
the next step would probably be to find good parameters for the quantization and good codebooks for rle and huffman
16:25
se6ast1an
codebooks?
16:25
vup2
tables used for the huffman compression
16:26
vup2
we need to figure out which values occour often and which ones don't
16:26
se6ast1an
right
16:26
se6ast1an
so you need lots of image samples I assume?
16:26
vup2
yes
16:26
anuejn
yup that is what i started with earlier this day
16:26
se6ast1an
should we seek to collect more or are the ones on the server sufficient?
16:27
vup2
those are probably sufficient for now
16:27
se6ast1an
great
16:27
se6ast1an
you need samples with high image frequencies in particular I assume (pictures of fine details)?
16:27
anuejn
but if there is anything you definitely dont want to compress badly, send it now ;)
16:28
se6ast1an
fine pattern, textiles for example would be interesting then
16:28
vup2
yep
16:28
vup2
that would be good
16:28
se6ast1an
dont have a beta currently with me but will keep it in mind
16:28
se6ast1an
many thanks for the report! very exciting!
16:28
vup2
(we were using a image that had lower optical resolution that the image resolution and it showed :)
16:29
se6ast1an
please share before/after images if you collect them
16:29
vup2
sure
16:29
se6ast1an
would be interesting to see
16:30
se6ast1an
with acompanying quality "ratio"
16:30
se6ast1an
ok quick updates from me:
16:30
se6ast1an
the nextpcb order has advanced a few steps further
16:30
se6ast1an
and again at least one step back
16:31
se6ast1an
we had to upgrade the copper thickness as they quote the thcikness not per layer but per top and bottom layers combined
16:31
se6ast1an
the stackup looks good and we gave green light
16:31
se6ast1an
today we received again "production files" for verification
16:31
se6ast1an
which contained a completely different stackup again...
16:31
se6ast1an
maybe just a mix up with another project...
16:32
se6ast1an
vup2: tinkered with a wifi usb dongle driver on the beta until we concluded that this particular model is not going to work
16:32
se6ast1an
https://wiki.apertus.org/index.php/AXIOM_Beta/Manual#WiFi_Access_Point_Setup
16:33
se6ast1an
Edimax EW-7811UN Realtek RTL8188CUS
16:33
se6ast1an
I started diving into the AXIOM Remote code again
16:33
se6ast1an
and updated the documentation with lots of images and examples of the GUI so far: https://github.com/apertus-open-source-cinema/AXIOM-Remote/blob/dev/Firmware/README.md
16:33
se6ast1an
explaining the terms and classes better
16:34
se6ast1an
some fixes and improvements also pushed
16:34
se6ast1an
and BAndiT1983 merged the visualizer adjustments upstream
16:34
se6ast1an
so we now have the great looking blender render of the actual remote with illuminated button in the visualizer now
16:35
Bertl
yay!
16:35
se6ast1an
for the ESD foam we want to ship hardware in there is slight progress
16:35
se6ast1an
two chinese companies have agreed to ship free samples if we cover shipping
16:36
se6ast1an
those foams on paper would fit our requirements and are slightly and the other supplier significantly cheaper than what we researched before
16:36
se6ast1an
samples will tell if they are of useable quality
16:36
se6ast1an
$0.95$/dm³
16:36
se6ast1an
and $0.39$/dm³
16:37
se6ast1an
vs â¬2.18â¬/dm³ that we got quoted before in Europe
16:37
se6ast1an
shipping still needs to be calculated of course
16:37
se6ast1an
for any volume
16:38
se6ast1an
next steps now that Tele is back from vacation are to prepare anything left before we can start the assembly run
16:38
se6ast1an
ordering solder paste
16:38
se6ast1an
discussion who buys which components from the bom, etc.
16:39
se6ast1an
pick and place files, etc
16:39
se6ast1an
I guess thats it from my side
16:39
se6ast1an
Bertl: your closing words? :)
16:39
Bertl
thanks!
16:40
Bertl
well, besides the usual stuff (helping out here and there) I mostly spent my time with celebrating the new year, and after that, recovering from the celebrations :)
16:40
se6ast1an
very intense!
16:41
Bertl
yes, indeed, as every year :)
16:42
Bertl
so nothing really to report from my side this week
16:42
se6ast1an
right, what are the next steps for you?
16:43
Bertl
next steps are to get the SATA plugin working so we can do some tests there
16:43
Bertl
as well as further work on the power board firmware
16:44
se6ast1an
great!
16:44
Bertl
if there is some time left, I'd like to spend it on the HDMI digitizer
16:44
se6ast1an
anything else for todays meeting, or does anyone else have topics or things to discuss/share?
16:45
eppisai
left the channel
16:47
se6ast1an
eppisai fixed the checkbox icon on the remote just today for example: https://lab.apertus.org/T1193
16:47
se6ast1an
right then
16:47
eppisai
joined the channel
16:47
se6ast1an
many thanks everyone for attending/sharing
16:47
se6ast1an
lets see what 2021 will bring for the project
16:47
se6ast1an
MEETING CONCLUDED!
16:50
EmilJ
since it seems like the pynq setup is a pain to extract information from, since it's all linked together with petalinux/yocto config files, I'm delving deeper into the devicetree overlay I'm trying to load. There isn't really a good reason for it not to work
16:51
vup2
well to me it all seems like the original devicetree does not have symbols, or does not have a amba symbol
16:52
Bertl
the overlays need to match the device tree labels
16:52
vup2
yeah
16:56
Shohei
left the channel
17:03
EmilJ
the original devicetree does have `__symbol__` nodes but for some reason it acts like it doesn't
17:03
EmilJ
compiling without symbols and adding it stops the dmesg error from appearing
17:04
EmilJ
I think I should implement this
17:04
EmilJ
> Using the non-phandle based target method allows one to use a base DT which does not contain a __symbols__ node
17:05
EmilJ
right now I got `target = <&amba>;` and it resolves into 0xFFFFFFFF *exactly* the same as in the raspberry pi docs for dt: https://www.raspberrypi.org/documentation/configuration/device-tree.md
17:17
EmilJ
I arrived at the conclusion that simplefb is outright not shipped with the pynq image
17:17
EmilJ
judging from the existence of this repo https://github.com/ciniml/pynqz1fb
17:20
vup2
hmm that repo is something else
17:20
vup2
can you get the kernel config from /proc/config.gz ?
17:37
EmilJ
https://gitlab.com/-/snippets/2056747
17:46
BAndiT1983|away
changed nick to: BAndiT1983
18:06
Bertl
off for now ... bbl
18:06
Bertl
changed nick to: Bertl_oO
18:30
vup2
EmilJ: hmm yeah, the simplefb module seems to be disabled
18:30
vup2
can you get the linux source tree that pynq uses?
18:44
eppisai
left the channel
18:46
EmilJ
I got the correct release of the source tree and am figuring out how to bulid a single in-tree module
18:50
vup2
I think `make M=drivers/video/fbdev/simplefb` should work
18:59
EmilJ
that would require simplefb to have its own Makefile
18:59
EmilJ
I guess I'll find what Makefile builds it
18:59
EmilJ
and just build all in that Makefile
19:03
EmilJ
it builds the .o but doesn't link it into .ko, that's frustrating
19:16
EmilJ
oh, I set the config to y instead of m for module, that's on me :D
21:01
BAndiT1983
changed nick to: BAndiT1983|away