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

build/logitacker_aprdongle.uf2 version v0.1.4-beta appears to be corrupted #10

Closed
fraabye opened this issue Aug 23, 2019 · 4 comments
Closed

Comments

@fraabye
Copy link

fraabye commented Aug 23, 2019

This binary does not appear to be working with the April Brother dongle as the v0.1.3 did.
Steps to reproduce:

  1. Connect April Brother nRF52840 Dongle as removable drive NRF52BOOT.
  2. Copy logitacker_aprdongle.uf2 to the mounted drive.
  3. Expected outcome, a disconnected device / reflash, does not happen and the drive NRF52BOOT drive stays mounted.

The dongle has been tested successfully with the v0.1.3 build afterwards.

@mame82
Copy link
Collaborator

mame82 commented Aug 23, 2019

I re-tested the firmware, just now, and can't reproduce the issue.

File used was the on this one: https://github.com/mame82/LOGITacker/releases/download/v0.1.4-beta/logitacker_aprdongle.uf2

The firmware in use before flashing v0.1.4 was v0.1.3, too.

@mame82
Copy link
Collaborator

mame82 commented Aug 23, 2019

Additional note: The dongle fails to reboot after flashing.

Behavior observed:

  1. Put dongle in bootloader mode (hold button while plugging to host)
  2. Copy firmware to NRF52BBOT
  3. Dongle LED starts blinking while flashing
  4. NRF52BOOT mount disappears and dongle stops blinking (flashing finished), but doesn't reboot
  5. After re-plug of the dongle, LOGITacker boots as intended

@mame82
Copy link
Collaborator

mame82 commented Aug 23, 2019

Question:

Could it be that you accidentally copied the logitacker_aprdongle.hex file instead of the UF2 one, from the build directory?

@fraabye
Copy link
Author

fraabye commented Aug 24, 2019

It turned out to be a proxy mangling the firmware during download. After re-downloading it (again) using a direct connection it works as expected. Sorry for the inconvenience!

@fraabye fraabye closed this as completed Aug 24, 2019
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

2 participants