PCB version control

Mar 24, 2025 Last reply: 1 year ago 21 Replies

Well the newer firmware could handle both revs of course, but our image was built on the older firmware which knew nothing of this newfangled 1.4 tin.

And the new firmware only came with a new kernel, and new userland software stack that was incompatible with our driver and application, so we had to knife'n'fork the new firmware into the image as the least worst solution.

And, whats even more annoying, was that we'd done a bulk order for the Pi3B+ to avoid this sort of thing, but half the delivery was delayed by 12 months over the pandemic parts shortage.

End moan :)

Quite. Fortunately our customer is somewhat less fussy then the US DoD in that respect, though they do rather expect the thing to actually work.

Our main objective was to avoid rewriting our application to use a different kernel API at that point in time.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required