-
Notifications
You must be signed in to change notification settings - Fork 30
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
Is it possible to install and use the firmware without yocto? #20
Comments
You can compile the original emulator from trezor to test the firmware. The pitrezor specific modifications take care of the enabling the usb gadget mode, the gpio for switches and i2c/spi for display. If you just enable the emulator without the pitrezor option, you will get the same emulator as trezor is using to test and you can run it on any linux. However, in that mode, the usb is replaced by a udp protocol to communicate. |
@heneault I want to run the latest trezor firmware with the latest trezor suit to get the benefits of all new available trezor model t functionalities. Will I be able to achieve that using the official emulator that trezor provides? Also, want to enable hardware accelerated number crunching and if any other trezor firmware related features on the pi zero alongside enabling one of the usb ports as host to connect it to PC and run trezor suit also. How should I proceed to achieve this? Just wanna have all the trezor firmware functionalities and security features by leveraging the pi hardware as much as possible. I just don't need the buttons and i2c display because I want to use the emulator for those inputs. |
for the model t I dont know if this is possible |
So for model one firmware? how to do what I mentioned above with the model one firmware? |
Hello,
I do not have much knowledge about the trezor firmware. But is it possible to somehow install the firmware on a normal linux distribution of my choice rather than installing it with an yocto base and kernel? Please let me know in details.
Thank you.
The text was updated successfully, but these errors were encountered: