#apertus IRC Channel Logs

metal_dent[m]: also for firmware task the hardware would be required, Bertl has created a new PCB to control the board from outside, it replicates button and knob signals

morning folks!

Bertl: can you describe the new PCB for the axiom remote control a bit?

just a small info, how it would be connected and what it does? so students know how they would test their cahnges

the main PCB is basically the current state of the remote prototype with all the changes we did manually

the connect board is more or less wiring to attach the pads strategically placed on the remote PCB to an IO shield on an AXIOM Beta

the IO shield has the necessary transistors to act as remote controllable switches

https://644db4de3505c40a0444-327723bce298e3ff5813fb42baeefbaa.ssl.cf1.rackcdn.com/1ff5e963a8839691c0ddb598e35687d9.png

the rest is software on the partial remote beta

if you are referring to the rotary encoders as 'knob' yes, they have three transistors, two for direction and one for button press

you're welcome!

I should get to the hardware on the weekend, at least for one prototype setup

shouldn't be too hard to make that available remotely if you are keen on testing/working on it

okay

https://github.com/gr8geek/apertus-challenge

don't know what kernel guidelines are saying, but the main() has different brace position nad also some empty lines won't be bad for easier reading

pratyush: I take it you chose Task 1 of T884, correct?

so, let's look at the code: https://raw.githubusercontent.com/gr8geek/apertus-challenge/master/proctest/simproc3.c

let me see

and that's against the Linux Kernel coding style?

The for loop

it looks like, yes

it is hard to pinpoint a specific place because it is all a mess

you ignore most of the coding style guides

i.e. what is the idea behind the design?

Yes

checksum=(checksum*checksum)^buf2[i];

Example:

checksum of PARTUYSH is 976459485908

okay

good

means we pass multiple arguments to the driver seperated by a space

it will look good :)

ehm, of course, that's what formatting is for

okay

metal_dent[m]: we can do better, I will hook up a webcam :)

metal_dent[m]: no, you would control it through SSH

either webcam or we could try to send the framebuffer data through USB back to host

as USB is a bit difficult topic

or both, you are greedy lately :D

ha, nice, do you know the cover by hämatom with hansi kürsch from blind guardian?

moving on to the code idea

btw, Sultans of Swing cover by Leo Moracchioli and Mary Spender is nice too

Bertl: When the user writes to the driver mywrite() is called

i mean to say when mywrite is invoked

Bertl: I realized I have been just using the procfs file to read and write data to the driver... I did not actually register and create a character device file ':D I see ioctl and procfs are just debugging methods for our driver. So I am currently changing the code to do all this.

bluez_[m]: sounds good, double check formatting and code style :)

Bertl: I have a doubt though, what must actually reading the character device return (and not reading the procfs entry) ? Should it return the same data we wrote or should it return the checksum like the procfs entry?

;)

> bluez_: sounds good, double check formatting and code style :)

write(fd, buf, sizeof(buf));

No rush absolutely ':D

or more precisely: what does the task description say about reading from the character device?

no need to 'guess', just check with the task :)

Ok ok... will get to work... thanks!

Bertl: We is I

Bertl: I am from Bihar so we becomes sometimes I

(not so much with the bad code formatting though)

And do we have to create three seperate kernel modules

Come on folks, the task description is literally three lines

> either webcam or we could try to send the framebuffer data through USB back to host

metal_dent[m]: it's not that difficult, you just have to divide the tasks in smaller sub-tasks -> "divide and conquer"

someone uses probably the web client

Sure we will! Sorry for the silly question though ':D

Yes, that's what am trying for the proposal 😅

Me?

Yes, am using riot :)

do you have questions at the moment or need anything?

of course, just write here or sent an email, whatever is more comfortable for you

cool!

Hello omar31! how's it going?

Having some difficulties in installing Vivado

I was using an older version (2015) but wanted to upgrade but unfortunately Xilinx tools are forbidden here in Egypt

I think I saw someone with a similar problem while looking into last year logs.

yeah, managed to 'work around it'

Hello there, I am Pragya Angra. I had been told to talk to you as I wanted to contribute the organisation through my skills in C and C++ and you deal with the languages I specified.

do i have a clone now?

crazy times, probably corona consequence

hm, good idea, come back clone, framebuffer is not outputting to USB yet

hello everyone!

I was wondering if, with firmware 2.0, we still need to use --swap-lines in the darkframe calibration process

ref : https://wiki.apertus.org/index.php/Factory_Calibration

maybe se6ast1an knows the latest state

hello!

please adapt the wiki where this is mentioned

thanks!

let us know how it goes or if you discover anything that needs to be fixed/updated

yep!

great, thanks

I was also wondering which method among the three described in the wiki shoud be used for "RCN calibration" validation ?

method 2 uses only one script, maybe you can try that first

off for today, good night

thanks and bye !