Foundation Passport Official Thread

[satscraper]

~

I just checked using their comparison tool and it looks like both devices now use the ATECC608C variant. As for Passport Core, earlier production batches did indeed use the ATECC608B, and if I remember correctly, the very first units may have even used the ATECC608A during initial fabrication. But based on the latest info, it appears they’ve since transitioned to the ATECC608C

[satscraper]

Foundation released the firmware update for their Passport Core. Now the latest version is 2.3.8

There is still no MiniScript support in this release. It was promised in the first release following shipment of Passport Prime, but according to the latest information, that shipment hasn't started yet.

[satscraper]

I usually prefer not to rush into updating firmware instead waiting a couple of weeks to see if any potential issues are revealed and resolved. This time, the issue involved signing transactions in certain multisig setups.

The latest v2.3.9 release has fixed the relevant bug found in 2.3.8 and also improved error handling in Passport Core wallet.

[Lucius]

@satscraper, I recently tried to upgrade to version 2.3.9 through the SD card that came with the device, but as soon as the upgrade started, the following message appeared : Firmware update error: OSError, Info 5

I found an identical case on their support page, and as far as I can see, the user managed to upgrade the firmware only when he bought a new SD card. I must mention that the SD card works perfectly normally in the computer, but even when I formatted it, I still get the same error on Passport.

I currently have 2.3.5 firmware.

[satscraper]

@satscraper, I recently tried to upgrade to version 2.3.9 through the SD card that came with the device, but as soon as the upgrade started, the following message appeared : Firmware update error: OSError, Info 5

I found an identical case on their support page, and as far as I can see, the user managed to upgrade the firmware only when he bought a new SD card. I must mention that the SD card works perfectly normally in the computer, but even when I formatted it, I still get the same error on Passport.

I currently have 2.3.5 firmware.

Did you check the hash of the bin file on your SD card before proceeding with the update?

If yes, then I'm not sure what else to suggest in this case.

Previous to 2.3.5 v.2.3.2 - 2.3.4 did indeed have a bug that resulted in the "Firmware Update Error: OSError, Info 5" when users attempted the next update. However, they claimed that this issue was fixed in version 2.3.5:

That was the unintended bug introduced in 2.3.2, which is also still present in 2.3.4. The device is looking for a key to be present in the developer slot. Most users do not have this present, causing the freeze.

To resolve the v.2.3.2 issue they recommended downloading the developer's key first. However, they also warned that the following steps should only be performed after consulting with Foundation's staff:

So, I would recommend reaching out to them directly on their community site at community.foundation.xyz, where they seem to be quite active.

P.S. I'm still on v.2.3.5 myself, as I prefer not to update unless there's some security issue. One more question. What exactly happened to your device after it got stuck on this error? Were you able to get it back to working with version 2.3.5? Please keep the community updated.

[Lucius]

@satscraper, I'll answer your last question first - the entire failed update process only takes 1 second, after which an error message is displayed - and after that the device displays a message that it will continue to use firmware that is already on the device. So there is no fear that the device will reset or anything like that.

I didn't check the hash, and I don't think my error has anything to do with the developer key, because I have the same problem as the user in the link I posted in the previous post - he solved his problem with a new SD card.

What I'm going to try next is upgrading to 2.3.8 first, and if that doesn't work I'll look for some of my SD cards and try to upgrade with them.

[satscraper]

@satscraper, I'll answer your last question first - the entire failed update process only takes 1 second, after which an error message is displayed - and after that the device displays a message that it will continue to use firmware that is already on the device. So there is no fear that the device will reset or anything like that.

This is the best possible scenario among all that could happen.

I didn't check the hash,

It is not the wise choice as any download could potentially be corrupted or malicious. Corrupted bin file could cause update errors and should be ruled out as a possibility.

have the same problem as the user in the link I posted in the previous post - he solved his problem with a new SD card.

Would be nice if the new SD card assists you.

What I'm going to try next is upgrading to 2.3.8 first,

In my opinion, this is an unnecessary step that could add stress to the memory cells of your device. In fact, any flash action stresses memory, so I prefer to eliminate unnecessary actions. However, you're free to make your own decisions. Keep the community updated on your progress.

[Lucius]

The problem was with the SD card, because I was able to upgrade the firmware with another one without any problems. They obviously used to make much better quality things that lasted longer, because the SD card I used to update was from when Satoshi was just planning how to launch Bitcoin (2008).

~snip~
It is not the wise choice as any download could potentially be corrupted or malicious. Corrupted bin file could cause update errors and should be ruled out as a possibility.

You are right, I will check the hash in the future, and I checked it now and it was correct.