Getting up and running with the Raspberry Pi Compute Module 4

Given how easy it is to get the board version of the Raspberry Pi 4 up and running, I figured that getting started with the compute module would be a walk in the park.  Not so.  The Compute Module 4 (CM) and Compute Module 4 IO Board are designed for more industrial usage, so there are more knobs and switches if you will.

I hope I can save you some time.  

Main caveats

  • The USB host on the Compute Module 4 IO board are disabled by default.
  • The MiniUART is disabled by default
  • Bluetooth is disabled by default
  • The SD Card only works for Lite (no eMMC) models of the compute modules
  • As an aside, Compute Modules dissipate heat less than Raspberry Pi boards, so some level of at least passive cooling will be needed.  It's a good idea to at least add heat sinks to the CPU and other components before proceeding.
So there are two main tasks ahead:
  1. Imaging the eMMC or SD Card
  2. Gaining terminal or desktop access

Flashing your module

If you have a Compute Module 4 Lite (no eMMC), this job is easy, just follow the usual instructions for writing an OS image onto an SD card on your PC.  Otherwise, you'll need to do the following, officially described here:
Start with your module installed on the IO board but no power applied:
  1. Add a jumper to J2 (labeled "Fit Jumper to disable eMMC Boot"). 

  2. Install RpiBoot utility
    1. Windows Installer
    2. Mac and Linux instructions
  3. Connect a micro-USB cable to your Linux, Mac, or Windows PC
  4. Apply power to the IO board
  5. Run the installed RpiBoot utility - at this point your module's eMMC should mount as a storage device on your PC
  6. Write a raspberry pi OS image to that drive, per the usual instructions (TL;DR: install and use the Raspberry Pi Imager utility from here).
At this point your module would theoretically boot, but don't disconnect your cable yet.  If you reboot now, the USB ports won't function and the bluetooth and TTYs are even disabled, so unless you happen to flash an OS image that already has your network and SSH already setup you won't be able to interact with the module yet.

Enabling USB

After writing the OS image, you should see in the newly written drive a config.txt in the boot folder.  Edit this file and add this line to the end:
    dtoverlay=dwc2,dr_mode=host

After this, be sure to unplug your power and your Micro USB cable, remove the J2 jumper, then plug in power.  If you have a screen and keyboard attached, you should be able to login (pi\raspberry) and run sudo raspi-config to connect to your network, enable SSH, and whatever you might have planned. 

If you are considering a custom Compute Module 4 board, be sure to read the datasheet. 

Happy compute moduling!

Comments

Post a Comment

Popular posts from this blog

Don't Repeat Yourself... Really!

...And I hope that someday That you, you people will all have the chance To read The Helping Friendly Book And experience the wisdom Of the great, the great and knowledgeable Man who wrote The Helping Friendly Book  Because he is, the great and knowledgeable He is the one, the only author of The Helping Friendly Book He is the man The great man The only, the special His name is The author of The Helping Friendly Book He is the great The knowledgeable, the one and the only The great, the knowledgeable Person who wrote The Helping Friendly Book His name could only be The one, the only, the only, the special The author of The Helping Friendly Book... -Excerpt from Icculus by Phish There are few mantras that are as universally agreed upon by Software Engineers as Don't Repeat Yourself or DRY.  It rings deeply and globally true that any form of code duplication is at best a compromise, at worst, an abominable trap.  Writing and maintaining...
Read more

Enough software patent madness!

Say patent, and one might get a nostalgic tear in their eye as they envision a brave garage inventor, who, protected by his patent, earns what's due him thanks to legal protection against large greedy corporations. Enter reality. Now picture large corporations able to easily crush or control small businesses. Picture large companies being relentlessly attacked for money even though such companies have made every effort to respect other's claims. Picture an environment where anyone wishing to innovate is all but unable to do so because such effort will invariably step on an almost infinite and unknown set of patent "toes". To make things worse, there are those that are pushing for even more liberal patent laws , such as first-to-file, rather than first-to-invent. Something must be done to stop this! Patents are ruining the software industry and causing tremendous indirect damage to our country! Software shouldn't even be patentable. Patent law prohibits the...
Read more

Virtual Appliances... poodoo

What I wish to address is this: "With the rise of virtualization, applications will transform into virtual appliances. Virtual appliances simplify application deployment by delivering the complete software stack—from OS to the application—as a single, integrated unit." -SDTimes Web Seminar Abstract Lest I be seen using VMs and am accused of being hypocritical: Virtualization is great for configuration testing. There is no better way to test against Oracle or Windows 98 without having to install such icky things than a VM. "Virtual Appliances", however, are a different story. Though they may “seem” exciting, and may be a practical solution given today’s technology and today’s problems, I find the trend disturbing. Why? ...Because a) the entire approach is grossly inefficient; and b) this is just another chapter in the long history of industry repetition. Setting aside the inefficiency aspect for a moment, isn’t this form of “run anywhere” virtualization exactly...
Read more