Code: Select all
sudo dtc -I dts -O dtb -o /boot/dt-blob.bin dt-blob.dts
Almost certainly you're still running a Raspbian Jessie release, not Stretch which was released in August. Run "cat /etc/os-release" to confirm - it'll contain either PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)", or PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)" as the first line. Jessie no longer gets significant updates.pibumble wrote: ↑Wed Nov 15, 2017 9:52 amFollowed the instructions how to get latest release from here: https://www.raspberrypi.org/documentati ... pdating.md
(Which takes a while to complete)
Now uname gives: Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
Which is STILL before your build of 22 July.
That is how far my knowledge goes.
What do I need to do to pull in the latest MMAL version?
Correct. This is called from the frame start and frame end interrupt handling of the CSI2 receiver, so it is active for every frame going in any mode with any settings. You will have very minor interrupt latency jitter on the signal, but the VPU is pretty good in that regard (certainly better than the ARMs!)Kozuch wrote: ↑Thu Apr 19, 2018 2:36 pmNice to hear we've got a precise frame signal from the camera! You do not mention any camera modes so I guess this will work in ANY camera mode (video, stills), am I right? I also guess this may be working regardless of other camera settings (shutter speed, ISO etc.). Would you confirm please?
Last line of the first postKozuch wrote: ↑Wed Apr 25, 2018 11:05 pmDo the sync pulses respect the framerate setting done by --framerate/-fps parameters of RaspiVidYUV? If I request a framerate of 5 Hz, does the sensor run at 5 Hz (and hence give 5 Hz sync pulses) or is the framerate lowered in software with the sensor running at a higher framerate?
Frame rate control (on the Pi at least) is always done by varying the blanking period on the sensor. Some systems vary the PLL setup to change the pixel clock, but that is significantly more involved.The period of the pulse will vary with the frame rate, and the mark/space ratio of the sync pulse will vary with the mode - that is to be expected.
single grab and continuous grab mode? Do you mean the capture and capture_continuous methods from Picamera?fishbeetle wrote: ↑Tue May 15, 2018 1:23 pmI'm trying to use the LED flash sync feature in continuous grab mode on a Pi3B with a v2 camera. I followed the instructions from above and was able to get the flash pulse(s) for single grabs but in continuous grab mode (with exposure_mode off) I get no pulses. Should this possible?
Thanks for your time.
OK, I'm still not clear whether you're using the sync pulses described here by setting disable_camera_led=2 or 3, or using the flash driver as described in the Picamera docs.fishbeetle wrote: ↑Tue May 15, 2018 8:34 pmThanks for responding, yes I should have said capture_continuous using PiCamera in Python. To be precise, I want to drive an IR illuminator with the pulse signal, if not directly then via some custom pulse shaping network. Any advise would be much appreciated. I'll be using the camera in fully manual mode, shutter speed, gain (ISO) set by software and at a fixed frame rate of 3 - 6 fps.
I don't know which mode you're running, but typically on IMX219 a line takes ~19us to read out. If you're turning on the illumination at the frame start interrupt then the top line will have had no extra illumination, and on a 1ms exposure time line 52 (1000us / 19us) is just starting to expose. Therefore there will be a gradual increase in brightness between lines 1 and 52.fishbeetle wrote: ↑Wed May 16, 2018 2:59 pmOK, couldn't get the flash driver to work in capture_continuous, but setting disable_camera_led=3 does generate the pulses I need. And driving the IR illuminator directly with these pulses works like a dream. I'm using exposure_mode=off and a fixed shutter speed of just 1-2ms and at 6 frames per second
Yes, exactly that.Kozuch wrote: ↑Mon May 21, 2018 8:01 pm
Could someone please provide me with a sample part of https://github.com/raspberrypi/firmware ... t-blob.dts for Pi 3 v1.2 (pins_3b2) if I want to map the camera led to GPIO21 (pin #40) to get the sync pulses there? In [email protected]_0_LED section should I just change type to "internal" and number to 21?
I don't quite see how this externally triggers cameras, it appears it just shows you when a picture is being taken. Anyone got any details how it can be used to trigger cameras?6by9 wrote: ↑Mon Aug 07, 2017 4:00 pmThere have been various requests over the years for external triggers for frame synchronisation. Generally it's been stated that doing such things isn't trivial, and it wasn't. However, as of the 22nd July firmware, there is support for repurposing the camera LED GPIO to change state on frame start and frame end interrupts.....