this post was submitted on 17 Oct 2023
23 points (100.0% liked)
Cybersecurity
5672 readers
202 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub
Notable mention to !cybersecuritymemes@lemmy.world
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There is no standard for SoCs. If your board has an NXP i.MX6, you can't just desolder it and drop in a TI Sitara or nVidia Jetson.
Designing a PCB for an SoC isn't rocket science. There's nothing magical about the schematic or the layout, and usually the vendor gives out full design files for their eval boards that you can use as a starting point for your product. The silicon is the hard part. You can make your own Beaglebone clone right now for a few hundred dollars including parts and the board, assuming you are comfortable soldering smt. Making a fully open equivalent to the Beaglebone SoC is a nine figure endeavor at a minimum.
The reason you don't see hobbyist x86 SBCs is that Intel and AMD make customers sign a large pile of NDAs before sharing the documents you'd need to make your own. And in the case of Intel, you need to pay a 3rd party to provide you with a BIOS framework that obfuscates the ME firmware and other blobs (like memory training) so that even the board manufacturer doesn't have any idea what's going on in those hidden processors. (source: used to help develop x86 server hardware)