00:17 | dmj_nova | left the channel | |
00:18 | dmj_nova | joined the channel | |
06:41 | se6astian | joined the channel | |
10:56 | Bertl | morning everyone!
| |
11:07 | se6astian | morning!
| |
11:47 | se6astian | just sent you an email to kickstart the script development
| |
11:51 | Bertl | did you test the scripts?
| |
11:52 | se6astian | how?
| |
11:52 | Bertl | by running them on the zedboard for example?
| |
11:53 | Bertl | (just curious :)
| |
11:55 | se6astian | well I dont have an image sensor :)
| |
11:55 | se6astian | I can validate syntax I guess
| |
11:55 | Bertl | doesn't matter, the only difference is that you will always get '0' when reading a register
| |
11:56 | Bertl | but I guess I can whip up a simple memory based replacement, which returns the last value you did set
| |
11:58 | Bertl | maybe dmj_nova has already done something similar or maybe even a better register simulation ...
| |
12:05 | se6astian | sounds good
| |
12:06 | se6astian | for a general desktop linux would be even better
| |
12:07 | Bertl | well, won't work as there is no AXI simulation so far (e.g. in qemu)
| |
12:07 | Bertl | but for sure, somebody could develop that or something similar
| |
12:08 | se6astian | the cmv_reg () could just write to a file instead for testing?
| |
12:09 | Bertl | sure, but then it is a different script :)
| |
12:09 | se6astian | but similar :)
| |
12:09 | Bertl | similar, alternatively I'd replace devmem :)
| |
12:09 | Bertl | (as long as you use devmem that is)
| |
12:11 | Bertl | but note that a 'normal' desktop and the limited arm linux is different, so it would be better to run it on a small sized arm, like a raspberry pi for example
| |
12:11 | Bertl | (or an arm simulation, like with qemu)
| |
12:12 | Bertl | http://zedboard.org/content/qemu
| |
12:15 | Bertl | mail looks fine
| |
12:16 | Bertl | (but you might want to incorporate the ideas we just had)
| |
12:20 | se6astian | hmm, I dont want to make it look to complicated - I already fear we will not be able to motivate anyone this way, if we now require rather complex preparations that small group of people who would be interested might be scared away right away
| |
12:21 | Bertl | well, then how about writing a fake devmem and telling folks to limit themselves to /bin/sh (instead of bash/csh)
| |
12:28 | se6astian | great!
| |
12:54 | Bertl | http://vserver.13thfloor.at/Stuff/AXIOM/FAKE/
| |
12:54 | se6astian | how does this work?
| |
12:55 | Bertl | this is a statically linked busybox (for x86_64, arm coming up shortly) which has a fake devmem builtin
| |
12:56 | Bertl | all you need to get it to work is the following:
| |
12:56 | Bertl | dd if=/dev/zero of=/tmp/mem bs=1k seek=4M count=1
| |
12:56 | Bertl | this will create a sparse 4GB file /tmp/mem, which will be used by the fake devmem
| |
12:57 | Bertl | values written can be read back, non existing values return 0
| |
12:59 | Bertl | /bin/sh and /sbin/devmem both link to busybox on the axiom alpha filesystem
| |
12:59 | Bertl | so both can be tested with this executeable
| |
13:02 | se6astian | documented
| |
13:02 | se6astian | https://wiki.apertus.org/index.php?title=Axiom_Alpha_Prototype#statically_linked_busybox
| |
13:03 | se6astian | will write the mail now and just add "to get started with instructions contact us" :)
| |
13:07 | se6astian | done!
| |
13:07 | se6astian | now lets see if we get the lazy bunch to do some work :)
| |
13:23 | se6astian | haha the first good idea (I assume)
| |
13:23 | se6astian | Stefan is the guy we also met at IBC
| |
13:23 | se6astian | he was sitting left to me when we had lunch
| |
15:09 | se6astian | Bertl, do you remember if the image sensor is absolutely centered to the FMC connector on the PCB ?
| |
15:21 | Bertl | it is not, as you can see on the eagle board files
| |
15:21 | Bertl | (i.e. the sensor area is on the layer "Sensor")
| |
15:22 | Bertl | but it is centered regarding lens mount
| |
15:23 | Bertl | (which is obvious, I guess :)
| |
15:24 | se6astian | ok, I will create a 3d model of the adapter board
| |
15:34 | Bertl | there are tools to export that from eagle IIRC
| |
15:34 | se6astian | do parts have 3 footprints associated?
| |
15:34 | Bertl | http://www.cadsoftusa.com/services/3d-visualization/
| |
15:35 | Bertl | 3 footprints?
| |
15:35 | se6astian | *3d footprints
| |
15:35 | Bertl | no
| |
15:35 | Bertl | but the board will work nevertheless
| |
15:35 | se6astian | I will be faster to rebuild it then I think
| |
15:36 | Bertl | okay
| |
15:36 | se6astian | which FMC connector did you solder on (stack height)?
| |
15:37 | se6astian | and could you meassure how thick the PCB is please
| |
15:38 | Bertl | that should be part of the design rules
| |
15:38 | Bertl | here it says 1.64084375mm
| |
15:39 | Bertl | (that is with both, top and bottom, still having copper on)
| |
15:39 | Bertl | the top/bottom copper layer is ~ 0.03556 mm
| |
15:39 | se6astian | thanks
| |
15:40 | Bertl | the solder mask will add a little as well (similar for silk screen)
| |
15:40 | se6astian | it doesnt have to be THAT accurate ;)
| |
15:40 | se6astian | and the FMC connector stack height please
| |
15:42 | Bertl | that actually depends on the FMC connector
| |
15:43 | Bertl | the current board has the 8.5mm connector
| |
15:44 | Bertl | the other board I'm working on at the side has the 10mm connector
| |
15:44 | Bertl | I'm measuring 8.56mm between the zedboard and the adapter pcb
| |
15:45 | se6astian | ok, I will just use the current board as reference for now
| |
15:48 | se6astian | while you are at it, could you meassure the tickness of the andon socket please (its not in the datasheet)
| |
15:49 | Bertl | you mean the cutout area or what?
| |
15:50 | se6astian | no the height of the andon socket (from PCB surface)
| |
15:51 | Bertl | that is in the datasheet
| |
15:51 | Bertl | well kind of, the pin limits it
| |
15:52 | se6astian | I see
| |
15:52 | Bertl | the fr board has a thickness of 1.7mm
| |
15:52 | Bertl | and it sits 2.2mm below the top
| |
15:53 | Bertl | i.e. 0.5mm of the pins are above the board
| |
15:53 | se6astian | the 400T4 pins right?
| |
15:53 | Bertl | the total pin height is roughly 2.8mm from the board top
| |
15:54 | se6astian | datasheet says 2.82mm so that sounds good
| |
15:54 | Bertl | but if you are modelling the components, wouldn't it be better to make that in a format suitable for pcb 3d models?
| |
15:55 | Bertl | s/format/way/
| |
15:57 | se6astian | its very simplified, just a box with the right dimensions
| |
16:02 | Bertl | well, those sockets are not really complicated, so it basically is a box (with a number of pins, all identical) with the right dimensions :)
| |
18:42 | se6astian | left the channel | |
18:43 | se6astian | joined the channel | |
18:55 | se6astian | left the channel | |
18:57 | se6astian | joined the channel | |
19:29 | [1]se6astian | joined the channel | |
19:31 | se6astian | left the channel | |
19:31 | [1]se6astian | changed nick to: se6astian
| |
20:02 | [1]se6astian | joined the channel | |
20:05 | se6astian | left the channel | |
20:05 | [1]se6astian | changed nick to: se6astian
| |
21:00 | se6astian | ok good night for today :)
| |
21:01 | se6astian | left the channel |