02:06 | Bertl_oO | off to bed now ... have a good one everyone!
| |
02:06 | Bertl_oO | changed nick to: Bertl_zZ
| |
02:58 | Spirit532 | left the channel | |
02:58 | Spirit532 | joined the channel | |
04:43 | BAndiT1983|away | changed nick to: BAndiT1983
| |
06:34 | BAndiT1983 | metal_dent[m]: hi, how is it going?
| |
07:03 | metal_dent[m] | Hi!
| |
07:05 | metal_dent[m] | Yesterday I was going through the microchip document for PIC16 and also checked out the scripts which Bertl showed us the day before on beta and I documented whatever he explained so that i can find it easily whenever I want to refer
| |
07:05 | metal_dent[m] | Also i was about to ask you regarding the prototype which you said i could use
| |
07:06 | BAndiT1983 | will check where it is, but should be in the same folder on my machine
| |
07:06 | BAndiT1983 | it was a very raw project for loading HEX and bringing it into right form for flashing pic16 through pic32
| |
07:08 | BAndiT1983 | not even sure it came further than loading HEX, as i had trouble with linker scripts at first, so flasher wasn't approached that much
| |
07:09 | BAndiT1983 | have you checked HEX specifications already?
| |
07:10 | BAndiT1983 | as i don't remember how far LVP was, have you also checked if ICSProgrammer has "write" commands implemented?
| |
07:10 | metal_dent[m] | > have you checked HEX specifications already?
| |
07:10 | metal_dent[m] | Which one?
| |
07:10 | BAndiT1983 | a diagram of steps would also be nice, so i can see if you are targeting the right direction and do "divide and conquer"
| |
07:11 | BAndiT1983 | e.g. https://people.ece.cornell.edu/land/courses/ece4760/FinalProjects/s2012/ads264_mws228/Final%20Report/Final%20Report/Intel%20HEX%20Standard.pdf
| |
07:13 | BAndiT1983 | you can also store the output of the bootloader with pic16 content and compare it to the files which Bertl has built or just grab the asm files from his server and build with gpasm
| |
07:13 | BAndiT1983 | this would show you in which order the bytes are stored on the pic16
| |
07:15 | metal_dent[m] | > as i don't remember how far LVP was, have you also checked if ICSProgrammer has "write" commands implemented?
| |
07:15 | metal_dent[m] | i think there are load and read methods for ICSP
| |
07:16 | metal_dent[m] | > e.g. https://people.ece.cornell.edu/land/courses/ece4760/FinalProjects/s2012/ads264_mws228/Final%20Report/Final%20Report/Intel%20HEX%20Standard.pdf
| |
07:16 | metal_dent[m] | thanks!
| |
07:19 | BAndiT1983 | have postponed writing, i suppose, as i wanted to have an app to send the data to bootloader (or also to control it in both directions) and was also having a bit of trouble with USB, there is still a comment which line helped to activate pull-up or pull-down resistor (thanks to alexML and Bertl)
| |
07:19 | metal_dent[m] | > you can also store the output of the bootloader with pic16 content and compare it to the files which Bertl has built or just grab the asm files from his server and build with gpasm
| |
07:19 | metal_dent[m] | are the asm files present in the remote setup?
| |
07:19 | BAndiT1983 | the final result is already flashed to the pic16, otherwise you couldn't control the boards or what do you mean?
| |
07:20 | BAndiT1983 | the source files, remote_e.asm and remote_w.asm, are here: http://vserver.13thfloor.at/Stuff/AXIOM/REMOTE/
| |
07:21 | metal_dent[m] | okay
| |
09:20 | samant[m] | left the channel | |
09:31 | samant[m] | joined the channel | |
09:49 | se6ast1an | vup / anuejn: I have a first concept to share: https://cad.onshape.com/documents/119d4253b556f8944095c5ad/w/8cba5fbf62e83d916df2c99f/e/af78801fa9663719e0120078
| |
09:51 | se6ast1an | the lens mount is envisioned to be 3d printed at the height matching the particular sensor to reach correct ffd
| |
09:51 | se6ast1an | for the mount I would screw a c to cs mount adapter into the 3d print
| |
09:55 | se6ast1an | for uv/ir filter I am still thinking
| |
10:03 | se6ast1an | found a simple solution
| |
10:11 | se6ast1an | a 29mm diameter uv/ir filter is glued into the 3d print
| |
10:21 | futarisIRCcloud | left the channel | |
10:28 | Bertl_zZ | changed nick to: Bertl
| |
10:28 | Bertl | morning folks!
| |
10:38 | se6ast1an | good day
| |
12:22 | futarisIRCcloud | joined the channel | |
12:48 | vup | se6ast1an: nice, where would the shield go?
| |
12:48 | vup | on the top?
| |
12:50 | vup | also how big would the sensor board need to be to fit atleast APS-C sensors? I think that would be a reasonable size.
| |
12:50 | se6ast1an | yes, top
| |
12:50 | se6ast1an | ah, if you want larger sensors as well the concept needs to be adapted a bit
| |
12:50 | se6ast1an | on it
| |
12:50 | se6ast1an | shields are identical to beta?
| |
12:53 | vup | se6ast1an: yep the shield is supposed to be identical to the beta
| |
12:53 | se6ast1an | right, adding now
| |
12:54 | vup | great
| |
12:54 | vup | I think as long as we can make it work mechanically, leaving the option for bigger image sensors would be good
| |
12:56 | se6ast1an | definitely
| |
12:56 | se6ast1an | fitting the shield at the top is a challenge though
| |
12:56 | se6ast1an | check the onshape link
| |
12:57 | se6ast1an | the zturn hole pattern gets in the way already
| |
12:58 | se6ast1an | with a larger sensor the shield will get in the way almost anywhere I am afraid...
| |
12:59 | se6ast1an | is moving the image sensor out of the center an option?
| |
13:00 | se6ast1an | moving it lower for example?
| |
13:04 | vup | yeah moving the image sensor out of the center should be no problem
| |
13:06 | vup | also we need to fit two usb-c ports somewhere
| |
13:06 | se6ast1an | right
| |
13:06 | se6ast1an | will try something
| |
13:07 | vup | shield on the side like currently is probably fine aswell I think
| |
13:46 | se6ast1an | take a look now: https://cad.onshape.com/documents/119d4253b556f8944095c5ad/w/8cba5fbf62e83d916df2c99f/e/af78801fa9663719e0120078
| |
13:51 | vup | Bertl: I just tried the camlink 4k with a dvi source and that works aswell btw
| |
13:52 | vup | so I am pretty sure it doesn't need the data island
| |
13:52 | vup | have a meeting now, will take a register dump later
| |
13:53 | vup | se6ast1an: would it not make sense to make the sensor pcb a bit wider and just use one pair of screws on the bottom?
| |
13:54 | vup | and where would you put the usb-c ports? left and right facing to the top?
| |
13:54 | vup | other than that looks pretty great
| |
13:54 | se6ast1an | good idea
| |
13:55 | se6ast1an | usb ports, any side works I guess
| |
13:55 | se6ast1an | the oher connectors on the zturn are all at the top
| |
13:57 | vup | hmm yeah I was kind of hoping to get rid of one of the sides that extend beyond the zturn, as we actually only need one for the plugin slots
| |
13:57 | vup | (r2 had pmod's on the other side, but we got rid of them)
| |
13:58 | se6ast1an | if I could choose any side for connectors then I would go for the right side
| |
13:59 | se6ast1an | if the micros lens is looking away from me
| |
13:59 | vup | yeah me too
| |
13:59 | vup | my problem is mostly how do we fit two usb c ports?
| |
14:00 | vup | I think making them facing to the right is pretty inconvenient
| |
14:02 | se6ast1an | why inconvenient ?
| |
14:03 | se6ast1an | I mean towards the back would be coolest but not sure if thats easy to do
| |
14:04 | vup | I just think cables going out of the camera to the right (if the lens is facing away from me) is inconvenient, you would be likely to get stuck on those cables and snap the ports of I think
| |
14:05 | vup | yeah to the back would be coolest, but I haven't found usb-c ports facing up from the pcb yet
| |
14:05 | se6ast1an | https://gct.co/images/products/usb-connector/gct-usb-type-c.jpg
| |
14:05 | se6ast1an | struggling with search as well
| |
14:05 | se6ast1an | https://gct.co/de/connector/usb4070
| |
14:06 | se6ast1an | https://www.digikey.at/product-detail/en/gct/USB4070-30-C/2073-USB4070-30-CCT-ND/9859732
| |
14:09 | vup | nice find
| |
14:09 | vup | although they don't look too stable I think
| |
14:09 | vup | hmm maybe we could fit them under the shield?
| |
14:09 | vup | (facing to the top)
| |
14:10 | vup | (so the normal RA ones)
| |
14:10 | Bertl | the vertical USB-C connectors are quite stable as long as they are THT
| |
14:11 | vup | by THT you mean not only SMT, right?
| |
14:12 | vup | (but having SMD pads and THT pin's)
| |
14:12 | Bertl | yes
| |
14:12 | se6ast1an | updated: https://cad.onshape.com/documents/119d4253b556f8944095c5ad/w/8cba5fbf62e83d916df2c99f/e/af78801fa9663719e0120078
| |
14:13 | se6ast1an | if you plan for mount holes around the usb-c receptables we could add a 3d print part on top of them that gives some protection
| |
14:14 | vup | se6ast1an: nice, I like it
| |
14:15 | se6ast1an | great!
| |
14:15 | vup | adding something that gives the usb-c receptables some mechanical stability sounds very good
| |
14:15 | vup | there are some truly intriguing usb-c receptable: https://www.digikey.at/product-detail/en/amphenol-icc-commercial-products/MUSBRM1C130/MUSBRM1C130-ND/5877551
| |
14:17 | se6ast1an | very solid!
| |
14:19 | se6ast1an | https://www.digikey.at/product-detail/en/jae-electronics/DX07S024WJ3R400/670-2950-6-ND/6594048
| |
14:19 | Bertl | yes, that is if you plan to hang your UPS on an USB-c cable :)
| |
14:19 | se6ast1an | https://www.digikey.at/product-detail/en/molex/2047110001/900-2047110001TR-ND/10440492
| |
14:19 | se6ast1an | https://www.digikey.at/product-detail/en/kycon-inc/KUSBVX-SMT3-CS-B30TRC/2092-KUSBVX-SMT3-CS-B30DKR-ND/9990252
| |
14:19 | se6ast1an | https://www.digikey.at/products/en/connectors-interconnects/usb-dvi-hdmi-connectors/312?k=&pkeyword=&sv=0&pv69=409429&sf=0&FV=28%7C418395%2C29%7C392960%2C-8%7C312&quantity=&ColumnSort=0&page=1&pageSize=500
| |
14:20 | se6ast1an | last time I searched that was much more difficult, great to see usb-c gain availability
| |
14:21 | Bertl | yes, it is quite accepted as 'new' standard
| |
14:22 | Bertl | in a few years, it will be hard to get micro USB connectors :)
| |
14:22 | vup | yeah I am more and more convinced of using a vertical usb-c receptable
| |
14:22 | vup | those are probably even easier to solder than the horizontal ones that have mixed tht and smt pads
| |
14:23 | vup | I think this one: https://www.digikey.at/product-detail/en/molex/2047110001/900-2047110001CT-ND/10440494 should work fine
| |
14:25 | Bertl | good choice, major brand, looks sturdy and is cheap
| |
14:26 | se6ast1an | great!
| |
14:26 | Bertl | double check if the side plated slots can be done by your PCB fab though, they are quite small
| |
14:26 | Bertl | that said, if they can't do them, round holes would work there as well
| |
14:26 | Bertl | (but they need to be plated)
| |
14:28 | vup | yeah middle terminal ones will need to be round
| |
14:29 | vup | s/terminal/blade/
| |
14:49 | se6ast1an | tried cmv12000 as aps-c option to determine size: https://cad.onshape.com/documents/119d4253b556f8944095c5ad/w/8cba5fbf62e83d916df2c99f/e/af78801fa9663719e0120078
| |
14:49 | se6ast1an | works fine
| |
14:52 | vup | nice
| |
15:52 | se6ast1an | we should revisit the CAD parts when the layout matures but for now I guess the concept is "good enough"
| |
15:52 | se6ast1an | if you need any dimensions or locations from it let me know ( you can also do measurements in the onshape webviewer)
| |
16:01 | vup | se6ast1an: yeah, could you add the connectors to the shield?
| |
16:03 | vup | And after that maybe export it to dxf in a way that the position of the screw holes and the connectors for the shield and sensor board is visible?
| |
16:07 | se6ast1an | sure
| |
16:08 | vup | awesome
| |
16:10 | miek | is there enough information out there to drive the electrical interface on m4/3 lenses, or is there more reverse engineering to be done there?
| |
16:15 | se6ast1an | hi miek, not sure as we are not using any m4/3 lenses
| |
16:23 | miek | ah ok, i was confused by the mentions of an m4/3 adapter
| |
16:26 | se6ast1an | its purely for mechanical reasons in the R2
| |
16:26 | se6ast1an | https://wiki.apertus.org/images/2/2c/00-ABP-001_AXIOM_Micro_V0.1_R1.0.px1150m.jpg
| |
17:42 | se6ast1an | vup: https://cloud.apertus.org/index.php/s/PGHsr9PjkaxLoJC
| |
19:03 | Bertl | off for now ... bbl
| |
19:03 | Bertl | changed nick to: Bertl_oO
| |
19:24 | uberardy | left the channel | |
19:25 | uberardy | joined the channel | |
20:42 | vup | se6ast1an: nice, thanks
| |
22:16 | se6ast1an | you are welcome, heading to bed, good night
| |
22:21 | Bertl_oO | changed nick to: Bertl
| |
22:34 | Bertl | vup: okay, zybo image boots, shall I upload the devicetree/kernel/boot.bin?
| |
22:35 | vup | sure, but the probably won't help that much, the vivado project for the fsbl would be interesting
| |
22:35 | Bertl | no idea what I did back then, it seems to be a xilinx kernel on it
| |
22:35 | Bertl | but it should work with a .bit stream if you have one
| |
22:36 | Bertl | Vivado is finally here, so I will try to build that now
| |
22:36 | Bertl | s/build/install/
| |
22:36 | Bertl | and then see what the reference design does
| |
22:39 | vup | Bertl: hmm I see, I think there should be some .def file that is used to configure the zynq block in vivado, which in turn is used to configure the fsbl
| |
22:39 | vup | I have a bitstream here: https://files.niemo.de/hdmi_zybo-27-May-2020--16-47-17.bit
| |
22:40 | vup | needs this init script: https://files.niemo.de/hdmi_zybo-27-May-2020--16-47-17.init.sh
| |
22:43 | Bertl | it's definitely an adapted beta image (for the zybo)
| |
22:43 | Bertl | 3.17.0-xilinx-dirty is the kernel
| |
22:43 | Bertl | let's test that then :)
| |
22:44 | Bertl | /sys/class/fclk/fclk0/enable: No such file or directory
| |
22:44 | Bertl | I remember that the pathes chaned there :)
| |
22:45 | Bertl | it also seems the fclk driver is missing ... :(
| |
22:46 | Bertl | ah, no, driver is there, pathes are just mor different than I remembered :)
| |
22:47 | Bertl | we have output!
| |
22:47 | Bertl | 1080p60 test image
| |
22:48 | Bertl | so let me try to get the same working with the reference design ...
| |
23:28 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
23:42 | vup | Bertl: wow didn't expect our hdmi stuff to just work, thats nice
| |
23:44 | Bertl | yeah, definitely nice job on your end! kudos!
|