#apertus IRC Channel Logs

no, they are just informational in case you want to rebuild the kernel (or diagnose the settings)

i know c++ and im a photographer by hobby

hello mohit!

what help do you need?

well, you already managed the first challenge, coming here on IRC

the next step is to pick a task from our Workboard https://lab.apertus.org/project/view/20/

here some more general information on GSoC 2018

thank you @Bertl i will just go through them

i had one more query in case if i'm unable to participate in gsoc can i still keep up contributing here as i,m found of this project already

Glad to know that..

you're welcome!

Welcome Mohit! I'm too a student interested in GSoC

Yeah, but I didn't have to run the full boot. Will do it when I get home

it takes a while till it boots to the shell, had some error messages which were shown in between from time to time, but overall it worked, haven't tried it for quite a while

Ok! Understood!

never tried to setup network there, but we can try to solve it together

Sounds good! :)

you should look into qemu xilinx docs, let me find the right one

at the bottom is the link to UG1169, this is the doc file

page 21, storage media should be a good start

TofuLynx: BAndiT1983: qemu is not that nice to use at the moment as a standalone solution

not an expert, so cannot say anything

I have the same question, what is it?

felix_, loose cable somewhere?

maybe not cable, but the fixed connector not sitting tight

is the hdmi output setup correctly? i mean the console commands

"If you look at the back of the camera you will now see a blue LED near the top flashing very fast - every blue flash is one image being acquired."

i ran the setup.sh

the blue led doesn't blink

you could try the steps in this chapter -> Generator and HDMI Output

the bitstream is a symlink to cmv_hdmi3_dual_60.bit and in the setup ./gen_init.sh 1080p60 is used

hm, maybe Bertl_oO can help

now you can try another slot ;)

out of ideas, sorry

TofuLynx, BAndiT1983: chroot is when you change the root directory on a unix system

no idea, where is it mentioned with qemu?

<anuejn> TofuLynx: BAndiT1983: qemu is not that nice to use at the moment as a standalone solution

well, you have to ask anuejn for details on that :)

note that QEMU can act as a pure binary emulator, not only as system emulation, so maybe he is talking about having an ARM filesystem and using QEMU + chroot to work there 'emulated'

copy the content (files) from the SD card into a directory, then chroot (using QEMU as binary emulator) into that directory

https://gist.github.com/mikkeloscar/a85b08881c437795c1b9

if the emulation would be complete, yes, of course

Really?

hmm?

emulating the SD card itself is not such a problem

but booting the AXIOM firmware from a virtual SD card requires more than that

including some proprietary boot loader code which starts the chip

And is it necessary to test my code of the c++ challenge?

Bertl_oO: TofuLynx bertl is right

Yeah but the challenge has the line .5

that's why it is a 'challenge'

jup

booting it works, but the problem is, that network is somehow broken in the xilinx qemu (at least for me)

for which you need to install the `qemu-user-static` package when your on ubuntu

this will lead to a beta image booting to a shell, but unfortunately no network at all

I think the network problems are related to a missing 'connection' between the 'nic' emulation and the qemu network stack

have you looked at the chapter about networking?

Well I don't have any knowledge about this, so will have to read a lot of docs

Yeah :D

often you have to search through many pages to find a little command which would help at the end

Learned really a lot

also TFTP part?

sooon ish (tm) i will upstream my changes to the apertus build system, then this will be a lot easier

TofuLynx, it was no joke, it's in the docs

no but using a chroot of the image

he modifies DTS

how long does it usually takes to boot?

and QEMU several minutes

3-5 minutes, if i remember correctly, but it depends on the machine

??

this is too much

hm, try to press any key

There is no such key

i mean this one -> https://en.wikipedia.org/wiki/Any_key#/media/File:Keyboard-anykey.jpg

:)

the script ones, from the lab

the ones in the lab are maybe outdated

Waiting for root device /dev/mmcblk0p2...

what is /dev/mmcblkOp2?

have you extracted the image, so it's 16gb big?

the image beta_201701089 is 14,9GiB, the devicetree.dtb 10,4KiB

this sizes are okay

it's not a directory. It's a file-backed blockdevice

what Kjetil said

more precisely it _is_ the SD cards second partition

if you extract the sd card image, you will find 3 partitions, if i remember correctly

first holds boot files, second one the linux file system

what is the sdcard image?

ah

or how the one was called with parameters

let me check

quit?

changed computers

failed to initialize

failed to initialize /amba/timer@f8f00200

ok wait a moment

see here, it happens also -> http://pressreset.net/2013/09/buildroot-and-qemu-the-quickest-receipe-for-your-own-linux/

will try to start investigation of qemu problems this weekend, currently planning to create a virtualbox VM, which should include such tools like QEMU, so people can start more faster to develop for axiom or play around with environment

have you tried to press keys? sometimes it helped

it's waiting for the sd card

please show your command line options

yes, that line

hm, have you set up the paths in same way, like in the script? i tested it with different folder structure, so there could be a problem

the target_dir seems Ok

yes

where have you got zImage?

no, i mean the file itself? do we have a downlaod link?

ah

http://vserver.13thfloor.at/Stuff/AXIOM/BETA/

kernel-4.9.0

I dont see the old version there

older one -> https://github.com/apertus-open-source-cinema/axiom-beta-qemu/blob/4334f25641b66013b49ab199e0ce75252bdd49aa/README.md

if you want to give it a roll ,try one from 05.07.2017

https://github.com/apertus-open-source-cinema/axiom-beta-qemu/tree/351364045b0e0c59caaa496499da25c81efe528d

this were the state before big rework, but i'm losing overview over output, too much is going on

off to bed

Bye bye!

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