-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected Behavior When Using Camera #21
Comments
Hi Nick, It is probably something that is for the regular SDK I think. I will try to nudge one of the developers to look at this issue. Maybe they know more! |
Hey Kim, |
Hi Nick, Sorry for my late reply for your issue.
This continous mode means you need to keep "always 2 capture task in uDMA (even each task is not a full image)", like what we do in this example: gap_sdk/examples/pmsis/bsp/cameras/test_camera_stream In this case, the uDMA will keep working and you will get the full image streaming. |
Hey Yao, Single Shot ModeThis is what should be achieved in this example: https://github.com/bitcraze/AIdeck_examples/blob/master/GAP8/test_functionalities/test_camera/test.c -- Capture a single image from the camera and save it to the disk. Sync
Async
Continuous ModeFor the continuous mode I looked at the example you mentioned. But since in Therefore, I looked at this other example: https://github.com/GreenWaves-Technologies/gap_sdk/blob/release-v3.7/examples/pmsis/bsp/cameras/test_camera_lcd/test_camera_lcd.c QuestionSo basically my questions boil down to:
|
Hi @SuperN1ck, You have my blessing to update the test camera examples :) If you haven't done it already |
Hi @SuperN1ck , |
I guess this already was fixed in in PR #23 right? |
Yes it was fixed to a degree which don't imply any modifications in the GAP SDK itself (see: SuperN1ck#1). The problem still occurs sometimes for me when not using the default values, but I think this is more related to the GAP SDK so it might make sense to reopen an issue there but I'm fine for now. |
Hey,
I have one problem when using the camera of the AI-Deck I couldn't fix properly. I tested out the
test_camera
-example for the GAP8-chip and got some weird results (but this is also applicable to other examples as far as it seems to me).When I try to capture an image it gets tiled in a weird way like so:
What got me thinking is that this only occurs for the first image. If you wrap it in a loop and continuously capture images like in the wifi streaming example or the GAP8-IO example the problem is gone starting from the second image. So I was investigating what caused this issue and how to solve it. So far the only solution that worked for me is to start and stop the camera once before starting the actual capture process but also after setting the registers for the orientation or other parameters (for instance around line 95)
Doing so is exactly what happens when capturing images continuously but leaving out the capture call.
Therefore this resolves the issue and generates a correct image
![img_correct](https://user-images.githubusercontent.com/12222160/91422411-6dca6180-e857-11ea-92cc-5a7beb047674.png)
But doesn't seem like the correct or proper solution. This also happened on two different AI-Decks so it don't think my specific board might be faulty.
So this results in a couple of open questions:
Cheers,
-Nick
The text was updated successfully, but these errors were encountered: