#apertus IRC Channel Logs

off to bed now ... have a good one everyone!

interesting link for users of VSCode: https://www.vscodecandothat.com/

se6ast1an: Hi, what size do you want for the checkbox icons?

20x20 please

morning folks!

se6ast1an: should I add the checkbox conversion in the makefile?

but I'll have to add another entry in the makefile for that as it's not an icon file, right? (also the icons are 24x24 and these are 20x20)

we have named the home, back, up, down, etc images as "_icon"

yes, so for that I created a method in makefile which has size and filename as parameters

great, thanks

yes, but with a different size (i just asked to make sure what should I write in the makefile :)

I might discover that 20x20 is too small later on :)

How about 24x24, same as the other icons? Will make makefile simpler too :P

meeting in 10 minutes!

who is here? please message me know if you want to report

great!

bluez_[m]: please start with the reporting

hello everyone

I also finally started coding, i made a simple driver that instantiates and binds with the addresses that our pic16s expose... the driver can now easily read and write from it

here is the repo i am using

sry... the entry for the pic16s in the betas

also, please make sure to adhere to the kernel coding style ...

a brief guide what commands are required to program/flash the PICs on the mainboard would be a great addition to https://wiki.apertus.org/index.php/Beta_Main_Board - I know of at least one user in spain who requires exactly that right now

okay

<se6ast1an "a brief guide what commands are "> right, thanks!

so continuing... i added a boot option that works with my devicetree file with the test kernel... the old devicetree file was renamed devcetree_golden and works with the golden kernel... another option is for the custom kernel bertl was building

<se6ast1an "bluez_: do you have a wiki accou"> i guess... not

<se6ast1an "please create one, I created a l"> ah, okay!

eventually ofc

many thanks!

sure!

i also modified the ImageButton to have a button with a text and an image

and right now i'm working on my PR for ImageButton (still need to eliminate some redundant code) and also on the checkbox task (T1193)

i guess that's it from side (sry i couldn't work much as my health was a bit off ':D )

I think you discussed with BAndiT1983 already a bit that the focus should shift steadily towards the axiom remote bootloader now which is the main task of GSoC for you

great

thanks se6ast1an:

I also discussed with bertl about the testing of the remapper, I have a few ideas in mind, currently modifying cmv_serdes.vhd to generate fake data that would help me in testing of the full pipeline.

Thats it from my side!

great, thanks, megora, you are next

I'm working on an e.MMC host. So far, I decided what I need to make as a very initial host functionality. I still have a lot of details to clarify, but the common picture is ready. In parallel, I'd found some existing open-source modules that could be useful in a verification process, and I'm checking how well these projects could fit my needs.

So if anyone can share their experience with this question, I would appreciate that.

thanks!

panintended cannot jon us right now but sent me a message to share with you:

Last week I worked on T1185 (handle BUTTON DOWN events in the visualizer). I have a working PoC for the 12 buttons (thanks BandiT1983 for the help on different options that simplified the code!), but currently the knob press is not behaving the way we'd expect (highlighting enabled while holding the knob down works, but selection of the item upon release doesn't). I'm thinking to change the way we implemented the button of the knob and currently going

I've also claimed T1203 (Central Parameter/Settings Database implementation - Observer Pattern) from se6ast1an, but I'm yet to work on it. I'll have some updates on this by the end of the week.

I had a telephone call with manfred today and he will take care of things on the next weekend (laser cutting rubber feet prototypes and drilling missing holes in AXIOM Beta CP enclosure prototype parts

vup & anuejn any news from your side?

I have been mostly working on the AXIOM remote code in the recent week, no real milestones reached, just improvements and progress here and there

my contact from 5 years ago does not seem to be working there anymore unfortunately

https://github.com/apertus-open-source-cinema/misc-tools-utilities/commits/master

Bertl: please go ahead with your news

so my week was mostly spent on rework and hardware fixes and testing ...

so the camera is now streaming 24/7 and images can be captured easily, but I still need to add low bandwidth encoding to make it work properly remotely

nevertheless, both Remotes are working fine as far as I can tell and the two Partial Betas doing their job as well

the entire setup seems to be doing fine and so far there have been no real issues

I'd say we can start end of the week with documentation

that said, I urge all our students to check the setup for their purpose till our next meeting (end of the week)

on the ultra-96 side a bunch of tests have been done, but the picture is very much the same so far

raid solutions with two 'slower' devices seem to work reasonably fine for sustained writes though

how was the raid setup exactly done?

software striping between two devices

we probably also want to start designing a simple interface between ultra-96 and Axiom Beta so we can actually transfer data between them

I still have the pcie nvme ssds to give to you for testing, still hope they have some potential for higher speeds

we also started testing the firmware 2.0 for actual Beta bringup and we are in the progress of figuring out all the broken and missing bits and pieces ...

the PCB testing front didn't get any love this week, but I'm quite happy that se6ast1an and BAndiT1983 have taken over the panelization and impedance calculations for the upcoming panel orders

I guess that's it from my side for this week, I leave the teensy disaster for BAndiT1983 to report :)

could be very well related to the smbus_cffi changes

and their stackup/materials

BAndiT1983 told me he does not want to report this week

I can give some quick updates

Ok, so i started the board layout of the micro r3, to figure out how difficult it is on 4 layers and what pcb design rules we need for that. We first thought that we might not be able to use jlc as they seem to have changed their design rules, however I ordered a small test pcb with just the ecp5 fanout (the most difficult part regarding the design rules) and they have accepted that, so it seems we actually can use jlc.

So apart from double checking all the footprints / pin assignments and the schematic in general, we should be ready for routing the board.

Thats it from my side this week.

I need to run before the supermarket closes :)

*so

megora: what technology are you planing to use?

anuejin, initially I need to read back several registers' values that wouldn't be dynamically changing. The total size is up to 4 MB. So I suppose that axi registers would work.

Thus I don't know if it worth effort.

oops.. scrap that ':D

nn