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

nk3xn alpha bricks lpc55 A and C #112

Closed
freswa opened this issue Nov 21, 2022 · 11 comments
Closed

nk3xn alpha bricks lpc55 A and C #112

freswa opened this issue Nov 21, 2022 · 11 comments

Comments

@freswa
Copy link

freswa commented Nov 21, 2022

Just flashed the file alpha-nk3xn-lpc55-v1.2.2-alpha.opcard.0.2.0.oath.0.3.0.sb2 via nitropy nk3 update alpha-nk3xn-lpc55-v1.2.2-alpha.opcard.0.2.0.oath.0.3.0.sb2 onto a 3A NFC and a 3C NFC. Update went up to 100% and after a few seconds a critical error occurred.
Another timeout(?) later the application quitted.

Both, the 3A and the 3C aren't even recognized anymore. dmesg reports

[  +6,892544] usb 4-2: device descriptor read/64, error -110
[ +15,570511] usb 4-2: device descriptor read/64, error -110
[  +0,239442] usb 4-2: new full-speed USB device number 82 using xhci_hcd
[ +15,546919] usb 4-2: device descriptor read/64, error -110
[ +15,573089] usb 4-2: device descriptor read/64, error -110
[  +0,106692] usb usb4-port2: attempt power cycle
[  +0,406841] usb 4-2: new full-speed USB device number 83 using xhci_hcd
[  +0,901844] usb 4-2: Device not responding to setup address.
[  +0,204628] usb 4-2: Device not responding to setup address.
[  +0,207172] usb 4-2: device not accepting address 83, error -71

lsusb hangs until I remove both keys.

@freswa
Copy link
Author

freswa commented Nov 21, 2022

Debug Logs:
3A_nitropy.log
3C_nitropy.log

@daringer
Copy link
Collaborator

daringer commented Nov 21, 2022

oh, this does not sound good, I've removed the flashable release-files to first investigate what is wrong here, we'll give you further information asap

@daringer
Copy link
Collaborator

Hey @freswa ,
we would like to replace your bricked device(s), please write support (at) nitrokey (dot) com and we'll clarify the details

@freswa
Copy link
Author

freswa commented Nov 22, 2022

As far as I understand these devices still have a working bootloader, but as we access the bootloader via application code and the application is bricked there is no easy way to flash anymore, is there?
Also I could pry them open to solder/attach something or even add a little switch to Pio0_5 to make the bootloader accessible if that's possible?

@freswa
Copy link
Author

freswa commented Nov 22, 2022

With the help of @daringer I managed to unbrick both devices. Will post a little guide later.

@freswa
Copy link
Author

freswa commented Nov 22, 2022

Personal note, not related to Nitrokey in any way, ymmv!

So a little guide for anyone who comes here, bricked their NitroKey 3A or 3C and would like to fix it themselves. One note regarding the early 3C cases: It's nearly impossible to reassemble them with the early version of the 3C casing. You can check your key for the version. If the groove on the side of the key is a waveform you have the early version. If it's straight you're in luck.

  1. Pry open the case. A good starting point is left and right of the USB connector. Be careful, don't use excessive force. The two sides are not only connected but there is a tiny (ribbon) cable for the touch button which is glued to the upper side. If that's ripped off you'll be out of luck
  2. We have to short the bootloader pin BL to GND like shown in the two pictures below.
    3A
    3C
  3. While shorting BL, insert the stick.
  4. Flash with nitropy

@freswa freswa closed this as completed Nov 22, 2022
@comio
Copy link

comio commented Nov 22, 2022

Why is this bug closed?
Is the issue understood?

Thanks

luigi

@freswa
Copy link
Author

freswa commented Nov 22, 2022

@comio Yes, the firmware files are offline, the problem has been identified, both devices have been recovered and an updated firmware will be released soon hopefully.

@comio
Copy link

comio commented Nov 23, 2022

Hi @freswa and @daringer,

can you provide any details?
Which was the issue exactly?

ciao

luigi

@szszszsz
Copy link
Member

Hi @comio!
Still working on it. Let me reopen this ticket for now.

@szszszsz szszszsz reopened this Nov 23, 2022
@daringer
Copy link
Collaborator

#116 fixes this, to be more precise this one: eb0ae22

release incoming, currently in internal testing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants