About Hardware

this page explains the structure of the hardware sub project, provides links to its resources, and outlines how to contribute to flipper one's electrical hardware development about hardware the hardware sub project covers electrical hardware development printed circuit boards (pcbs), antennas, schematics, and everything related to the electrical connections of chips, connectors, and processors the hardware team works closely with the mechanics team to ensure the electronics are compatible with the enclosure the hardware sub project consists of ✅ task tracker https //github com/orgs/flipperdevices/projects/9 ⚡ design files on altium 365 https //flipper 365 altium com/designs/folder a78c8d02 ea07 49e1 ac7a e84faa2af410 📁 github repository https //github com/flipperdevices/flipperone hardware 📚 docs 🔌 hardware section (you're here) 🧪 testing section docid\ rvvadwks7cxz 5srk9zm0 we'd love your feedback — look for tasks tagged help wanted in the task tracker, share your ideas in the comments, or contribute directly to the docs hardware sub project structure ✅ tasks tracker all hardware team tasks are tracked in the github project flipper one — hardware https //github com/orgs/flipperdevices/projects/9 there, you can see what the engineering team is working on and follow progress and discussions hardware board explainer some tasks are open to the community and marked with a help wanted label you're welcome to join the discussion on these tasks or submit your design proposals — just make sure to read the contribution guide docid\ nmkfutofpywq8fp40mnmx first ⚡ design files on altium 365 selected parts of flipper one's electrical design — schematics, pcb layouts, and bom — are hosted on altium 365 https //flipper 365 altium com/designs/folder a78c8d02 ea07 49e1 ac7a e84faa2af410 , the cloud collaboration platform for circuit design altium 365 hosts the latest version of the shared design files; you can view them in your browser without installing any software altium 365 web viewer interface click any project in the flipper one folder to open it in the web viewer five view tabs are available along the top sch — schematic pcb — 2d layout 3d — interactive 3d render draftsman — fabrication documentation bom — bill of materials how to view the design files the altium 365 web viewer lets you browse the project directly in your browser — no altium designer install required open the flipper one folder go to flipper one on altium 365 https //flipper 365 altium com/designs/folder a78c8d02 ea07 49e1 ac7a e84faa2af410 sign in with your altium or google account if you don't have an altium account, create one — it's free for viewing shared projects altium 365 sign in open a project click the project you want to inspect switch between views use the tabs at the top of the viewer to move between sch, pcb, 3d, draftsman, and bom altium 365 open project — schematic view inspect components and nets all views support pan and zoom, plus search and cross probing — click a component on the schematic to highlight it on the pcb, or select a net to trace it across the design how to export the design files the web viewer includes a download control whose available formats depend on the view you're in from the schematic, pcb, or bom views you can download a copy of the document for offline reference altium 365 web viewer download control the web viewer can export the entire project or individual derived files for offline reference open a project and click the downloads icon in the top right of the viewer a panel opens with project source files and derived files sections download the whole project in project source files, click the project entry to download all source files as a single archive or download individual files in derived files, pick what you need — gerber, assembly docs, pdf schematic, step, or bom for full info about the download feature, see altium's official web viewer documentation https //www altium com/documentation/altium 365/viewers/web viewer#downloading 📚 docs hardware documentation is split across two sections 🔌 hardware section (you're here) — port pinouts, modules, and subsystem references (wi fi & bluetooth, power, m 2, gpio) 🧪 testing section docid\ rvvadwks7cxz 5srk9zm0 — hardware verification procedures for each subsystem how to contribute the hardware sub project accepts contributions in two forms comments on open tasks for ideas, suggestions, and improvements, and edits to the docs for documenting hardware experiments, findings, or external module designs suggest your change as a comment on an open task ⚠️ contributions only — no flooding to keep collaboration productive, please keep comments on topic open tasks are for contribution related discussion only if you have an idea or concern, first turn it into a concrete contribution and share it as a comment on a task for general questions or discussions, you're always welcome to join the conversation on social media https //x com/flipper rnd or discord https //discord com/invite/flipper ! contribute a comment on an open task open tasks that need the community's help are labeled help wanted if you have ideas on how to improve the design, you can contribute by commenting on the task and attaching screenshots, schematics, or links pick a task in the hardware github project https //github com/orgs/flipperdevices/projects/9 , browse the open tasks and click the one labeled help wanted that you want to contribute to write your suggestion in the comments section, clearly describe your suggestion and attach a screenshot, schematic snippet, or a link to your design on altium 365 ensure your design is accessible for others to view good vs bad comment on a hardware task attachment size limit images 10 mb videos 100 mb click comment to submit we review all comments carefully! we may ask additional questions about your idea in the task thread, so please watch for github notifications in your email contribute to the docs if you've spotted an error in the hardware section, want to clarify something, or want to share your hardware experiments and findings, you're welcome to contribute by editing the docs the fastest way to jump straight to a page's source is the edit on github button on the live site — it opens the page's md file directly in the github editor contribute to the hardware docs for a longer change, fork the repository, make your edits on a new branch, and open a pull request read the markup example docid 43g4bbz9vhcuzq4hl9m1e page to learn the supported markdown and archbee syntax fork the repository go to flipperone docs https //github com/flipperdevices/flipperone docs and click fork in the upper right corner your fork opens on the public release branch — the production branch connected to the live site all your work happens here edit or create your md file in your fork, find the file you want to edit under docs/hardware/ , or create a new one in the appropriate subfolder follow the syntax shown on the markup example page — some markdown features behave differently in archbee (optional) add images if your change includes images, diagrams, or screenshots, upload them to docs/files/pics/ and reference them with a relative path !\[alt text]\(/files/pics/your image png "caption") use descriptive, lowercase filenames with hyphens (e g gpio pinout png ) keep images under 1 mb (optional) register the new page in archbee json https //github com/flipperdevices/flipperone docs/blob/public release/archbee json place it in the sidebar hierarchy (no deeper than two levels) — see how archbee json works docid 0qacsa2ejito2hwqfzgjh for the syntax it's okay to skip — we'll update the file after merging your pr create a branch and commit name the branch nickname/what changed (e g john/gpio module experiment ) keep commit messages concise — e g add gpio module pinout reference open a pull request from your branch to the original repository the target is pre selected to public release — leave it as is add a clear title and description, and ideally attach screenshots and a link to the related open task make sure allow edits by maintainers is ticked so we can apply small wording or syntax fixes directly to your pr once merged, archbee publishes your changes to the live site once your pull request is merged into public release , archbee automatically picks up the changes and rebuilds the live site at docs flipper net/one https //docs flipper net/one