-
Notifications
You must be signed in to change notification settings - Fork 71
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
Most recent 'nrfutil device' programmer can't read included .hex firmware files anymore / This repo unsupported? #70
Comments
I suggest using the nRF Connect for Desktop to program the dongle.
The support ticket mentions nRF Sniffer for Bluetooth LE. |
Thanks! Yes, although it was for another protocol the issue hit was quite similar. It can be solved also by using a .zip version of the same hex file - so in principle also the .zip file versions could be added to this repository as an alternative to installing the desktop app. (I have this working now based on a .zip I got via a Thread Group Nordic contact.) |
There's another
Would that work for you? |
@Damian-Nordic Thanks, that's useful to know! Overall, my goal was to have a way to create the latest Nordic dongle sniffer easily without having to install anything else than the latest 'nrfutil' package with the CLI tool. (So, no further Windows or Linux desktop applications etc). It looked like this repo tried to do that but wasn't maintained to support the latest nrfutil programmer in an easy way. But maybe this isn't the goal of this repo. |
Firmware files are included in
.hex
format in this repo. The most recent programmer 'nrfutil device' can't read this format, it seems.Programmer version:
Error message:
The programmer does work for .zip firmware files though but these aren't included in this repo.
Answer from Nordic support is to use another source of the firmware: https://devzone.nordicsemi.com/f/nordic-q-a/114969/nrfutil-device-program-results-in-sdfu-firmware-file-extension-hex-is-not-supported
From which it sounds like this repo should be deprecated?
The text was updated successfully, but these errors were encountered: