-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
V4L2 ISP produces green frames when resizing 9248x6944 (64MPix) images to some output resolutions #1844
Comments
Resize to 1280x720 and 1280x960 both need 45x15 = 675 tiles, exceeding the allocation of 650. @naushir @davidplowman Increasing the number of tiles appears to work, and it looks to only be a memory allocation thing, so how high do we go? |
675 tiles is crazy!! I see no reason not to bump the limit up, maybe to 700 or 750? |
Crazy high, or crazy low?! I did hear mutterings about a ~120MPix sensor, and I haven't looked at how many tiles that would require. I'll see if I can get some malloc figures to see how much the memory usage goes up by for 750 tiles. |
Crazy high. It ought to work, but that's a lot of overhead. |
Updated firmware at https://drive.google.com/file/d/1n_e-qFXIjDcdz8cuXgVSPtO404FHd-5R/view?usp=sharing that should allow for 800 tiles. |
Fix merged into the firmware tree 28th Nov 2023. Closing. |
From raspberrypi/linux#5708 (comment)
Arducam's new 64MP camera causes the ISP to produce green images.
I've put together a basic V4L2 M2M app to load the raw file it produces and feed it into /dev/video12.
Resizing to the 1280x720 logs a firmware side assert
Throughput is impressive as it claims to complete the frame in around 280usec for 9248x6944 to 1280x720!
Conversion to 4624x3472 works, but takes a more leisurely 165ms.
ISP_MAX_TILES_PER_FRAME
is defined as 650. We may be able to just increase it.The text was updated successfully, but these errors were encountered: