GitHubBecome a leader in the IoT community!
Join our community of embedded and IoT practitioners to contribute experience, learn new skills and collaborate with other developers with complementary skillsets.
Step 1 of 5
CREATE YOUR PROFILE *Required
Step 2 of 5
WHAT BRINGS YOU TO DEVHEADS? *Choose 1 or more
Connect & collaborate 🤝with other tech professionals
Learn & Grow 📚
Contribute Experience & Expertise 🔧
Step 3 of 5
WHAT'S YOUR INTEREST OR EXPERTISE? *Choose 1 or more
Hardware Design 💡
Embedded Software 💻
Edge Networking ⚡
Step 4 of 5
Personalize your profile
Step 5 of 5
Read & agree to our COMMUNITY RULES
- We want this server to be a welcoming space! Treat everyone with respect. Absolutely no harassment, witch hunting, sexism, racism, or hate speech will be tolerated.
- If you see something against the rules or something that makes you feel unsafe, let staff know by messaging @admin in the "support-tickets" tab in the Live DevChat menu.
- No age-restricted, obscene or NSFW content. This includes text, images, or links featuring nudity, sex, hard violence, or other graphically disturbing content.
- No spam. This includes DMing fellow members.
- You must be over the age of 18 years old to participate in our community.
- You agree to our Terms of Service (https://www.devheads.io/terms-of-service/) and Privacy Policy (https://www.devheads.io/privacy-policy)
By clicking "Finish", you have read and agreed to the our Terms of Service and Privacy Policy.
is the large carrier at the bottom standard?
It defines the main compute module. You then will need the larger carrier board to provide the I/O out to the real world.
https://en.wikipedia.org/wiki/Smart_Mobility_Architecture
so only the interface to the carrier board is standard
Yes – because the compute module could be anything, ARM, RISC, etc
ok is the carrier standard?
No – that can be designed to fit the specific requirements. You want GigEthernet – you put that on the carrier. You don’t want HDMI – don’t include it.
While companies will supply standard Dev kits with a carrier, it allows for the flexibility to then design your own.
For example, several of my clients have designed systems based on the BeagleBone Black. They didn’t want to use an actual BBB because:
– It was the wrong physical shape for their design
– They wanted to add a Cell Modem directly on the board – not attached by USB cables
– They wanted to change the size of the eMMC
– They didn’t want the USB port
– etc
So even for something as common as the BBB, people need to modify the design.
With SMARC, you can design the carrier to your physical requirements, the find a compute module that fits your processing needs. This then also gives the flexibility to upgrade the processing as the needs change.
I realise that now, im not thinking wide enough basically. I see how the interface and the credit card thing become the standard.
In PICMG and SGeT standards (SMARC, COM Express, COM-HPC), the modules are standard but the carriers can be customized. As you point out, the interface and pinout is specific to a module specification. Your custom carrier plugs into that.
Yeah linux applications are huge
but looking at this carrier they are not so foreign
CONTRIBUTE TO THIS THREAD