Packing Camera Capture

At Fenwick Mail Centre, a small camera photographs every box above belt 6. It sends each pixel as two bytes over an 8-bit parallel bus.

One damaged image line arrived one byte short. The old capture block missed the fault, so every colour after it shifted by one byte.

On the preview screen, orange packing tape turned blue halfway across each box.

The error lasted until someone powered the sorter off and on. Boxes kept moving, but their saved images could not be trusted.

Your task: build the camera capture stage. Pair bytes again at every line, publish complete RGB565 pixels, and report any line that ends with half a pixel.

Interface

Behavior

• The camera changes vsync, href, and d after falling pclk edges
• The capture stage samples all inputs only on rising pclk edges
• While href is high, every rising edge carries one byte
• Each RGB565 pixel contains two bytes, with the high byte first
• Nothing is captured while href is low or vsync is high
• Each sampled low-to-high transition on href resets byte pairing
• Every line therefore starts with a high byte, regardless of the previous line
• One clock after a pixel's second byte is sampled, pixel updates and pixel_valid pulses
• pixel holds its value between completed pixels
• pixel_valid is low except during its one-pclk pulses
• Each observed vsync pulse marks the next captured line as the first line of a new frame
• frame_start pulses one clock after that line's first byte is sampled
• frame_start pulses only once per frame
• When href falls after an even byte count, line_end pulses one clock later
• When href falls after an odd byte count, line_end and frame_err pulse together one clock later
• A half pixel at the end of a damaged line is discarded and never published
• The next line starts fresh with high-byte-first pairing
• After reset, capture stays idle until a vsync pulse has been observed, and pixel reads zero until the first published pixel
• Any lines seen before the first vsync pulse are ignored
• rst high at a rising edge clears capture progress and returns the stage to its initial waiting state
• pixel, pixel_valid, frame_start, line_end, and frame_err are registered outputs

What the bench checks

• The testbench changes camera inputs after falling edges and checks every output cycle by cycle against a reference model
• It sends byte patterns that expose swapped, shifted, or wrongly paired bytes, with the first byte expected in bits 15 through 8
• It sends an odd-length line and checks that line_end and frame_err pulse together one clock after the fall
• It checks that the dangling half pixel is discarded and never reaches pixel
• It follows the damaged line with a clean one and checks that pairing re-anchors on the href rise
• It sends lines before the first vsync pulse and checks that they are ignored
• It resets mid-line with a pixel one clock from publishing and checks that nothing of that line comes out

Constraints

Do not add ports.