NRF52840 boards? #3

tmikaeld · 2020-01-31T14:15:29Z

Does the key need to be the specific Nordic NRF52840 devoper dongle or does the key only need to have the NRF52840 SOC on the dongle?

jmichelp · 2020-01-31T15:06:28Z

The main requirement today is the Nordic nRF52840 SOC.

The two development boards that Nordic made around their chip (the NRF52840-DK and the NRF52840-Dongle) are already supported but it's pretty easy to adapt the code to support a custom design around the Nordic chip. You need 1 button and at least 1 LED to be wired to the chip.

Supporting another chip than the Nordic is also possible but requires more effort.

tmikaeld · 2020-01-31T15:09:55Z

Seems great, unfortunately I know nothing of programming hardware.

But if someone else is interested, this dongle would be a great match for OpenSK:

https://github.com/makerdiary/nrf52840-mdk-usb-dongle

It has a really small form-factor and is available with a form-fit shell, I already made a suggestion to integrate OpenSK in their github.

brouhaha · 2020-01-31T18:54:18Z

Just FYI, the official Nordic nRF52840 dongle sells for $10, which is less than the price of the Makerdiary dongle. The design of the Nordic dongle is open. It doesn't come with a case, but if you have a 3D printer...

tmikaeld · 2020-01-31T21:04:53Z

@brouhaha I looked at having the shell printed, but the shell is much larger, less durable and doesn't have a ring to have it in a key-chain. Plus, the MD dongle size is smaller, which I prefer - I'm too used to the smaller form-factor of Yubikeys.

xiongyihui · 2020-02-01T07:06:11Z

I managed to get it work with https://github.com/makerdiary/nrf52840-mdk-usb-dongle.
We just need to change the IOs. As I don't have a jlink, I used a CMSIS-DAP debug adaptor with pyocd to flash the firmwares.
The steps are a little different.

By the way, I use gitpod.io to build the project.

Run curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh to install Rust
Run setup.sh

Change the pins of LEDs and Buttons at OpenSK/third_party/tock/boards/nordic/nrf52840_dongle/src/main.rs

// The nRF52840 MDK USB Dongle LEDs
const LED1_PIN: Pin = Pin::P0_04;           // not connected to a LED
const LED2_R_PIN: Pin = Pin::P0_23;
const LED2_G_PIN: Pin = Pin::P0_22;
const LED2_B_PIN: Pin = Pin::P0_24;

// The nRF52840 MDK USB Dongle button
const BUTTON_PIN: Pin = Pin::P0_18;
const BUTTON_RST_PIN: Pin = Pin::P0_03;     // not connected

const UART_RTS: Pin = Pin::P0_05;
const UART_TXD: Pin = Pin::P0_06;
const UART_CTS: Pin = Pin::P0_07;
const UART_RXD: Pin = Pin::P0_08;

Run board=nrf52840_dongle ./deploy.sh os to build Tock OS

The Tock OS firmware nrf52840_dongle.elf is at third_party/tock/boards/nordic/nrf52840_dongle/target/thumbv7em-none-eabi/release/

gitpod /workspace/OpenSK $ ls third_party/tock/boards/nordic/nrf52840_dongle/target/thumbv7em-none-eabi/release/
build  deps  examples  incremental  nrf52840_dongle  nrf52840_dongle.bin  nrf52840_dongle.d  nrf52840_dongle.elf

Run pyocd flash -t nrf52840 nrf52840_dongle.elf to flash the Tock OS into the dongle.
Run board=nrf52840_dongle ./deploy.sh app to build the OpenSK app

The app contains two parts padding.bin and cortex-m4.tbf at target/tab/
```
gitpod /workspace/OpenSK $ ls target/tab/
cortex-m4.elf  cortex-m4.tbf  ctap2.tab  padding.bin
```
Run pyocd flash -t nrf52840 --format bin -a 0x40000 cortex-m4.tbf and pyocd flash -t nrf52840 --format bin -a 0x30000 padding.bin to flash the app

cortex-m4.tbf should be written to the address 0x40000. padding.bin should be written to the address 0x30000.

mikejrh · 2020-02-01T14:45:52Z

Is it possible to program the NRF52840 USB Dongle as a security key without additional hardware ?

rmm200 · 2020-02-01T17:48:38Z

Google is presenting OpenSK as a tool for developers and hobbyists.
The Nordic Dongle costs about $10.
The associated hardware to program it costs roughly $1000, per installation guide.
Try to come up with a cheaper solution for us hobbyists. $1000 is more than I spent on my 3D printer.

brouhaha · 2020-02-01T18:19:54Z

There are a multitude of options for programming the nRF52, none of which cost $1000. The Nordic nRF52 DK board can be used, and sells for $40.

rmm200 · 2020-02-01T19:21:22Z

It looks like nRF Connect Programmer can do the job:
https://devzone.nordicsemi.com/nordic/short-range-guides/b/getting-started/posts/nrf52840-dongle-programming-tutorial
Maybe the install guide could reference this? All it shows are the very expensive JProbe accessories.

elfmimi · 2020-02-01T19:29:35Z

I tried RAYTAC MDBT50Q-RX and it worked.
https://www.raytac.com/product/ins.php?index_id=89

Note: you need to tweak pin settings for the led and the button. It would be safer to also change the pin for uart so that it won’t interfere with the reset pin.

rmm200 · 2020-02-01T19:58:24Z

It looks like the MDBT50Q-RX does not include a bootloader, so you also need a MDBT50Q-RX to do the programming? Sure beats anything JLink for cost though. The NRF52840 does appear to include the DFU Bootloader, so programming by USB is possible.

xiongyihui · 2020-02-02T02:04:07Z

If you have two nRF52840 MDK USB Dongle, you can use one as a CMSIS-DAP debug adapter with OpenOCD or pyOCD

See https://github.com/xiongyihui/mbed-CMSIS-DAP

rmm200 · 2020-02-02T02:10:35Z

Well that leaves open the question. Can you use the nRF52840 dongle bootloader to install OpenSK on itself, using just the one dongle - or does that destroy the bootloader? May be time to buy a second dongle...

elfmimi · 2020-02-02T03:16:42Z

I think it can be done. I mean, it should be possible to install OpenSK with ordinary bootloaders and without using any jtag/swd adapters.

xiongyihui · 2020-02-02T03:46:58Z

We can modify OpenSK/third_party/tock/boards/nordic/nrf52840_dongle/layout.ld to make Tock OS compatible with the nordic open bootloader.

MEMORY
{
  rom (rx)  : ORIGIN = 0x00001000, LENGTH = 124K
  prog (rx) : ORIGIN = 0x00030000, LENGTH = 704K
  ram (rwx) : ORIGIN = 0x20000000, LENGTH = 256K
}

MPU_MIN_ALIGN = 8K;

INCLUDE ../../kernel_layout.ld

rmm200 · 2020-02-02T06:22:01Z

Man - you are getting there! Glad I asked!
Now to just not lose track of this information...
And - Thanks!

MatchstickUK · 2020-02-03T15:38:43Z

Google is presenting OpenSK as a tool for developers and hobbyists.
The Nordic Dongle costs about $10.
The associated hardware to program it costs roughly $1000, per installation guide.
Try to come up with a cheaper solution for us hobbyists. $1000 is more than I spent on my 3D printer.

The larger nRF52840 DK board spec lists it as "comes with an on-board SEGGER J-Link debugger allowing programming and debugging both the on-board SoC and external SoCs through the debug out header" so could one of those be used to provide the required support to the dongle ?

jmichelp · 2020-02-03T15:46:22Z

Thanks all for your contributions.

Regarding JLink probes, multiple things:

If you're not using them for commercial use, check if you're not eligible for their EDU (or EDU mini) version which is more affordable.
Of course you can use other probes to program the dongle. JLink is the one that was already supported in Tock OS (and more specifically the tockloader tool) and it's embedded in the Nordic nRF52840-DK development kit. We're mentioning this as a tested/validated solution.

Regarding using another probe than the JLink, I tried a while ago with a Black Magic Probe and OpenOCD without success. I haven't tried with pyOCD instead. I'll give it a try and add documentation about it.

Regarding supporting the Nordic DFU bootloader, that's something we will indeed think about. Because it will also spare the cost of the Tag-Connect cable (even though one can also use a breadboard and press fit headers on the castellated holes for SWD).

Finally about supporting the nRF52840 MDK board, it's for sure possible but as mentioned in the review of the pull request, we would prefer the boards to be added directly to Tock OS instead of having to maintain patches for this. The patches we currently have in our repository are changes that are in the process of being upstreamed and we hope that we will soon be able to fully remove them from our repository.

Raboo · 2020-02-03T16:55:13Z

We can modify OpenSK/third_party/tock/boards/nordic/nrf52840_dongle/layout.ld to make Tock OS compatible with the nordic open bootloader.

@xiongyihui would this mean you can program the dongle with nRF Connect Programmer?
It would be super awesome if you could make a PR for Tock OS to also support nordic open bootloader.

rmm200 · 2020-02-03T17:08:24Z

Let me second the Super Awesome. Us low budget users will thank you forever!

xiongyihui · 2020-02-04T15:39:21Z

On nRF52840 MDK USB Dongle, we can install OpenSK without a debug adapter. See Get Started with OpenSK guide

I still can not get OpenSK with Nordic open bootloader directly. However, the open bootloader supports self-upgrade, so we can replace open bootloader with a UF2 bootloader, and then get OpenSK work with the UF2 bootloader.

tmikaeld · 2020-02-04T16:16:39Z

@xiongyihui Amazing! I'll start ordering a bunch :-D

gregvinyard · 2020-02-06T15:14:09Z

Regarding the nRF Connect Programmer, it looks like you need hex files. The build script creates elf files. Is there a way to convert elf to hex? Or modify the build script to output hex files?

MatchstickUK · 2020-02-06T15:23:04Z

@gregvinyard the Building OpenSK page https://wiki.makerdiary.com/nrf52840-mdk-usb-dongle/opensk/building/ covers using bin2hex.py and hexmerge.py to built a single .hex file to install via UF2 bootloader.

I'm guessing someone has already tried using the output of that with nRF Connect Programmer ?

gregvinyard · 2020-02-06T20:47:15Z

Thanks @MatchstickUK . Apparently I have a lot to learn, heh. I was able to convert the bin and tbf files to hex and flash them using nRF Connect Programmer, but OpenSK doesn't run. I didn't brick the dongle, I can flash again. No idea what I'm doing though. Time to do some more reading. :-)

dennisg · 2020-02-26T06:23:05Z

@sissaias yes I did: have a look at dennisg/OpenSK. After the generic installation instructions, run the flash_nrf52840_using_dfu.sh script and if all's well your dongle will have been programmed correctly

sissaias · 2020-02-26T20:03:58Z

@sissaias yes I did: have a look at dennisg/OpenSK. After the generic installation instructions, run the flash_nrf52840_using_dfu.sh script and if all's well your dongle will have been programmed correctly

Thank you will give it a try tonight.

@dennisg I am getting these errors:

WOPR ॐ ~/Projects/OpenSK:(9d15h10m|git@nrf52840_dongle_bootloader)
1264 ± ./flash_nrf52840_using_dfu.sh ✹
Compiling tock-cells v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/libraries/tock-cells)
Compiling tock-registers v0.5.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/libraries/tock-register-interface)
Compiling enum_primitive v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/libraries/enum_primitive)
Compiling tock_rt0 v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/libraries/tock-rt0)
Compiling nrf52840_dongle v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/boards/nordic/nrf52840_dongle)
Compiling kernel v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/kernel)
Compiling cortexm v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/arch/cortex-m)
Compiling nrf5x v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/chips/nrf5x)
Compiling capsules v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/capsules)
Compiling cortexm4 v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/arch/cortex-m4)
Compiling nrf52 v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/chips/nrf52)
Compiling nrf52840 v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/chips/nrf52840)
Compiling components v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/boards/components)
Compiling nrf52dk_base v0.1.0 (/Users/sissaias/Projects/OpenSK/third_party/tock/boards/nordic/nrf52dk_base)
Finished release [optimized + debuginfo] target(s) in 21.67s
text data bss dec hex filename
114176 1708 260436 376320 5be00 target/thumbv7em-none-eabi/release/nrf52840_dongle
make: objcopy: No such file or directory
make: *** [target/thumbv7em-none-eabi/release/nrf52840_dongle.hex] Error 1
cp: third_party/tock/boards/nordic/nrf52840_dongle/target/thumbv7em-none-eabi/release/nrf52840_dongle.hex: No such file or directory
./deploy.sh: line 59: declare: -A: invalid option
declare: usage: declare [-afFirtx] [-p] [name[=value] ...]
ERROR: File not found: target/tab/padding.bin
ERROR: File not found: target/tab/cortex-m4.tbf
Traceback (most recent call last):
File "/usr/local/bin/hexmerge.py", line 178, in
sys.exit(main())
File "/usr/local/bin/hexmerge.py", line 158, in main
ih = intelhex.IntelHex(fname)
File "/usr/local/lib/python3.7/site-packages/intelhex/init.py", line 90, in init
self.loadhex(source)
File "/usr/local/lib/python3.7/site-packages/intelhex/init.py", line 199, in loadhex
fobj = open(fobj, "r")
FileNotFoundError: [Errno 2] No such file or directory: 'target/dfu/nrf52840_dongle.hex'
Traceback (most recent call last):
File "/usr/local/bin/nrfutil", line 5, in
from nordicsemi.main import cli
File "/usr/local/lib/python3.7/site-packages/nordicsemi/main.py", line 52, in
from nordicsemi.dfu.dfu_transport_serial import DfuTransportSerial
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/dfu_transport_serial.py", line 53, in
from nordicsemi.dfu.dfu_trigger import DFUTrigger
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/dfu_trigger.py", line 48, in
import usb1
File "/usr/local/lib/python3.7/site-packages/usb1/init.py", line 61, in
from . import libusb1
File "/usr/local/lib/python3.7/site-packages/usb1/libusb1.py", line 199, in
libusb = _loadLibrary()
File "/usr/local/lib/python3.7/site-packages/usb1/libusb1.py", line 173, in _loadLibrary
return dll_loader('libusb-1.0' + suffix, **loader_kw)
File "/usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ctypes/init.py", line 364, in init
self._handle = _dlopen(self._name, mode)
OSError: dlopen(libusb-1.0.dylib, 6): image not found
Insert the dongle, make it go into DFU mode...
Traceback (most recent call last):
File "/usr/local/bin/nrfutil", line 5, in
from nordicsemi.main import cli
File "/usr/local/lib/python3.7/site-packages/nordicsemi/main.py", line 52, in
from nordicsemi.dfu.dfu_transport_serial import DfuTransportSerial
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/dfu_transport_serial.py", line 53, in
from nordicsemi.dfu.dfu_trigger import DFUTrigger
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/dfu_trigger.py", line 48, in
import usb1
File "/usr/local/lib/python3.7/site-packages/usb1/init.py", line 61, in
from . import libusb1
File "/usr/local/lib/python3.7/site-packages/usb1/libusb1.py", line 199, in
libusb = _loadLibrary()
File "/usr/local/lib/python3.7/site-packages/usb1/libusb1.py", line 173, in _loadLibrary
return dll_loader('libusb-1.0' + suffix, **loader_kw)
File "/usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ctypes/init.py", line 364, in init
self._handle = _dlopen(self._name, mode)
OSError: dlopen(libusb-1.0.dylib, 6): image not found
Okay, make it go into DFU mode one more time...
Traceback (most recent call last):
File "/usr/local/bin/nrfutil", line 5, in
from nordicsemi.main import cli
File "/usr/local/lib/python3.7/site-packages/nordicsemi/main.py", line 52, in
from nordicsemi.dfu.dfu_transport_serial import DfuTransportSerial
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/dfu_transport_serial.py", line 53, in
from nordicsemi.dfu.dfu_trigger import DFUTrigger
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/dfu_trigger.py", line 48, in
import usb1
File "/usr/local/lib/python3.7/site-packages/usb1/init.py", line 61, in
from . import libusb1
File "/usr/local/lib/python3.7/site-packages/usb1/libusb1.py", line 199, in
libusb = _loadLibrary()
File "/usr/local/lib/python3.7/site-packages/usb1/libusb1.py", line 173, in _loadLibrary
return dll_loader('libusb-1.0' + suffix, **loader_kw)
File "/usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ctypes/init.py", line 364, in init
self._handle = _dlopen(self._name, mode)
OSError: dlopen(libusb-1.0.dylib, 6): image not found
Traceback (most recent call last):
File "/usr/local/bin/nrfutil", line 5, in
from nordicsemi.main import cli
File "/usr/local/lib/python3.7/site-packages/nordicsemi/main.py", line 52, in
from nordicsemi.dfu.dfu_transport_serial import DfuTransportSerial
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/dfu_transport_serial.py", line 53, in
from nordicsemi.dfu.dfu_trigger import DFUTrigger
File "/usr/local/lib/python3.7/site-packages/nordicsemi/dfu/dfu_trigger.py", line 48, in
import usb1
File "/usr/local/lib/python3.7/site-packages/usb1/init.py", line 61, in
from . import libusb1
File "/usr/local/lib/python3.7/site-packages/usb1/libusb1.py", line 199, in
libusb = _loadLibrary()
File "/usr/local/lib/python3.7/site-packages/usb1/libusb1.py", line 173, in _loadLibrary
return dll_loader('libusb-1.0' + suffix, **loader_kw)
File "/usr/local/Cellar/python/3.7.6_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/ctypes/init.py", line 364, in init
self._handle = _dlopen(self._name, mode)
OSError: dlopen(libusb-1.0.dylib, 6): image not found
WOPR ॐ ~/Projects/OpenSK:(9d15h10m|git@nrf52840_dongle_bootloader)
1265 ±

dennisg · 2020-02-29T09:51:33Z

Hi @sissaias, I'm running this on linux, untested on OSX, sorry.

your root cause is this:

make: objcopy: No such file or directory
make: *** [target/thumbv7em-none-eabi/release/nrf52840_dongle.hex] Error 1
cp: third_party/tock/boards/nordic/nrf52840_dongle/target/thumbv7em-none-eabi/release/nrf52840_dongle.hex: No such file or directory
./deploy.sh: line 59: declare: -A: invalid option

which means that it cannot find objcopy used to generate the hex file.

A little bit further in the logs I see that when deploy.sh is run from the script, there seems to be a mismatch w.r.t. arguments fed into declare and lastly libusb-1.0 cannot be found.

I'm afraid I cannot help you to solve this since I do not have a mac for testing.

zappos23 · 2020-02-29T11:49:04Z

I had this problem on my MacOS too. Most probably it's due to old bash version not supporting declare option.
I think you could either removed the declare in the sh file or update your bash. Thanks

jmichelp · 2020-02-29T14:33:41Z

Portability issues should have been fixed. The deploy.sh script is gone.
If you're not using code from this repository I suggest you open an issue on the forked repository to tell them to update their fork

dennisg · 2020-03-02T20:33:31Z

Hi @jmichelp, I updated the fork, still untested but I will hopefully soon find time to do so; are you interested in knowing how to flash a regular nrf52840 dongle with your application without the use of expensive hardware? Do you care to help with your knowledge to fix the 'double flashing' ? I would really appreciate your input!

sissaias · 2020-03-02T21:35:30Z

Hello everyone

I upgraded bash as suggested now using @dennisg fork I am getting the follow request for j-link:

mlberlin · 2020-03-03T20:28:08Z

@dennisg awesome work! Many thanks! One small correction: the 1st argument of deploy.py in your bash script flash_nrf52840_using_dfu.sh should read app not os:

./deploy.py app --board=nrf52840_dongle

This probably also does away with your problem @sissaias.

jmichelp · 2020-03-03T21:44:24Z

@dennisg Of course we're interested :) I actually bought myself 2 makerdiary dongles so that I can experiment/test.
I'll do my best to help merging your contribution to the main repository.

dennisg · 2020-03-04T07:27:36Z

Yes, I've now started _really_ looking at the changes in master and indeed we should build the `app` instead of the `os`. Thanks Adriaan. Here's what I think we should fix to get flashing over DFU working again (it's probably not that much): - Within the `deploy.py` in `install_elf_file` the padding is installed at address `0x30000` using tockloader just before flashing the app itself; we should be able to generate a hex file that contains that padding and that hex file should be merged with the os and app hex-es. - it might be best to create a completely separate target (e.g. nrf52840_dongle_dfu) that incorporates these changes because we deviate quite a lot from the regular target - fix the issue that we have to flash the os twice, maybe we just flash the padding, os and app hexes separately? downside is that we then have to reset the dongle 3 times during the process. I'll try setting this up as soon as possible

…

On Tue, Mar 3, 2020 at 10:44 PM Jean-Michel Picod ***@***.***> wrote: @dennisg <https://github.com/dennisg> Of course we're interested :) I actually bought myself 2 makerdiary dongles so that I can experiment/test. I'll do my best to help merging your contribution to the main repository. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAB3P3O7BKJYFQA7IZ3KFODRFV23TA5CNFSM4KOHWZR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENVI27Y#issuecomment-594185599>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB3P3OC5LKRH7DODJCNJZDRFV23TANCNFSM4KOHWZRQ> .

dennisg · 2020-03-05T10:53:59Z

@jmichelp Okay, I moved as much as possible/ seemed sensible from the bash script to the deploy.py and made it possible, using a --dfu flag, to bypass tockloader completely and only generate the hex files. Also updated the Tock OS main.rs for the nordic dongle (in most certainly a very dirty way, I'm no Rust developer) to set the table_offset_vector during compile time. Please have a look, sigh, do a face-palm and then point me to a better way to do it. thanks!

dennisg · 2020-03-05T11:49:55Z

This is an overview of the memory layout if you load the hex files in nrf programmer.

1579: add set_vector_table_offset() r=alevy a=xiongyihui when using a bootloader, tock os may need to relocate interrupt vector table, then use this function to do that. See the discussion at google/OpenSK#3 ### Pull Request Overview This pull request adds `add set_vector_table_offset` function to relocate interrupt vector table. ### Testing Strategy TODO ### TODO or Help Wanted N/A ### Documentation Updated - [x] Updated the relevant files in `/docs`, or no updates are required. ### Formatting - [x] Ran `make formatall`. Co-authored-by: Yihui Xiong <yihui.xiong@hotmail.com>

sissaias · 2020-03-08T20:57:25Z

@dennisg I have to say after spending days on OSX, I decided to do it on Linux. Your flash script worked. The key now works fine. Thanks everyone for your help next move to find somewhere to print a case

ejeyaseelan · 2020-03-09T04:44:16Z

it would be helpful to have an updated write up on how to program this onto a new dongle with factory defaults on windows, linux and macos.

I am on windows and I got the files compiled in gitpod.

I have the nrf desktop connect app, not sure whats the best to proceed without frying my dongle.

thx

jmichelp · 2020-03-09T18:18:15Z

Please be patient. I'm working on integrating all of that nicely into the main repository and the deploy.py script.

At the end, one should be able to flash OpenSK firmware using:

Segger JLink (it will leverage tockloader)
OpenOCD (it will also leverage tockloader)
pyOCD
Nordic DFU
No programmer (it will only produce a HEX file which will be handy for continuous integration and testing purpose or if a flashing method is not supported).

Update the example-app branch

jbalius · 2021-11-25T11:07:07Z

Has anyone tried
Minew C2-7001 Nordic NRF52840 Dongle?

https://aliexpress.com/item/4000127809241.html

jmichelp · 2021-11-25T11:10:11Z

No we haven't.
They say it's a buttonless dongle though which is an issue for FIDO2 because we need the button to validate user presence.

jbalius · 2021-11-25T12:14:17Z

No we haven't. They say it's a buttonless dongle though which is an issue for FIDO2 because we need the button to validate user presence.

Actually it has a button. I have picture and schematics of it:

MS04SF7_SCH_V1.0_a.pdf

As I understand they are suggesting it can be used without a button for some applications.

jmichelp · 2021-11-25T13:02:00Z

So, according to the schematics you provided, the board is equivalent to the nRF52840 Dongle from Nordic. Both LEDs and buttons are wired the same. Like on the Nordic dongle, one button acts as a reset button and the other one will be used for User Presence.

You should be able to flash OpenSK using the board definition nrf52840_dongle_dfu (simply follow the instructions we have for the Nordic nRF52840 dongleflashing over DFU and you should be fine).

wezm · 2023-02-01T06:27:17Z

I tried RAYTAC MDBT50Q-RX and it worked. https://www.raytac.com/product/ins.php?index_id=89

Note: you need to tweak pin settings for the led and the button. It would be safer to also change the pin for uart so that it won’t interfere with the reset pin.

@elfmimi I have one of these, did you publish your tweaks anywhere? I can work out the changes to the pins myself but figured if you've already done it I would ask first.

elfmimi · 2023-02-02T13:55:54Z

No, I haven't. I'll try to dig it out. pls wait few days.

elfmimi · 2023-02-03T15:01:12Z

Here you are. @wezm
https://gist.github.com/elfmimi/e8ffd589fc7ca3794641803700d734aa

wezm · 2023-02-03T22:48:39Z

Here you are. @wezm

Wonderful, thank you.

jmichelp mentioned this issue Jan 31, 2020

Why Nordic? #2

Closed

tmikaeld mentioned this issue Jan 31, 2020

OpenSK compatible? makerdiary/nrf52840-mdk-usb-dongle#16

Closed

xiongyihui mentioned this issue Feb 2, 2020

add new board - nRF52840 MDK USB Dongle #6

Closed

2 tasks

xiongyihui mentioned this issue Feb 4, 2020

add set_vector_table_offset() tock/tock#1579

Merged

2 tasks

jmichelp added the question Further information is requested label Feb 6, 2020

xiongyihui mentioned this issue Feb 25, 2020

OpenSK compatibility/porting between nrf52840-mdk-usb-dongle and nrf52840-mdk makerdiary/nrf52840-mdk#32

Open

fateyan mentioned this issue Mar 10, 2020

Error when deploying to nrf52840_dongle #76

Closed

jmichelp mentioned this issue Mar 11, 2020

Revamp deploy.py #78

Merged

2 tasks

jmichelp closed this as completed in #78 Mar 12, 2020

Confined- mentioned this issue Mar 15, 2020

Requests for USB dongle without additional hardware. #81

Closed

mshetairy added a commit that referenced this issue Nov 13, 2020

Merge pull request #3 from MirnaMuhammad98/master

1270cdd

Update the example-app branch

NRF52840 boards? #3

NRF52840 boards? #3

Comments

tmikaeld commented Jan 31, 2020 • edited Loading

jmichelp commented Jan 31, 2020

tmikaeld commented Jan 31, 2020 • edited Loading

brouhaha commented Jan 31, 2020

tmikaeld commented Jan 31, 2020

xiongyihui commented Feb 1, 2020 • edited Loading

mikejrh commented Feb 1, 2020

rmm200 commented Feb 1, 2020

brouhaha commented Feb 1, 2020

rmm200 commented Feb 1, 2020

elfmimi commented Feb 1, 2020

rmm200 commented Feb 1, 2020

xiongyihui commented Feb 2, 2020

rmm200 commented Feb 2, 2020

elfmimi commented Feb 2, 2020 • edited Loading

xiongyihui commented Feb 2, 2020 • edited Loading

rmm200 commented Feb 2, 2020

MatchstickUK commented Feb 3, 2020

jmichelp commented Feb 3, 2020

Raboo commented Feb 3, 2020

rmm200 commented Feb 3, 2020

xiongyihui commented Feb 4, 2020

tmikaeld commented Feb 4, 2020

gregvinyard commented Feb 6, 2020

MatchstickUK commented Feb 6, 2020

gregvinyard commented Feb 6, 2020

dennisg commented Feb 26, 2020

sissaias commented Feb 26, 2020 • edited Loading

dennisg commented Feb 29, 2020

zappos23 commented Feb 29, 2020

jmichelp commented Feb 29, 2020

dennisg commented Mar 2, 2020

sissaias commented Mar 2, 2020 • edited Loading

mlberlin commented Mar 3, 2020

jmichelp commented Mar 3, 2020

dennisg commented Mar 4, 2020 via email

dennisg commented Mar 5, 2020

dennisg commented Mar 5, 2020

sissaias commented Mar 8, 2020

ejeyaseelan commented Mar 9, 2020

jmichelp commented Mar 9, 2020

jbalius commented Nov 25, 2021

jmichelp commented Nov 25, 2021

jbalius commented Nov 25, 2021 • edited Loading

jmichelp commented Nov 25, 2021

wezm commented Feb 1, 2023

elfmimi commented Feb 2, 2023

elfmimi commented Feb 3, 2023

wezm commented Feb 3, 2023

tmikaeld commented Jan 31, 2020 •

edited

Loading

tmikaeld commented Jan 31, 2020 •

edited

Loading

xiongyihui commented Feb 1, 2020 •

edited

Loading

elfmimi commented Feb 2, 2020 •

edited

Loading

xiongyihui commented Feb 2, 2020 •

edited

Loading

sissaias commented Feb 26, 2020 •

edited

Loading

sissaias commented Mar 2, 2020 •

edited

Loading

jbalius commented Nov 25, 2021 •

edited

Loading