Embedded Board Checklist for IoT in Telecom: Raspberry Pi Compute Module 4 Carrier Board, RK3588 SBC, and PCB Carrier Board Pitfalls

Why This Checklist?

In my role coordinating embedded board sourcing for a small distributor, I've handled 200+ rush orders over the past eight years. Most of them came from clients who didn't have time to research, so this checklist is the one I use when the clock is already running.

It's written for IoT in telecom industry projects where "soon" means yesterday. Whether you're choosing a Raspberry Pi Compute Module 4 carrier board, an RK3588 SBC, or a custom embedded controller board, these are the questions I ask before I quote a lead time.

Six steps. Do them in order, or jump to the one that's keeping you up at night.

The Checklist

1. Decide If You Need a Compute Module or an All-in-One SBC

The first fork is form factor. A Raspberry Pi Compute Module 4 carrier board is the right call when you are designing a product, because the compute module plugs into your own PCB carrier board and you control the I/O. An RK3588 SBC is better when you need an embedded board that works out of the box and can handle a demo or a small deployment today.

People skip this step and buy a development board, then realize they're building a product on something never designed for production. That's how schedules die.

Checkpoint: Write down whether this is a one-off, a pilot, or a volume product. Your answer determines which embedded board is even worth considering.

2. Verify the PCB Carrier Board Mechanically Before You Trust a Photo

A carrier board is the embedded controller board between the module and the rest of your hardware. It has to physically fit your enclosure. It isn't enough for a board to say "for CM4" on the listing.

• Check connector type and orientation. Per Raspberry Pi's official Compute Module 4 documentation (raspberrypi.com/documentation/computers/compute-module.html), the module uses two 100-pin high-density board-to-board connectors; some carrier boards populate only one, and that changes which modules you can use.
• Check mounting hole locations. Standard holes are not always in the same place.
• Check component height on the underside. A metal standoff under an inductor can cause a short.

Checkpoint: Compare every mechanical drawing against your enclosure before ordering. If the vendor doesn't provide dimensions, ask for them. "It should fit" is not engineering.

3. Map Your I/O to the Board, Not to the Processor

The RK3588 chip and the CM4 can support a lot on paper. The board you're evaluating supports a subset. For IoT in telecom industry projects, I usually ask about a specific list:

• Dual Ethernet, ideally with PoE.
• M.2 slot for 4G/5G modules.
• SIM card slot.
• RS-485 or RS-232 for legacy telemetry.
• 9-36 V DC power input instead of 5 V micro-USB.

If your gateway needs dual Ethernet and the board has one, no amount of processor performance fixes that. If your device sits on a corporate network behind a firewall, you might not need PoE at all.

Checkpoint: List the connectors and electrical interfaces your deployment site actually has. Then ask the vendor if the board has them. "It should have" is not a technical quote.

4. Ask About Thermal Behavior, Not Just Performance

The step I end up debugging after the fact is thermal behavior. A spec sheet says "RK3588 SBC with four Cortex-A76 cores" and everyone assumes it can run at full speed forever. It can't unless the thermal design supports it.

In a telecom cabinet, ambient heat is real. If you put an embedded controller board in a 50°C enclosure with no airflow, the board will throttle, crash, or slowly cook itself. A carrier board that only performed in a lab test at 25°C is not a telecom-grade board.

Checkpoint: Ask for maximum ambient operating temperature, sustained clock speed, and whether the case needs forced airflow. If the vendor can't answer, treat it as a red flag.

5. Check Real Lead Time and Stock Before You Approve Anything

This is where my "time certainty" mindset kicks in. The perfect board with a 12-week lead time is worse than a good board available in five days when your project is due in three weeks.

In March 2024, a client called at 2 PM with a lab demo booked for the next morning. The CM4 carrier board we specified was $320. Overnight shipping was $180. The client paid it without flinching because losing the demo slot would have cost them a contract much larger than that.

I'm not saying rush fees are always worth it. I'm saying the fee buys certainty. "Probably in stock" and "probably will ship tomorrow" are not build schedules. Get stock status, availability date, and shipping commitment in writing.

Checkpoint: Ask if the item is stocked in the vendor's own facility or dropshipped from the factory. If it's dropshipped, add two to five days no matter what the website says.

6. Demand Proof, Not Promises

When a delivery date matters, ask for evidence. A photo of the actual unit, the revision number, a boot log, or a video of the board booting to the OS. It takes a supplier two minutes to send proof, and it saves you from opening a box of wrong revision boards.

If the vendor says "we have these in stock" but can't tell you whether it's rev 1.2 or 1.3, they probably don't have physical stock.

Checkpoint: Confirm that the carrier board includes the matching firmware and that the compute module variant is correct. For a Raspberry Pi Compute Module 4, the difference between Lite and eMMC modules changes the boot process. For an RK3588 SBC, ask which capacity of RAM and eMMC is fitted.

Notes From the Field

"Standard" Is Not Universal

The most frustrating part of this job is the word "standard." There is no universal PCB carrier board. An RK3588 SBC from one vendor can have different mounting holes, connector positions, and BIOS defaults from the next vendor. Always check the mechanical drawing.

If you're ordering a carrier board and a case from different vendors, don't assume they fit. Ask for dimensions.

Order One Extra Board

Looking back, I should have kept a spare CM4 carrier board in stock. At the time, it felt like wasted budget. Then a client's board arrived dead on arrival 36 hours before an install. The spare saved us.

If you're buying one board, buy two. If you're buying 50, buy 52. The cost is a few percent; the risk is a missed deadline.

Cheap Can Be Expensive at the End

I have mixed feelings about discount suppliers. On one hand, I've seen legitimate deals. On the other, I've seen a $20 discount turn into a five-day delay. If your project has a hard date, factor in the cost of being late, not just the unit price.

Your Situation May Differ

This checklist is based on my experience as a distributor and field engineer. If you're doing high-volume manufacturing with a fully custom PCB carrier board, your process will look different. I can only speak to off-the-shelf embedded boards and quick-turn projects.

The right embedded board for IoT in telecom isn't always the most powerful one. It's the one that fits mechanically, runs thermally, has the I/O you need, and can actually be delivered when you need it.