#apertus IRC Channel Logs

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

off for now ... bbl

Hello, I am Sergio González :)

great to have you here"

;)

hello sgonzalez! :)

This is it se6astian

all you need to do is get a new micro sd card for the beta

instructions here: https://github.com/apertus-open-source-cinema/beta-software

put it in the beta, boot it and report what works/is missing

or the explosion yes :D

Ok, this part is simple

the thing is that this new firmware build is very different to the current images we ship with cameras

like all the cmv_* tools that in the "normal" build are placed in /root/

But I have two problems now

on the Beta?

are meant to be in a linux system path for binaries in the automated build so they can be executed from anywhere

maybe a normal pc monitor to just evaluate if the image is clean is enough

how can we support you to get it fixed?

what exactly is the problem, do you have a picture?

please elaborate what happened

from the MicroZed, yes?

If I can't fix, maybe I can buy another MicroZed

Ok, I will send to you

great

Thinking that I already have the camera fixed and working, besides seeing that it takes more or less correct photos, what kind of tests would you like to make?

that would be great

checking if the fpga binary is correctly loaded

like startup.sh

Ok, another thing is were I can upload the results of the automated test

lab tasks would be best I think

This is the other question, there are any task already?

I'm open to suggestions (name wise) but 'startup.sh' and 'boot_up.sh' are as bad as 'kick.sh' (note that 'kick_manual.sh' is called from 'kick.sh')

the systemd service is called cmv12k

I think these names should be associated with their function

I mean, if they are the starting scripts of the axiom, they should be associated with the axiom

so, load firmware, train LVDS, configure sensor, configure HDMI output, etc

Jejeje, maybe ;)

I'm thinking

lets focus on just getting everything to work properly before we start renaming stuff :)

also note that the future control daemon should probably take care of most of the initialization part

I'm fine with that (or similar names based on init/initialize)

As se6astian say, for the moment, we focus on the automated builds and tests

Perfect

Yes ;)

We can meet another day to continue, or manage it through the lab

https://lab.apertus.org/T1091

lets meet again once you got the task "rolling" and maybe have specific questions already

solving this will mean a great deal to the project

currently there are as many different firmware version as we have cameras shipped :)

I will meet another day

Ok, I will

only the tets are missing ;)

we werent able to fix this, because we dont have hardware to test and fix this.

if i remember correctly, kick.sh doesnt make it through on the image, because of some fuckup with the memory mapped region

the camera hung

i dont remember the probems exactly tho

we tried it, but not sure, wether it worked

because without a proper zynq image kick.sh will just hang the camera

bitstream seemed to be properl loaded...

*this would be a good thing to continue with

good night