Current Server Time: 23:41 (Central Europe)

#apertus IRC Channel Logs

2020/08/31

Timezone: UTC


00:37
Dest123
left the channel
05:10
BAndiT1983|away
changed nick to: BAndiT1983
07:30
illwieckz
left the channel
08:00
Triffid_Hunter
left the channel
08:00
ArunM
left the channel
08:04
danieeel
joined the channel
08:04
Bertl_zZ
changed nick to: Bertl
08:05
Bertl
morning folks!
08:05
Triffid_Hunter
joined the channel
08:05
ArunM
joined the channel
08:09
danieel
left the channel
08:58
danieeel
changed nick to: danieel
09:01
theresa[m]
left the channel
11:36
BAndiT1983
changed nick to: BAndiT1983|away
11:59
BAndiT1983|away
changed nick to: BAndiT1983
13:02
intracube
left the channel
13:13
intracube
joined the channel
13:30
illwieckz
joined the channel
14:32
RexOrManual
joined the channel
16:00
se6ast1an_
MEETING TIME
16:00
se6ast1an_
hello everyone
16:00
se6ast1an_
please pm me now as usual to report
16:01
Bertl
we probably should have rescheduled the meeting today :)
16:02
Bertl
or at least scheduled it two hours later ...
16:02
se6ast1an_
ah, why is that?
16:03
Bertl
August 24 - 31 18:00 UTC Students submit their final work product
16:03
se6ast1an_
ah, yes just read the gsoc timeline
16:03
se6ast1an_
good, lets meet in 2 hours
16:03
Bertl
appreciated!
16:04
se6ast1an_
then I am sure everyone is eager to share their end reports!
16:06
Bertl
definitely
16:48
RexOrManual
left the channel
17:00
preetimenghwani[
Hello Everyone, I wont be able to attend todays meeting so I am repoting right now
17:01
preetimenghwani[
This week we tested the patch of two writers on full Beta, it worked fine
17:02
preetimenghwani[
I have also made the patch doubt throughput we are currently testing it on full Beta
17:03
preetimenghwani[
I also implemented a wrapper for pixel remapper will test it soon
17:04
preetimenghwani[
I removed the timing erros and now we are able meet all the timing constraints
17:05
preetimenghwani[
Here is my GSoC final report: : https://drive.google.com/file/d/1nMD4Cyxck2vTtg9ObFisTuhURBMLQoe-/view?usp=sharing
17:05
preetimenghwani[
Thanks!
17:06
Bertl
thanks you!
17:22
se6ast1an_
left the channel
17:22
se6ast1an
joined the channel
17:59
RexOrManual
joined the channel
18:01
Bertl
meeting time?
18:01
se6ast1an
MEETING TIME
18:01
se6ast1an
who wants to report after just having pressed the final submit button ? :)
18:02
se6ast1an
metal_dent[m]: please go ahead
18:02
metal_dent[m]
hi everyone!
18:02
Bertl
how was pressing the 'final submit button'?
18:03
metal_dent[m]
was a little nervous ':D
18:04
RexOrManual
left the channel
18:04
metal_dent[m]
last week i worked mostly to properly read the data from the selected key mangers (west or east) using the python script, i added SelectChip() and GetKMData() methods in the firmware
18:05
metal_dent[m]
this uses the existing ICSProgrammer class methods to select km, enter lvp and retrieve the data
18:07
metal_dent[m]
after it worked nicely, i formatted the hex file data using the intelhex library in the python script (but i did some unnecessary operations which i discussed with BAndiT1983 )
18:08
metal_dent[m]
due to the lack of time, i couldn't successfully implement the writing process (did do some testing which did not work properly)
18:09
metal_dent[m]
here is my final report -> https://github.com/MetalDent/GSoC-Final-Report/blob/master/GSoC_Final_Report_MetalDent.pdf
18:09
metal_dent[m]
the code link is also present there
18:11
metal_dent[m]
that's all from my side! thank you and really enjoyed the gsoc period and learnt many useful stuff including the good coding styles (though still need to improve there)
18:12
se6ast1an
great to hear, many thanks!
18:12
Bertl
glad you enjoyed it and looking forward to see you around after GSoC 2020
18:12
se6ast1an
apoorva_arora & bluez_[m] you around?
18:12
se6ast1an
we would love to hear your final report!
18:12
metal_dent[m]
yes of course!
18:13
bluez_[m]
yep I am here
18:13
se6ast1an
great, please go aheag bluez_[m]!
18:14
bluez_[m]
thanks! so last week I finally added support for our driver in OpenOCD... the patch can be found in my repo
18:14
bluez_[m]
https://github.com/Swaraj1998/axiom-beta-rfdev
18:14
bluez_[m]
the report is there as well
18:15
bluez_[m]
after some testing I was finally able to flash the FPGAs with SVF replays!!
18:16
bluez_[m]
The last week was very tightly packed...did a lot of changes... many many bugs
18:16
bluez_[m]
finally wrapped up the code and cleaned up as much as I could
18:17
bluez_[m]
I would say the project is in a way complete... but it definitely needs a lot of improvements in terms of code design, performance etc.
18:17
bluez_[m]
I did as much as i could...the rest I will be continuing after gsoc
18:18
se6ast1an
great! many thanks
18:18
Bertl
well, you can tick all the boxes in the task description
18:18
bluez_[m]
Also updated the WIki somewhat
18:18
bluez_[m]
oh and i would have pressed the 'final submit button' at least three times xD
18:19
bluez_[m]
<Bertl "well, you can tick all the boxes"> i guess... thanks :)
18:19
bluez_[m]
I had a lot of help :)
18:20
Bertl
that's what the mentors are for
18:20
bluez_[m]
and I had a great experience! thats all from me!
18:20
se6ast1an
thanks!
18:20
se6ast1an
anu3jn: you around?
18:20
se6ast1an
vup?
18:23
se6ast1an
anu3jn asked me to report in case he wont be able to be here:
18:23
RexOrManual
joined the channel
18:23
se6ast1an
he worked on AXIOM Micro r3 routing
18:23
se6ast1an
quick update from me:
18:24
se6ast1an
after some deadlines with my dayjob last week I eventually got to grips with the PCB prober and python
18:24
se6ast1an
I can already move the probe head on all axis, change speed/stepsizes
18:24
se6ast1an
save and move to fiducials
18:25
se6ast1an
added a safety mechanism that prevents the user from crashing the needle into the board unintentionally
18:25
se6ast1an
now I am implementing the optical fiducial center detection movements
18:25
se6ast1an
the detection was already added by bertl
18:26
se6ast1an
now I just enabled the move to center function
18:26
se6ast1an
github repo was also created last week and I pushed code changes constantly
18:26
se6ast1an
axiom presentation at CH meet last wednesday also went well
18:27
se6ast1an
small crowd due to covid distance rules
18:27
se6ast1an
but very interesting questions and discussions
18:27
se6ast1an
laser cut session with bertl last thursday went good and bad
18:27
se6ast1an
the acrylic pieces for glue tests worked well
18:28
se6ast1an
in general the laser cutter is fully operational now which is also great
18:28
se6ast1an
cutting the rubber sheets didnt work very well though, ugly edges so we need another method to manufacture the enclosure feet custom shapes
18:28
se6ast1an
will continue to work on the prober for the next week
18:28
se6ast1an
thats it from me
18:29
se6ast1an
Bertl: do you want to "finish us"?
18:29
Bertl
of course!
18:29
Bertl
I'm too tired today for any special moves though :)
18:29
se6ast1an
sub zero tired?
18:30
Bertl
yep, obviously I spent most of the time with our students, testing and integrating code where possible
18:31
Bertl
there is still a lot to do, as reported, but it looks like GSoC 2020 was quite successful
18:31
Bertl
at least productive :)
18:31
RexOrManual
left the channel
18:32
Bertl
there is now another GSoC week in front of us (final evaluations) where we will try to sort through the submissions and test and get as much as possible integrated as well
18:33
Bertl
after that, it should be back to normal business ...
18:33
Bertl
that's it from my side for this week :)
18:36
se6ast1an
great, many thanks!
18:36
se6ast1an
anyone else who wants to speak?
18:37
se6ast1an
otherwise, MEETING CONCLUDED, gsoc might be over but we would love to still hear from you next week!
18:38
se6ast1an
with final evaluations coming up
18:38
Bertl
s/coming up/being here/
18:39
bluez_[m]
yep!
18:39
metal_dent[m]
sure!
18:58
Bertl
off for now ... bbl
18:58
Bertl
changed nick to: Bertl_oO
19:18
RexOrManual
joined the channel
19:23
RexOrManual
left the channel
20:52
anuejn
bluez_[m]: we might want to discuss how to integrate your driver into the automatic firmware builds :)
20:54
anuejn
Do we want to import your code into the axiom-firmware tree or do we want to keep it seperate?
20:55
anuejn
(And include it as a submodule)
20:55
anuejn
In any case, i think we want to somehow move the code inside the apertus github orga
21:36
se6ast1an
its not really a separate thing (right?) so I guess the firmware repo would be suitable
21:39
se6ast1an
off to bed for today, good night
21:53
BAndiT1983
changed nick to: BAndiT1983|away
22:06
Topic
apertus° - open source cinema | www.apertus.org | join the apertus° Lab: http://lab.apertus.org/ | IRC Logs available at: http://irc.apertus.org | Weekly IRC meeting: Monday 18:00 CET/CEST
22:06
se6ast1an
has set the topic
22:23
bluez_[m]
anuejn: sure, integrating into firmware repo could be a good idea... But yes we should discuss it, maybe Bertl could give some input here...?
22:29
Bertl_oO
yes, we should definitely integrate it, we need to address a few things though to make it really useful/standard
22:29
bluez_[m]
Also, I don't want axiom betas all around to crash because of my driver, so I want to take some time to make sure that doesn't happen ': D
22:30
Bertl_oO
yeah, main issue is that we probably want to switch to the kernel GPIO drivers
22:30
bluez_[m]
Bertl: indeed what i was thinking...
22:31
Bertl_oO
well, to be precise, to a modified version with named/labeled IOs
22:31
Bertl_oO
the idea here is that we do a lot of stuff via those GPIO drivers
22:31
Bertl_oO
s/drivers/extenders/
22:32
Bertl_oO
and we currently use 'magic' register settings in our python scripts to do so
22:32
Bertl_oO
now in cases like the analog switch, it is not really necessary to know what the GPIO does (selecting the bus) as long as it is correctly identified and properly used
22:33
Bertl_oO
but in the many other cases, were e.g. a GPIO pin disables or enables a power rail or report the status of such a power rail
22:34
Bertl_oO
it is rather confusing to enable GPIO 987 or read GPIO 985
22:34
Bertl_oO
so the idea here was to have some meaningful names associated with each GPIO
22:34
Bertl_oO
as far as we know (and that doesn't mean too much :) this is not currently possible from the kernel side
22:35
Bertl_oO
so the options there are basically:
22:36
Bertl_oO
- 'improve' the kernel GPIO driver to use some kind of labels from the devicetree
22:36
Bertl_oO
- use some smart userspace script to create a bunch of symlinks somewhere
22:37
Bertl_oO
and of course, once done, we need to adapt the scripts to make use of that
22:38
Bertl_oO
bluez_[m]: for your driver, also we need to get the generalization working properly, i.e. no RFE/RFW special casing :)
22:38
Bertl_oO
s/also we/we also/
22:39
bluez_[m]
Yep yep ill get to it :)
22:39
Bertl_oO
this for example could be used to program/debug MachXO2s on the plugin modules like the USB3 module
22:39
Bertl_oO
although that might need some other tricks ...
22:41
Bertl_oO
we should also discuss the PIC side functions we want to implement to simplify the driver setup and allow for non driver related PIC access
22:41
Bertl_oO
(which wasn't tested so far, IIRC)
22:41
bluez_[m]
I have no idea but guess ill know when ill know xD
22:42
Bertl_oO
mainly the other 16 PIC registers :)
22:42
Bertl_oO
we might at some point wrap those into a GPIO driver or so
22:44
bluez_[m]
<Bertl_oO "this for example could be used t"> Are we going to do that 'through' one of the routing fabrics though...?
22:45
Bertl_oO
kind of, yes
22:45
bluez_[m]
Interesting....
22:46
Bertl_oO
at least for now, till we have a proper remote JTAG interface via the Zynq-MachXO2 connection
22:46
Bertl_oO
(which would be way faster and probably also simpler)
22:47
bluez_[m]
Ohh.. Ok ok
22:48
bluez_[m]
Anyway... Was just dozing off... So lets discuss tomorrow..
22:49
bluez_[m]
Nn!
22:49
Bertl_oO
yep, have a good sleep!