#apertus IRC Channel Logs

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

off for now ... bbl

good day

https://twitter.com/ApertusOSCinema/status/693426610301698048

beta cases will still be cnc milled?

more details in next teamtalk

gotta go

hey Bertl

found the git repo, but it's a flat hierarchy without test benches that I noticed

hey jjshawver_!

still there is no documentation or test benches, because when the software was developed (for the alpha) there was not much time for that

any starting projects?

gotcha. probably a good time to swap to automake and the git repo?

very cool

just nice for bundling things. especially if you utilize makefiles

automake can handle the dependecies and get you an initial setup so that people can get started really easily

aka, with automake you can create rpms, deb files etc

anyway, as I said, no problem with that

ok cool. is the firmware somewhere else then?

ah, https://github.com/apertus-open-source-cinema/beta-software/tree/master/cmv_hdmi3 seems to be "up-to-date"

ok cool. does vivado dump out a block diagram or anything like that?

there are options for schematic and similar in vivado, but as the cmv_hdmi3 does not work at the "IP" level but on the "VHDL" level I don't think there is anything useable

yeah. I wasn't really meaning "schematic capture"

verdi (an expensive tool) generates one for you from the HDL code you use.

the dvt plugin for eclipse looks pretty nice as well. although that can also be rather spendy 700 per seat

makes sense

basically the firmware works in two almost independant parts

are all of the vhdl files shown at this level?

an input pipeline which receives the images from the sensor, rearranges the data and bursts it into memory

ok. so a specific hardware DMA type of setup

or are you using a different type of memory?

we are using the DDR memory on the Microzed

and the PL <-> DDR transfer happens via the AXI busses

https://www.crowdsupply.com/krtkl/snickerdoodle

hehe, we are backer of the snickerdoodle :)

nice :)

any thoughts on the other alternatives?

that is fair, although any savings can be nice

we have been investigating the parallella, which would be a nice option for low end sensors

yeah. the parallella is a very cool board. guessing you'd go the embedded flavor for the more GPIO

that definitely could be nice

most definitely. that's part of the fun with the open source aspect. any dev board can be plugged in later

that would be great, although some solid documentation would probably help more so.

you have to write that or use the source :)

latex cool with you guys?

documentation isn't a favorite, but definitely helps. so I can start to chip away there initially

removes the need of a lot of verbose coding

personally I'm not a fan of Verilog per se but I'm not against it if you can make a point

I'm not familiar with VHDL 2009. Currently using SystemVerilog 2012. Which I think Vivado also supports

2012 you say, you should probably check that, xilinx is not so fast in picking up new standards :)

i.e. whatever we do, we are limited to the Web Pack provided by Xilinx

Trying to find where I read that

it also has enums, typedefs, structs and unions

in any case it should be combineable with VHDL, so as I said, if you can make a point, that's fine with me

also has keywords to help protect synthesis. i.e. always_comb will throw warnings if there are inferred latches, and always_ff is a good way of showing when registers are being used

it's open source software, and Vivado starts at the VHDL/Verilog level

most definitely. I'll have to check out MyHDL and see what is nice about it. (as I'm sure you've noticed, I'm partial to SystemVerilog - primarily to it's C similarities)

when I started coding HDL (which was when we started with the Alpha design :) I checked out both languages

I'd consider SystemVerilog almost as a third language. A blend between VHDL, Verilog, C and a little of its own :)

most definitely agree that SystemVerilog is a huge improvement over verilog.

check out what the Web Pack provides in this regard

or let me know what you want to work on ...

what hours are you typically available?

ok. sounds good. thanks!

I'll go ahead and get started and get back to you periodically in the next couple weeks

shouldn't be a problem to get you added to the repo, but I guess for a start it's simpler to fork

not sure what that even means :) I'm using vim in a "pro" way :)

not marketing bullshit, i mean pro like you can do a lot of thing with

like 4:2:2 or 4:4:4 10bit support

by editor, i mean video editor (sorry)

I'm currently using vegas on windows, but i want to slowly change my workflow on linux, if it's possible

:'(

so give it a little time and maybe ask again if you don't get feedback

nice, tx!

I wonder if that nonlinear highlight response from regular exposures (that "nondata" part) may be actually a side effect of the PLR circuits

off for a nap ... bbl