Current Server Time: 07:29 (Central Europe)

#apertus IRC Channel Logs

2021/08/09

Timezone: UTC


03:39
Dest123
left the channel
03:39
Dest123
joined the channel
04:47
Bertl
off to bed now ... have a good one everyone!
04:47
Bertl
changed nick to: Bertl_zZ
04:56
illwieckz
left the channel
05:04
illwieckz
joined the channel
06:01
eppisai
left the channel
06:01
se6astian
left the channel
06:01
bluez
left the channel
06:01
BAndiT1983
left the channel
06:01
eppisai_
joined the channel
06:01
bluez_
joined the channel
06:01
se6astian_
joined the channel
06:03
BAndiT1983
joined the channel
06:45
Dest123
left the channel
06:55
Dest123
joined the channel
07:30
fredy
joined the channel
08:38
Dest123
left the channel
08:54
Dest123
joined the channel
13:39
Bertl_zZ
changed nick to: Bertl
13:39
Bertl
morning folks!
15:30
Dest321
joined the channel
15:32
Dest123
left the channel
16:55
BAndiT1983
meeting in 5 minutes
16:57
eppisai_
is here!
16:58
tpw_rules
is here
16:59
vnksnkr
is here
17:00
BAndiT1983
MEETING TIME!
17:00
BAndiT1983
who else is available?
17:00
BAndiT1983
vup? anuejn? Bertl?
17:00
anuejn
me is here
17:00
vup
is here
17:01
BAndiT1983
ah, great, lets start in same order
17:01
BAndiT1983
eppisai_: you are
17:01
eppisai_
Hi..!
17:02
eppisai_
Since, last week my remote hardware is completely working now, was able to flash the PIC16s.. after so long, now everything works like magic.. :D
17:02
eppisai_
I had started documenting the process of flashing firmware on PIC16s and PIC32 on remote.. it's mostly finished, I'll finish other modifications in the same that might be needed..
17:02
eppisai_
https://wiki.apertus.org/index.php/AXIOM_Remote/Development
17:02
eppisai_
Because of the help from BAndiT and bertl, I was able to understand how I can use timer to time any block of code or get the fps on remote,
17:03
eppisai_
For timing functions, I'll be using delta's (difference between values of count register) but for fps I am still using interupt..(which gets call when count == compare), I'll try to use difference here also, but haven't yet figured how I can generate core timer interupts that way..
17:03
eppisai_
I was also working little bit on transition task, I had started writing down other transition animations of the remote, so far I have written push-up ;), push-left, and push-right.. but I was struggling a bit designing push-up and push-right.. I'll work on it..
17:03
eppisai_
https://photos.app.goo.gl/cG5ELGdS9SHqpe6b6
17:04
eppisai_
Above is 42 second long video (with 5 second of me struggling a bit to navigate through menu using knob :), which I use to mostly do in visualizer) of current progress on AXIOM remote, that number on the right side is fps, buttons and everything is working.
17:04
eppisai_
Keythings - screen is not being modified while transition is taking place, I am getting 10-12 fps with or without transition
17:04
eppisai_
https://github.com/eppisai/AXIOM-Remote/tree/transitiontask
17:04
eppisai_
https://github.com/eppisai/AXIOM-Remote/tree/core-timer
17:04
BAndiT1983
have general trouble to play videos on google page, probably ad blocker
17:05
eppisai_
Oh.. I'll share drive link next time.. probably something with Google photos
17:05
eppisai_
Above is code for the same.. ( transition animation, and core timer)
17:06
eppisai_
That was my last week... That's it for me..
17:06
BAndiT1983
alright, many thanks
17:06
BAndiT1983
tpw_rules: you're next
17:06
tpw_rules
alright
17:07
tpw_rules
so last week we made a bunch of progress
17:07
tpw_rules
i finished the work to receive and validate the beta sensor test pattern which proves the PHY works
17:07
anuejn
yay
17:07
tpw_rules
vup, anuejn, and i also collaborated on various infrastructure improvements which should make future things nicer
17:08
tpw_rules
i am working on finishing up a version of the sensor code which receives the sensor pattern to DRAM and should have that ready to go today or tomorrow
17:08
tpw_rules
next, and really final, step is the pixel remapper to order the camera images correctly
17:08
tpw_rules
then a bit of work to do HDMI output and i think my project should be complete!@
17:09
anuejn
really nice work :)
17:09
tpw_rules
thank you
17:09
vup
yep, nice work!
17:09
BAndiT1983
sounds like a great progress, keep it up!
17:10
BAndiT1983
tpw_rules: anything to add?
17:10
tpw_rules
no i think that's it from me
17:10
BAndiT1983
many thanks for the report
17:10
BAndiT1983
vnksnkr: your turn
17:11
vnksnkr
Hi
17:11
vnksnkr
So last week I was spending most of my time with the remote hardware
17:11
Bertl
is here ...
17:12
vnksnkr
Ran a few tests and I'm now able to generate signals from the beta via JTAG for the different GPIOs connected to the shield
17:13
vnksnkr
However I tested this only on the debug shield on the east side where the LEDs
17:14
vnksnkr
were blinking in the expected pattern
17:14
vnksnkr
There were a few issues with testing it on the remote
17:16
vnksnkr
Since the version of the remote remote is different from when the PIC16 codes were written..some changes had to be made
17:17
vnksnkr
However still there seems to be an issue with I2C
17:19
vnksnkr
So Bertl will be connecting a logic analyzer soon to find out what's happening there
17:20
vnksnkr
Apart from that been cleaning up the code here and there
17:20
vnksnkr
That's it from my side this week
17:21
BAndiT1983
please report from time to time in gsoc channel, how the I2C investigation goes on, would like to know the progress, as EF version was not tested that often yet
17:21
BAndiT1983
many thanks!
17:21
BAndiT1983
anuejn: please go on
17:21
vnksnkr
BAndiT1983: will do
17:21
Bertl
I'd say it wasn't tested at all before ;)
17:22
BAndiT1983
will be in Vienna soon, maybe we can discuss beforehand if some small version can be done or how we want to proceed even, if pic32 EF will still be used etc.
17:22
anuejn
This week I colaborated a bit with tpw_rules and vup on the "various improvements" for naps
17:23
anuejn
mainly some speedup and correctness improvements for the pydriver
17:23
anuejn
on the narui (new axiom recorder ui; my gsoc project) side I was able to draw the first debayered picture
17:24
anuejn
that means that the boundry between the existing image processing pipeline and the developed gui library (atleast kinda) works
17:25
anuejn
I also fixed a rather nasty delta-evaluation related bug in narui and improved input latency in debug builds
17:25
anuejn
(and also in release builds)
17:26
anuejn
currently I am hunting for a rather nasty vulkan api usage bug together with vup
17:26
anuejn
(that prevents zero-copy displaying in narui to work)
17:26
anuejn
thats it from my side for this week
17:27
BAndiT1983
many thanks!
17:27
vup
very nice work!
17:27
BAndiT1983
alright, now we want screenshots ;)
17:27
BAndiT1983
vup: please continue
17:28
vup
ok, nothing major from me this week, as already mentioned, I mostly worked together with anuejn and tpw_rules on a few different topics
17:28
vup
this includes some performance improvements when accessing fpga registers from the pydriver framework on the zynq
17:29
vup
reworking the remote (ssh) programming capabilities of the naps framework
17:29
vup
and some other usability and performance improvements in naps
17:29
vup
thats it from me
17:30
BAndiT1983
many thanks
17:31
anuejn
thanks for the good support :)
17:32
BAndiT1983
also not much to report here, am a bit obstructed by work, so just small fixes done for the 3d visualiser and started to look into ICSP, package delivery failed today and proper cables for JTAG have not arrived, so replacement has to be found, but in general next steps are: implementation of communication on the remote, with focus on ICSP
17:32
vup
anuejn: you're welcome :)
17:32
BAndiT1983
Bertl: please finish us
17:32
Bertl
well, as vnksnkr already hinted, I spent some quality time on the remote and the remote control shield this week
17:33
Bertl
to my surprise, it seems that nobody has ever programmed the PIC16s there correctly before ...
17:33
BAndiT1983
what do you mean?
17:34
Bertl
well, there are some hardware changes between v0.9 and v0.13+ which make it impossible to program the PIC16s with the old tools
17:35
BAndiT1983
as you have the only board there, that's natural that nobody has tried to adjust the tools
17:35
BAndiT1983
*the only EF board
17:35
Bertl
it has been in the remote setup for over two years now
17:35
Bertl
so I would have expected somebody to 'discover' the problem before ;)
17:36
Bertl
anyway, I updated the tools and now programming works as expected
17:36
BAndiT1983
we can count how many people had access :D
17:36
Bertl
at least five according to the zbox
17:36
BAndiT1983
2-3 at max, leaving myself out, as i like local development and often it's tedious to try things on remote systems, where i can't even fix things if something goes wrong
17:37
Bertl
we also fixed a few issues with the remote shield and the connection to the remote
17:37
Bertl
and currently we are getting some unexpected feedback from the KMs which hints at some I2C problems
17:37
BAndiT1983
what is unexpected feedback?
17:38
Bertl
we get key presses and rotary encoder movements reported from the remote even when there is nothing happening
17:38
Bertl
they follow a certain pattern which doesn't look like valid data
17:40
Bertl
I also cleaned up the demo (code example) for KM access and I2C communication so that it will work with both Remote versions
17:40
BAndiT1983
hm, had also trouble with UART pull-up and genuine pickit3 not flashing from pic32prog, can it be that something is off or missing, to minimize cross-talk or whatever causes interference?
17:40
Bertl
the I2C connection is on the PCB, so there is little to none cross talk or similar
17:41
BAndiT1983
just saying, as pic32prog had problems to contact the board through pickit, but works fine (if cable has no loose contact) with FT4232H
17:41
Bertl
we have a PICkit2 here (or a clone, I do not remember which) and it seems to work just fine with all the code I tested
17:42
BAndiT1983
*have tried both, my pk3 clone and original one, both show same behaviour
17:42
Bertl
the serial console is on the FT2232 and that works fine as well, we are using 1MBaud at the moment without any issues
17:43
Bertl
so, also as vnksnkr hinted, the next steps will be analyzing the I2C traffic to ensure there is nothing weird going on there
17:43
Bertl
and if that is true, we probably have to revisit the KM code base and see if there is a weird bug
17:44
BAndiT1983
so you left i2c connection and added UART? not that some pin change (in the layout) is the cause
17:44
Bertl
but my money is still on the PIC32 side as the software was not really updated over years now and the compiler might have changed things a little
17:45
Bertl
BAndiT1983: not sure what you are talking about
17:46
Bertl
anyway, that's it from my side for this week
17:46
Bertl
I hope we can resolve the issues in the next few days
17:46
BAndiT1983
was just wondering, as you've added UART from pic16 to pic32, if the pin setup has changed, or if I2C is also there
17:46
Bertl
we are currently doing I2C between PIC32 and KMs
17:46
BAndiT1983
alright, many thanks everyone! keeü up the good work!
17:46
BAndiT1983
meeting concluded
17:46
Bertl
the pins in the v0.13+ remote are capable for UART as well
17:47
Bertl
but I do not plan to spend time on that right now
17:49
BAndiT1983
was just asking, to cross-chekc, if there is something problematic in the layout, haven't looked at the 0.13+ schematics and pin layout there thoroughly yet
18:12
Dest321
changed nick to: Dest123
18:20
Dest123
Sorry couldn't make it on time
18:20
Dest123
this week I was working on connecting the logic analyzer and testing my control channel data on it
18:22
Dest123
me and Bertl, we connected the analyzer and identified, sorted 8 channel pins
18:23
Dest123
7 of them are working fine but channel 4 doesn't seem to transfer any data
18:23
Dest123
the ports are constrained in my repo if anyone wants to reuse them
18:24
Dest123
https://github.com/Destfolk/CMV12000-Simulation/blob/test1/analyzer_test/pin_analyzer_north.xdc
18:24
Dest123
back at the main issue at hand
18:26
Dest123
even though the sequencer not receiving the data, and the control signals seem to be fine
18:27
Dest123
so for the next thing I'll do, I'll disable the live view and see, trigger a single frame capture
18:27
Dest123
and observe the sequencer signals
18:27
Dest123
that's it for me :)
18:33
BAndiT1983
many thanks, Dest123!
18:45
Dest321
joined the channel
18:46
Dest123
left the channel
18:47
Dest321
changed nick to: Dest123
18:57
Bertl
off for now ... bbl
18:58
Bertl
changed nick to: Bertl_oO
23:24
fredy
left the channel