Skip to content
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

Cannot authorize CJ on legacy fw - Hard fault detected #3892

Closed
marekrjpolak opened this issue Jun 4, 2024 · 2 comments · Fixed by #4535
Closed

Cannot authorize CJ on legacy fw - Hard fault detected #3892

marekrjpolak opened this issue Jun 4, 2024 · 2 comments · Fixed by #4535
Labels
bug Something isn't working as expected T1B1 legacy Trezor One

Comments

@marekrjpolak
Copy link
Contributor

Describe the bug
When trying to authorize CJ on legacy fw built from current main (both locally or in GH action), device shows Hard fault detected. Please unplug the device. On 1.12.1 or locally built firmware approximately from that time (March 2023) it works as expected.

I was testing it in desktop Suite with regtest and local coordinator.

@marekrjpolak marekrjpolak added the bug Something isn't working as expected label Jun 4, 2024
@onvej-sl
Copy link
Contributor

onvej-sl commented Jun 5, 2024

I discovered that this bug

  • was introduced in a0aa414,
  • doesn't only concern coinjoin, tests/device_tests/bitcoin/test_multisig.py, for example, causes the hard fault as well.

@prusnak prusnak added the T1B1 legacy Trezor One label Jun 5, 2024
@onvej-sl onvej-sl self-assigned this Jun 6, 2024
@onvej-sl
Copy link
Contributor

onvej-sl commented Jun 7, 2024

New discoveries:

  • The hard fault happens on this line.
  • It is caused by updating gcc-arm-embedded from 10.3.1 to 12.2.1.
  • Updating gcc-arm-embedded to 12.3.1 or to 13.2.1 didn't help.
  • Updating nanopb to 0.4.8 didn't help.

@onvej-sl onvej-sl removed their assignment Jun 14, 2024
@matejcik matejcik moved this to 🎯 To do in Firmware Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as expected T1B1 legacy Trezor One
Projects
Status: 🎯 To do
Development

Successfully merging a pull request may close this issue.

3 participants