-
Notifications
You must be signed in to change notification settings - Fork 12
Loading fails for Nano S Plus on Mac #20
Comments
Manifest generated by
|
Indeed, known difference between 1.1.0 version and others: a new flag needs to be defined. |
About the other difference: one device has most likely already installed a "custom CA" that allows bypassing the usual screens and warnings for custom apps. |
It might be. Can't answer for sure because just don't remember all the details. My feeling is that all I did was quick setup of fresh device directly from the device - set PIN and install 12-word seed phrase (this one: "equip will roof matter pink blind book anxiety banner elbow sun young"). I'll try to reset the device and try to reproduce device setup steps. |
After reset and configuration, device started asking about unsafe manager, so seems I had custom CA installed. |
Is your |
|
Just for information: I've updated the other device to firmware 1.1.0, and it started triggering the same error code - 6512. |
+1, I updated |
Hi, could I get a link to your app so I can reproduce the problem? |
Thanks @williamrobertson13 |
That did the trick 😄, I guess I wasn't pulling in the most up-to-date version of |
Strangely enough, with
|
Actually, updated |
The problem now is that the |
Solved issue with Nano S Plus - it was caused by the updated |
wait which version of protobuf do we need, 4.xx or 3.20.xx? My build is finishing but it stops are
|
Nvm, looks like case sensitivity is the issue: |
I'm using a modified
cargo-ledger
(see this PR) to load the firmware to Ledger Nano S Plus. I'm trying to do this on two different Mac's with ARM CPU. On one system, everything works fine, but the other shows the following error:Systems configures identically (as far as I can see), the only difference is the firmware versions of the Nano S Plus device.
Working one has:
Secure element - 1.0.2
Microcontroller - 4.02
Bootloader - 3.12
Failing one has:
Secure element - 1.1.0
Microcontroller - 4.03
Bootloader - 3.12
Another observed difference is that failing system asks for "allow unsafe manager", while working one goes directly to deletion of existing app and loading a new one.
Any ideas what could be the cause of the issue?
The text was updated successfully, but these errors were encountered: