02:18 | jucar | joined the channel | |
03:13 | jucar | left the channel | |
03:49 | jucar | joined the channel | |
04:04 | jucar | left the channel | |
06:43 | se6astian | joined the channel | |
06:44 | se6astian | good morning
| |
06:46 | Bertl | morning se6astian!
| |
06:54 | se6astian | While I am at the university waiting for students to need me I am starting now to code the c program to display the sensor registers in human readable form, is it possible to read the 128x16bit in one command on the zedboard and pipe it through the tool as well on the ssh commandline?
| |
06:55 | Bertl | yes
| |
06:58 | se6astian | perfect
| |
06:59 | se6astian | then we can use it for images and the current state of the sensor when creating images
| |
06:59 | Bertl | yup
| |
07:26 | Bertl | vserver.13thfloor.at/Stuff/AXIOM/cmv_snap
| |
07:26 | Bertl | minor update, allows to use -r without implicit -e
| |
07:27 | Bertl | i.e. will simply dump the registers to stdout
| |
07:31 | Bertl | off for a nap ... bbl
| |
07:34 | se6astian | thanks, good night!
| |
10:33 | jucar | joined the channel | |
14:01 | Bertl | morning everyone!
| |
14:02 | se6astian | hello!
| |
14:23 | FergusL | hi here
| |
14:23 | FergusL | ha se6astian, good about the sensor register program
| |
14:24 | FergusL | thought I could make one too but... like many think it was just an idea that wasn't completed
| |
14:49 | se6astian | are you good with c programming?
| |
14:57 | se6astian | left the channel | |
16:22 | se6astian | joined the channel | |
16:24 | FergusL | no se6astian I am not
| |
16:24 | FergusL | basic stuff
| |
16:25 | FergusL | (^ answer to your question about C programming)
| |
16:25 | FergusL | I was planning on doing it in Python
| |
16:27 | se6astian | too bad :)
| |
16:31 | FergusL | well sorry !
| |
16:39 | FergusL | se6astian: but I think I can give a hand
| |
16:39 | FergusL | is C your main language ?
| |
16:40 | se6astian | do you mean am I good with C? not at all, its like the first time in 10 years I touched it again
| |
16:40 | FergusL | hah
| |
16:40 | FergusL | how do you plan to store the strings that will describe each memory address ?
| |
16:41 | FergusL | directly in the code ?
| |
16:41 | se6astian | what do you mean with "store"?
| |
16:41 | FergusL | like, a separate text file ? with all the text
| |
16:41 | se6astian | no need to store anything
| |
16:42 | Bertl | you can do both, by simply putting the strings in a header file
| |
16:42 | se6astian | the 128x16 bit register dump is appended to each image the prototype saves
| |
16:42 | Bertl | he is referring to information about the registers
| |
16:43 | Bertl | like for example, register 127 is the temperature sensor
| |
16:43 | se6astian | ah I see, directly in the code yes
| |
16:43 | FergusL | I can help with that
| |
16:43 | se6astian | great
| |
16:43 | FergusL | it's just reading the cmv12000 pdf and copying the text there I guess
| |
16:44 | se6astian | we want to make the data "human-readable" not just print text from the datasheet
| |
16:44 | Bertl | it requires a little more, but just a little :)
| |
16:44 | se6astian | if you want to help right now please create a function that converts a char to its binary representation
| |
16:44 | Bertl | first, information is often spread over several registers, and some registers contain several values
| |
16:45 | Bertl | so it isn't a 1:1 match between registers and values
| |
16:45 | Bertl | secondly, as sebastian points out, we do not just want to dump a value with a name, we want to make it comprehensible
| |
16:46 | FergusL | okay
| |
16:46 | Bertl | e.g. single bits -> Enabled, Disabled, On, Off, etc
| |
16:47 | Bertl | values -> ms, factors, etc
| |
16:47 | FergusL | it is some kind of metadata display ? much like an EXIF tags reader ? Foo : Enabled | Value of Bar : 123K
| |
16:47 | FergusL | yes
| |
16:47 | Bertl | yeah, something like that
| |
16:49 | Bertl | but what you can do is work through the latest datasheet and make a list
| |
16:49 | Bertl | something like What, Where and How to interpret
| |
16:51 | FergusL | yes, that was the idea
| |
16:51 | FergusL | lots of bitshifting ahead ! prepare for war
| |
17:01 | FergusL | I'm not sure I understand the char to bin need se6astian, is it because you need to display a binary value like "0b01001011" ? or simply to make the program interpret a char as binary/integer ?
| |
17:09 | se6astian | I draw a table that displays each 16 bit register as binary, hex, decimal and then the interpretation
| |
17:10 | Bertl | not sure that makes much sense though
| |
17:11 | se6astian | its a great way to verify the program is working ;)
| |
17:11 | se6astian | properly
| |
17:12 | Bertl | let's take two examples: reg68, and reg72
| |
17:14 | Bertl | if you want to generalize the program, I'd suggest a structure like this:
| |
17:15 | Bertl | 'Name', 'Comments', 'Format', {(reg, bitrange), (reg, bitrange) ...}
| |
17:17 | Bertl | where 'Name' is for example "Exp_time", "Color_exp", 'Format' might be a function to interpret and output the value, and the reg, bitrange specify which bits are stored where
| |
17:17 | Bertl | but personally I think that is overkill for now, I'd go with a printf for each 'Value' not per register
| |
17:18 | Bertl | e.g. Exp_time, Exp_time2 in ms (or us), Exp_kp1, Exp_kp2 in V, etc
| |
17:19 | Bertl | still makes sense to have binary output, for example for the enable registers
| |
17:19 | Bertl | e.g. Channel_en_bot/top
| |
17:22 | se6astian | FergusL, look at lines 49+ https://github.com/apertus-open-source-cinema/alpha-software/blob/master/misc_scripts_and_utilities/metadata-reader/metadatareader.c
| |
17:22 | se6astian | can you add more here?
| |
17:25 | FergusL | yes
| |
18:59 | jucar | left the channel | |
21:16 | mikkael | joined the channel | |
21:40 | se6astian | good night!
| |
21:40 | se6astian | left the channel | |
22:07 | fsteinel_ | joined the channel | |
22:14 | mikkael | left the channel |