Arducam EK037 video streaming fails with 'skip frame, mismatched length' error

Hi everyone, I’m having trouble getting my new EK037 kit up and running. Hoping someone here has seen this before.

Here’s what I’m working with:

  • Product: EK037 – Arducam 2.2MP Mira220 RGB Global Shutter USB3.0 Camera Evaluation Kit
  • Board label: UC-B10, Rev A
  • Environment: Windows 11 laptop, using the Windows GUI (Shield UI)

I’ve been following the quick start guide and loaded the config file (EK037_Mira220_124MHz_RAW.zip) through the Windows GUI. The config loads without any errors, but when I try to get a video stream, nothing shows up. The only thing I see is this warning spamming the log:

Warn: skip frame, mismatched length

I’ve tried both of the most recent Shield UI app versions — same result. No video at all, just that warning.

Here’s a screenshot of what the Shield UI looks like on my end:

Shield UI screenshot

Anyone have any ideas? The quick start guide I’m referencing is here: 2MP Mira220 USB3 Evaluation Kit - Arducam Wiki

Thanks for the detailed report and the screenshot. That’s helpful.

Before we dig deeper — just to rule out something simple: after loading the config file, did you click the “play” button in the Shield UI? I know it sounds obvious, but sometimes the UI needs an explicit start after config loading. Does anything at all show up in the video pane when you hit play, or is it just the warnings in the log?

Yeah, I did click the play button — multiple times actually. Still nothing. The video pane stays completely blank/black, and the log just keeps repeating that same warning over and over:

Warn: skip frame, mismatched length

No frames, no partial image, nothing. Here’s another screenshot of the current state:

Shield UI state

I should mention I’m on a Windows 11 laptop, and I’ve tested with both of the latest Shield UI releases just to be sure it wasn’t a version-specific issue. Same behavior on both.

Got it, thank you for confirming. The “skip frame, mismatched length” warning typically means the host is receiving data that doesn’t match the expected frame size — so the driver is discarding frames rather than displaying garbage. It could be a USB bandwidth issue, a firmware mismatch, or something in the configuration pipeline.

Since you’re getting the same result across two Shield UI versions and the config loads cleanly, I think remote debugging would be the fastest way to narrow this down. I’ve sent you the remote support details through private message — please check your inbox and send over your AnyDesk ID when you’re ready. I’d like to take a look at the live device enumeration and USB descriptor data directly.