-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hardware Design #655
Comments
Hey there. Have you already looked at the files in doc directory? |
Sweet. But this directory does not contain design sources. |
Re: license. All files in this repository are published under the LICENSE file in the root, unless explicitly stated otherwise. Which format would you like to see it in? |
Yes, that would be greatly appreciated. |
I'll reopen to post here an update once we publish the hardware repo with all the sources. |
Any update for this, and can you also post gerber files for pcb? |
sorry i'm not working on the hardware anymore but @jadzeidan does. |
Any update on this? |
cc @jadzeidan |
It seems, the dev is pretty inactive. No reply when tagged last time as well #655 (comment) Any others from the team can provide with the resources? |
@mdhz apologize for the delay. I just need to check what we can publish exactly and will get back to you soon. |
Ah ok. Will wait. |
Hey @mdhz, sorry again to keep you waiting. The current Gerber files we have are for mass production and can't easily be used for one to create their own device (for example the OLED has a modified FFC so it's not an off-the-shelf part). We could make new Gerber files that makes it easier for DIY builders to make their own device (such as being able to use an off-the-shelf OLED) and it could also have a slightly different form factor, so malicious actors cant use it to produce exact copies of the PCB that is hard to distinguish from an original device. But this would take some time. What do you you plan to do specifically? If you want to load your own firmware onto the device, we would be happy to send you a developers version of the device. Just email [email protected] and we can help you from there. |
Hey, no worries. I was planning to make my own device since I've tried it with Trezor One already as it was pretty easy as gerber files were readily available. |
Yes, this is something I would like to do as well, publish a DIY version of the gerber files along with a 3D printable case so people can make their own device. Resources are tight now so it probably wont be available soon but I'll keep this issue updated about any progress :) |
Oh OK :) |
Should we close this issue? |
Still no DIY gerber files? If no, then yeah close it. |
If you have the source files, you can generate the gerber files. |
No update since the last comment. So yes we can close the issue and re-open if there is any progress. |
This is not how issues work 😹 Just leave it open until done so others can find it, or close it if there is no more interest. |
Also waiting for this to be released! |
For anyone wanting to run their own firmware on a Bitbox02, check out #1157 I'll try use my ChipSHOUTER to get the MCU back into a debuggable state, that should let me re-flash firmware with my own keys, I'll update via the email and issue linked above. Aside from that I'd very much like to build my own device, another idea I had was to manually re-work the MCU (ATSAMD51J20A) from the board, that would mean de-soldering the MCU and replacing it with an untouched new MCU. @jadzeidan is the PCB epoxied? |
Hi,
Where can I please find the source design of BitBox 02?
Is it open source hardware licensed under Creative Common International 4.0?
The text was updated successfully, but these errors were encountered: