-
Notifications
You must be signed in to change notification settings - Fork 201
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
USB Problem after writting final compiled firmware. #57
Comments
Just notice if I just leave the genca with default parameters (without adding anything) the key inside the firmware program is about 3 bytes less and it works. If I change any of the parameters on genca, it grows some bytes and stops working, |
Ok so its not size related, because now i rebuild the CA, gave it 18 more bytes (instead of 3) and its working. So it looks like some field cannot be filled on CA. |
Thanks for sharing this. The warning you get during compilation happen every time and shouldn't be an issue. Are you still programming using the bootloader? |
Yeah, but when it doesn't work, it breaks the USB bootloader (since it get 3 bytes error writting the firmware), then I use the programmer to reset the device back to the bootloader. I will check some more parameters on |
I think I get the same problem. Did you figure out what's causing this? |
Seens related to CA Cerfificate. I managed to change just the company name and got it working. Looks like its one of |
There might be just too much data with all the fields filled in the cert, causing the flashing to overwrite the bootloader page. Could you post what firmware (and cert) sizes worked and didn't work? |
The problem still persists and I cannot program firmware into the controller. However, according to Application note AN945, bootloader can be invoked with by connecting C2D pin to ground. There is no need for programmer to fix the bootloader if something goes wrong during flashing. |
Hi, I am running into the same issue. Did you find any solution ? The U2F is correctly is recognized with setup.hex:
I can do the setup:
I have the same warning during the link:
Then flashing the software reports errors. I do not find any documentation on how to get the error.
Thank you |
If you run efm8load.exe -t firmware.boot it'll give you the full download details, showing the errors.
|
I followed the steps in the wiki and I'm getting this error when compiling:
that leads to unrecognizable device:
I disabled the 4 features in the header as mention (to not corrupt the bootloader) and if I compile with ATECC_SETUP_DEVICE defined (so setup mode) the generated hex file works fine (the USB device works, and u2f client list devices perfectly). If I disable ATECC_SETUP_DEVICE I get the compilation warning and the device doesn't work.
I'm using a programmer to reset everything when it goes bad, since I cannot reset it in the normal way.
The text was updated successfully, but these errors were encountered: