-
Notifications
You must be signed in to change notification settings - Fork 93
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
DAPLink source for nrf52840-mdk-usb-dongle #106
Comments
Well I found at least this PR with some other nrf52840 devices ARMmbed/DAPLink#1015 - Nordic 52840 dongle and XIAO BLE, no nrf52840-mdk-usb-dongle there though. |
Second this |
@caizelin is the source for nrf52840-mdk-usb-dongle's DAPLink firmware closed and thus not provided? If not, could it be shared, much appreciated. I have power profiler board and nrf52840-mdk-usb-dongle attached to a target device. The dongle flashes firmware onto the target device and the power profiler board makes measurements after. Sometimes the dongle does something on its pins, which makes the power profiler board to burn (the issue isn't present when I remove the dongle). This is why I need the source code, to customize it for my case... Edit: Justifying the my request for access to source code. |
Hello @fanoush and @h0m3us3r , you can check again ARMmbed/DAPLink#1015 . We have been working together with the maintainers to add support for Makerdiary's nrf52840-mdk-usb-dongle. You can check it out and test it how it works. I am already using it in manufacturing process for our flash programmers. And now you can build the DAPLink firmware by yourself :) |
Hello, I'd like to rebuild https://github.com/makerdiary/nrf52840-mdk-usb-dongle/blob/main/firmware/daplink/daplink-nrf52840_mdk_usb_dongle-v0258.uf2 from source
Found your fork https://github.com/makerdiary/DAPLink but it only contains commit for your Pitaya-Link board. Can you make your patches for nrf52840 MDK dongle available?
Also looks like the pitaya board was merged upstream ARMmbed/DAPLink#896 but can't find MDK dongle upstream.
The text was updated successfully, but these errors were encountered: