Commit graph

113 commits

Author SHA1 Message Date
bunnie
265805ac94 cleanup warnings 2024-11-19 22:17:07 +08:00
bunnie
4a99341269 cleanup warnings 2024-11-14 22:19:40 +08:00
bunnie
fac7adca35 improve UX a little bit 2024-11-14 00:36:24 +08:00
bunnie
0bad04856b debug fixed point underflow issue 2024-11-14 00:34:02 +08:00
bunnie
fc95e8b7b3 update findings 2024-11-14 00:33:39 +08:00
bunnie
c2edfee2fd try to fix timeout issue on camera capture 2024-11-14 00:15:51 +08:00
bunnie
2e25ebff9f upgrade the linederivation to use std
this eliminates occasional storage overflow errors during searching
2024-11-14 00:03:49 +08:00
bunnie
3135407e8e live QR decoding now working!
Got up to version 8 to decode, although version 8 is a bit fussy.

Fairly sensitive to camera focal distance - hard to see focus
issues on B/W display. This needs to be improved in the HW.
2024-11-13 23:29:50 +08:00
bunnie
2b5aab23e0 add fractional iterator for conversion of pixels to modules 2024-11-13 23:29:26 +08:00
bunnie
8002d522b0 add support for neighborhood estimation and version guessing 2024-11-13 23:28:54 +08:00
bunnie
45b5dc1d95 flip image vertically as it comes from the camera fb
this orients it correctly for processing by the QR pipeline
2024-11-12 23:22:15 +08:00
bunnie
dc0fd47ff4 add an option to decongest udma
There is a hardware bug that causes SPIM RX packets to fail when
the UDMA bus is busy (like when streaming video). This causes
swap memory to fail because it relies on the SPIM bus.

This patch causes the video to sample *after* any computation
happens, so that any swap memory that might be hit taken care of.

This reduces the efficiency of the loop somewhat, because without
the decongesting, we could kick off the camera read and do useful
computation while the camera streamed data. Now we have to keep
them separate to work around this bug.
2024-11-08 00:14:21 +08:00
bunnie
2692d374c6 add some test scaffolding for userspace video processing
The whole graphical interface - camera + display & QR code processing -
is incorporated into a single process space to minimize on the amount
of swapping/memory message passing necessary to implement a low-latency,
high-frame rate video interface.

The current service just starts a camera-to-display loopback
while searching for and aligning QR code markers, without consulting
any other service on whether it should do that or not. Suitable
for debug and performance characterization, but not usable for
product integration.

The good news is we're getting an acceptable frame rate on
the camera during search mode with the kernel running.
2024-11-07 16:14:29 +08:00