Nordic "nRF52840 Dongle" Support #6870
Replies: 2 comments
-
Posted at 2018-07-26 by @gfwilliams I'm afraid not. I've been looking into support for the nRF52840DK but realistically to work properly it needs to be running with SDK15, and I haven't managed to get that going at the moment. They look like great little devices though, and extremely cheap too. Posted at 2018-07-26 by Stev
Well, I guess all the Nordic chips ask for this kind of cheap generic board designs, this one from Nordic themselves, so that will not go away. Still enough market for specific power/battery designs and special form factors as well as sensor/display combos. Now that the 52s with this chip got USB support, too, I hoped to get Espruino's USB HID support running, though I haven't verified that they will support that via the dongle's USB contact pads... Posted at 2018-07-26 by Stev
From the SDK downloads page it seems that the SDK from 12.2.0 up support the nRF52840. So the keyword were "realistically" and "properly"? Posted at 2018-07-27 by @gfwilliams
That's probably going to be a whole other chunk of work I'm afraid. You'll basically be starting from scratch as all of Espruino's USB HID code is STM32 specific.
As I understand it, USB only really became properly supported in 15 (I believe it was pretty flaky before). I did have a build for nRF52840 on SDK14 but USB never worked. But I could be wrong - you're welcome to give it a try yourself. Posted at 2018-07-27 by Stev 15’s release notes say something about production quality, also for USB, so lets hope they mean it. For the HID part, I totally forgot about the STM specific implementation. Still, the 52840’s integrated USB is a pretty cool thing and makes that dongle so interesting. I had a look at the HID examples yesterday but had troubles with flashing existing example hex’ and getting some if the tools to work. Seems I have to recompile using the full tool chain. The dongle is brand new and the desktop integration might still need minor work/updating. I‘ll post an update if I got something going Espruino-wise. Posted at 2018-07-27 by user92372 Please do keep us updated, I have 2 of these little jewels arriving Wednesday. Posted at 2018-07-28 by Stev Better not count on an early. Got the native blinky example running.. Posted at 2018-08-09 by @gfwilliams Just to let you know I now have a build of Espruino running on SDK15 on the nRF52840, with preliminary USB support (you can move the console over to it and upload code \o/ ). Posted at 2018-08-09 by user92372 Terrence here. Posted at 2018-08-09 by Stev Hooray, indeed, @gfwilliams Though we got a new dog and I will never have time for anything again, I‘m afraid... Had a look at the sources, though, last week after not having looked at it for a few years now, and am pretty happy with what Espruino has become and that it‘s well and alive. Great work. Posted at 2018-09-13 by urish Hi @gfwilliams, Is the code for the nRF52840 + USB on GitHub? I tried to look for it in master, but couldn't seem to find any mention of nRF + USB... Thx! Posted at 2018-09-18 by @gfwilliams It is now :) https://github.com/espruino/Espruino/tree/NRF52840 Posted at 2018-09-18 by urish Thank you for that @gfwilliams! Does it still build for you? I'm getting an error saying it can't find
Posted at 2018-09-19 by urish Looking at .gitignore, it seems like most of the content of the
Any pointers? Posted at 2018-09-19 by @gfwilliams try now :) Posted at 2018-09-19 by urish 😍 It compiles! When I upload the .hex file and run it on the chip, it doesn't seem to be showing up as a USB device, though it is connectable by BLE (even though it doesn't seem to advertise correctly). When I debug it in GDB, it seems to always stop inside
Not sure if this is something wrong with my setup or it indeed is busy parsing regular expressions all the time for some reason. I will keep investigating - any pointers are appreciated! Posted at 2018-09-19 by urish Since the advertisement was broken, I went ahead and patched
However, once connected, the device sends a single line endlessly, and does not seem to respond to any input:
Any ideas what this might be? Posted at 2018-09-20 by @gfwilliams Hmm - not sure. What are you running it on? The 52840DK, or the dongle? The board file was for the DK so perhaps there's something different in the pin mappings? It's possible that the computer you're using keeps connecting & disconnecting on USB, which causes that? Posted at 2018-09-20 by urish It's running on the Dongle, I'll try to tinker with the pin mapping and see if that helps. It doesn't seem the the USB serial port even show up on the Windows machine I'm connecting it to - it works in CircuitPython for the same dongle, though, so this probably has something to do with the configuration. Should I try switching to SDK 15.2.0 and see if that helps? So far, I tried changing the pin mapping for the serial port and map RX/TX to unconnected pins, but it didn't make any difference. Also, tried switching the default console to Posted at 2018-09-21 by @gfwilliams
You could give it a go. Looks like I used SDK15 for my builds. Honestly not sure what to suggest though - afraid I'm a bit too busy to help out with this at the moment Posted at 2018-09-21 by urish Sure, no worries! I'm already happy that we managed to get it to build and run on my board. Perhaps you could share one of the hex files that you have built so I will be able to test it and compare the results? Posted at 2018-09-24 by @gfwilliams Here's one I believe works - however I was using the 52840DK, not the Dongle - so I don't know if that changes things. Attachments: Posted at 2018-09-25 by urish Thank you! Posted at 2018-09-26 by urish Okay, the hex file you built is giving me a similar result:
I'm wondering why each line now has an extra Anyway, getting Espruino to run on it is just a nice to have experiment for me at this stage, so if you are busy, this can definitely wait... Posted at 2018-09-26 by @gfwilliams Hmm - just tried here on the nRF52840DK - I can connect via serial and it's responsive. Then I can do For Bluetooth it looks like it doesn't specify a BLE name, but I can connect using the CLI and that all seems to work as well. So I think it must be related to something on the dongle. Posted at 2019-04-13 by the1laz @urish I've had a go at compiling this but I've hit a wall and was wondering if you remember whether there was something extra that you did to get it to compile? I grabbed that branch from the repo, copied all of SDK_15.0.0 into targetlibs/nrf5x_15, copied all of the micro-ecc repository into the external/micro-ecc folder and then ran make clean && BOARD=NRF52840DK RELEASE=1 make. I'm running into this:
Which isn't making sense as sdk_config.h has this:
Posted at 2019-04-13 by the1laz Tossing "#define NRFX_UARTE_ENABLED 0" into nrf_drv_uart.h seems to have got it working. Probably not the best way of dealing with it, but I haven't managed to narrow down where it should be... Posted at 2019-04-13 by the1laz Interesting. I've loaded this onto a Particle Xenon to give the nrf52840 a spin (gave up on writing stuff for it in C. Nothing wrong with the Particle stuff, I've just been spoiled by Espruino :P). I can connect via serial and use the console, then I can switch it over to USB and use it there. However, I'm also getting the lines of:
when trying the bluetooth UART. If I switch to USB, then try to connect via bluetooth, I get this instead:
I'm connecting via the Bluefruit app on Android. Having some issues getting the espruino cli talking to it at the moment, the noble module seems to have some bugs but isn't being maintained any more. Posted at 2019-04-14 by the1laz jsiSetConsoleDevice was only being called once, so it looked like it's something to do with Espruino->Bluetooth rather than something weird happening with the serial or USB ports. Figured it was a buffer not being cleared somewhere so I scanned through likely files until I found a candidate. Changed this in targets/nrf5x/bluetooth.c and it came good:
Posted at 2019-04-15 by @gfwilliams Nice - thanks! That's a great spot. Do you want to add a PR for that change, or shall I pull it in? Posted at 2019-04-15 by the1laz I'll put it in when I get home. I'm not really sure about the "uarte" issue though, I don't know if the change I made should be somewhere else or should be altogether different. (I'm pretty sure it shouldn't be in the SDK where I have done it though...) Posted at 2019-04-15 by @gfwilliams I actually have the build working here, so I'm not sure what's different (I just pushed some changes that bring the branch up to date I hope). I'd have thought it was the @urish was there anything you remember having to change? There are some patches to do with the NFC libraries in Posted at 2019-04-15 by @gfwilliams Actually, just merged into Master Posted at 2019-04-16 by the1laz Alright, thanks, I'll have a go with a fresh download and see how it goes. Posted at 2019-04-16 by the1laz It's happy now that it's merged. 👍 Posted at 2019-04-21 by urish @gfwilliams I don't remember too much, but I will give it another go now and update shortly! Posted at 2019-04-21 by urish Update: it works well on nRF52840DK, but I had to follow @the1laz steps first:
and then compile:
The firmware seems functional, with one caveat - it won't advertise the board name nor the UART service, making it unconnectable from Espruino Web IDE. After patching the Web IDE to use the Posted at 2019-04-23 by urish Update: seems like commenting out this line solves the advertising issue. Calling Posted at 2019-04-23 by @gfwilliams Interesting - thanks! Looks like it needs a bit of refactoring done so that maybe Posted at 2019-04-23 by urish @gfwilliams would you like me to look into that and send a PR? On a different note, it seems like I am not being able to use any pins on the GPIO1 port. I have updated the board definition file to define ports up to D48, yet when Posted at 2019-04-23 by @gfwilliams It'd be great if you could - thanks! Please could you try and make it so that advertising_init and jsble_advertising_start are merged on SDK13 as well? It's nice to try and keep the ifdef nightmare as small as possible :) For the IO, I'd check I guess there might be a different function to Posted at 2019-04-23 by urish So far, I learned that I can poke the GPIO register to make it work:
This works and blinks the LED. Thanks for the pointer - my test program (without Espruino) is able to write to this port using Posted at 2019-04-23 by urish I managed to narrow it down by looking at the generated assembly code - it seems like for some reason, Posted at 2019-04-23 by urish I found the culprit -
This defines After commenting this out, I am finally able to use the GPIO1 pins. @gordon do you want me to add a new SDK patch and send a PR? Posted at 2019-04-23 by @gfwilliams Thanks for tracking this down. I guess the alternative is to change all of Espruino defines away from Assuming there's no easy fix in Espruino, a patch for the SDK would be great. At some point I should modify Posted at 2019-04-23 by urish Agreed - PR on its way, along with some other fixes that are required for making GPIO1 work Posted at 2019-06-01 by Delano Hi guys,
I'm using a copy of the NRF52840DK.py board file and use J-LINK to flash the *.hex binary. Status quo is that I can run any code, use GPIO 1, but not save it and run from boot. Also "Save on send" does not work. It just hangs forever, until I press CTRL+C, which yields "Execution Interrupted". Sometimes I get a message "Got ?[255] expected ','" when pressing CTRL+C, and the REPL points to the }); at line 3 of the code below. In that case, it executes the LED trigger with setInterval, except for the setWatch function. Using 'dump()' gives then the same error message. The code that I try to upload:
BTN1 is connected to GPIO1 (D36) and LED2 to D8. Serial1 is working, and connected to an external module. REPL over USB is not working, Bluetooth works without problems. Using Espruino 2v03.12. Any thoughts? Posted at 2019-06-01 by asez73 Hi @gfwilliams, how about a new generation of Espruino boards based on NRF52840? More ram, flash and ultra low powerwith ble integrated... 😎 Posted at 2019-06-03 by @gfwilliams Sounds like the addresses for the saved code area (in BOARD.py) need tweaking - it's odd though as I was pretty sure I had it working on nRF52840. I've definitely been considering nRF52840 - although IMO users aren't really hitting any big issues with nRF52 that the 52840 would fix. USB would definitely be nice though! Posted at 2019-06-03 by Delano I think you are right @gfwilliams about the board.py configuration; will look into it a bit more. IMHO the NRF52840 is indeed nice because of the dedicated USB, and e.g. Thread (IEEE 802.15.4 / 6LowPan based) protocol support. Also, it has a nice amount of GPIO for advanced set-ups :) Posted at 2019-06-09 by tcpipchip yes, think about and then we can port to NINA B3 now :) Posted at 2019-06-09 by tcpipchip But, is there some tip to compile to NRF52840, or it´s easy too like the NRF52832 ? Posted at 2019-06-09 by AkosLukacs One more thing might be interesting is that the nRF52840 has a low speed mode with better sensitivity: -103dBm sensitivity at 125kbps BLE vs -96dBm of the nRF52832 at 1Mbps. Also +8dBm max output vs +4dBm of the nRF52832. Has anyone tested, or has data on potential range improvement (preferably inside a building)? Nordic has published pretty impressive range outdoors... Is there any gotcha? Other than there is no support for Bluetooth 5 on either my phone or laptop & I have no idea about the intricacies of Bluetooth versions.... Posted at 2019-06-09 by tcpipchip We got 1km range communication outdoor with NINA B3 Posted at 2019-06-09 by AkosLukacs Oh, that's impressive. NINA B3 on both sides? What antenna did you use? Posted at 2019-06-09 by tcpipchip embedded antena! Posted at 2019-09-11 by zeromem Hi, any news about Nordic nRF52840 Dongle support? I just got one. Thank you. Posted at 2019-09-11 by tcpipchip I see that they are tryng to port it! I guy have success! Did you see that ? Posted at 2019-09-11 by @gfwilliams I believe it's actually pretty reasonable when ported to the DK now, so if the dongle uses the same pinouts then you could use the exact same hex file from that. Unfortunately Nordic are only supporting the Thingy at the moment. Maybe if enough people prodded them they could be convinced to get me to do builds for the dongle ;) Posted at 2019-09-11 by tcpipchip Yes, i agree with you! But did you ported to dongle ? Posted at 2019-09-12 by @gfwilliams Not specifically, but Nordic do tend to use the same pinouts so the DK version may 'just work' Posted at 2019-09-12 by tcpipchip btw, i am writing a book about Alexa amazon and i would like to include your Espruino in a chapter, but needs to be to ESP32...and with 2Mb flash Posted at 2019-09-12 by @gfwilliams
I think so. On official Espruino WiFi boards you can supply SSL certificates: http://www.espruino.com/Storing+HTTPS+Certificates On ESP32? Not sure, but it's possible. As with all this stuff while it'd be nice to support more hardware, I have to run a business and more hardware means more dev and support work for me - and yet no more income. Posted at 2019-09-12 by user95229 Gordon Very interesting! Before i tests ESP32 + SSL + ASW IOT, please, tell me if ESPRUINO will runs in a 2Mb FLASH ESP32? I will use NINA W102. Posted at 2019-09-12 by tcpipchip I am testing first on WROOM! Works fine using TERATERM... Posted at 2019-09-13 by tcpipchip found! 115200 Posted at 2019-09-14 by tcpipchip Gordon,
Very strange :( Posted at 2019-09-14 by tcpipchip https://www.dropbox.com/s/dj6fcj0039064bj/gordon.png?dl=0 Posted at 2019-09-16 by AkosLukacs Tried to build for the nRF52840 DK, but ran into two issues with provisioning: First at line 160 in provision.sh:
Second is the SDK15 NFC patches. Which file should be patched?
Output:
Posted at 2019-09-17 by @gfwilliams Not sure what's up with the permission issues at all. I don't get that, and it should be an empty directory I'd have thought :/ Also with NFC, it just doesn't work at the moment on SDK15. Just ignore the patch errors and it should still work as long as you don't try and enable NFC functionality. Posted at 2019-09-17 by AkosLukacs Thanks, looks like the permission issues are some kind of WSL & remote VSCode locking up freakshow. Manually copying and moving solved the problem. Edit: Applied the last patch Posted at 2019-09-17 by AkosLukacs Update: the 52840-DK does work: Can connect via virtual serial thru the built-in JLink + native USB(serial) + BLE. \o/ But couldn't get it working on the dongle :( First try: just flash the same hex with nRF Connect. No luck. Tried to create a board file for the dongle, but no luck. Compiles OK, but doesn't do anything :/ Attached the board file, if anyone wants to give it a try. Attachments: Posted at 2019-09-17 by AkosLukacs Got it working \o/ Attachments: Posted at 2019-09-18 by zeromem Working on my dongle! Thank you!
Posted at 2019-09-19 by @gfwilliams That's great! Thanks! You ok with me pulling that into the UNMAINTAINED_BOARDS branch? Posted at 2019-09-19 by AkosLukacs There are still some small issues:
So those pins should not be toggled even accidentally. Toggling a pin that's not routed is no issue, but if someone sets these pins to different output values, that could fry the board I guess. Tiny chance, but still... The green LED (D6 IIRC) is turned on after boot. I can toggle it later, but strange. Any idea why? The LEDs are active low, so they turn off on the first
should solve it? Posted at 2019-09-23 by @gfwilliams I answered the pin removal thing in your other post - so it should be easy enough to remove them. And yes, doing the negation should fix the LED thing I'd have thought. Posted at 2019-09-30 by tcpipchip Running now on UBLOX NINA B302 too! Attachments: Posted at 2019-09-30 by tcpipchip How can i do make direct access to GPIO P0.30 ? Posted at 2019-09-30 by AkosLukacs
Posted at 2019-09-30 by user95229 D30 maps to direct io P030 ? Posted at 2019-10-01 by tcpipchip hI, d30 IS not mapped to P030. Who is mapped to P030 is D2 Wich files has this map to me to follow ? Posted at 2019-10-01 by AkosLukacs Should be. Haven't tested all, just the LEDs and button available on the 52840 dongle, and those were working:
All pins should be there. P0.00 as D0 and so on. P1.00 is D32 and so on. Posted at 2019-10-02 by tcpipchip Akos, if i send my personal MAP, can you compile to me ? Or, if you give instructions to compile i can do here...i had done 832 year ago! Thanks! Posted at 2019-10-02 by AkosLukacs Just follow the build instructions :) Posted at 2019-10-02 by tcpipchip :) The main is change devices = { Right ? I will want to map For example, Attachments: Posted at 2019-10-02 by AkosLukacs I have a new build, fixes:
Board file two hex files are attached: 2v04.105 is built from the same commit as the previous one, 2v04.121 is from the latest master. Bluetooth and USB serial works, haven't done much testing... @tcpipchip Don't exactly remember what made it working, IIRC make everything "right"... You can do that from JS (or wrap it in an object, if you'd like to):
Or - since the dongle build file defines the LEDs, button, and two pins for serial, you might want to create your own board file, and the pin naming could be done like the NodeMCU pin aliases: Add an extra file that defines aliases: Something like @gfwilliams I have one last (hahaha) question: The nRF52840 has pins on P0 and P1. right now P1.00 maps to D32, that's kind of annoying (thoughts in my brain: do I add 31 or 32 or wat?). Tried to mess with the board file and build_pininfo.py, and I could make a mess and create for example an Attachments: Posted at 2019-10-02 by zeromem Working on my dongle! Thank you!
Posted at 2019-10-02 by tcpipchip Ready, can you compile ?
Posted at 2019-10-02 by Robin Wed 2019.10.02 As @AkosLukacs suggested in #86, 'Just follow the build instructions' as two builds have been provided in #88 The following is a good starting point, see the AkosLukacs entry which is #8 in the entire thread, when expanded. The step-by-step instructions are what I am following to perform the exact task you wish to accomplish: Posted at 2019-10-03 by AkosLukacs Without NFC, because I didn't apply the NFC patches, and build fails with NFC. But yeah, @robin is right, try to get it building on your computer, so you can tweak the board file. Attachments: Posted at 2019-10-03 by @gfwilliams Ok, I think you're after two things that are incompatible (I could be wrong though :). Basically when you access a pin in Espruino, Espruino gets the hardware pin number and port from Normally, without But since you want to skip pins out as well, you use The other thing you could do is mess around with Posted at 2019-10-04 by tcpipchip Lucas Posted at 2019-10-04 by AkosLukacs The ~800k file is the ".app_hex", but there should be a bigger ".hex" file too. Posted at 2019-10-04 by tcpipchip then really something is wrong during my compile... Posted at 2019-10-04 by AkosLukacs @gfwilliams Saving code to the dongle doesn't work , but works on the nRF52840DK. The DK:
The dongle:
Edit: thanks for the previous reply, of course I want to do something totally not supported with the pins :) Posted at 2019-10-04 by @gfwilliams Is it actually the same chip, or is it one with less flash memory? You could try Posted at 2019-10-04 by AkosLukacs nevermind, fix is in my next post :) Posted at 2019-10-04 by zeromem Same thing on my dongle. :(
Posted at 2019-10-04 by AkosLukacs Figured it out: The dongle ships with a USB bootloader, located at the end of the flash. And the saved code area is defined right there. Details here Moved the saved code area a bit, and now everything seem to be working :) (If I got the numbers right, but it's getting a bit late. Only tested with a small blinky code. Still, the 52840 has a ton of free flash, so moving the saved flash area is not a big deal) Attachments: Posted at 2019-10-05 by zeromem Tested OK save().
Posted at 2019-10-13 by AkosLukacs Small update: I think solved the pin naming issue. Or does anyone have a better idea for pin naming? @tcpipchip did you solve your pin naming problem? Attachments: Posted at 2019-10-13 by user95229 I had aborted because was creating only a 800k size! I will test your version with new gpio map that you created! I will use on nina b302 :) Posted at 2019-10-13 by zeromem I tested the new version, thank you.
Posted at 2019-10-14 by tcpipchip Can you map all pins ? For example, you forgot D0...D31...D32...it´s working! Posted at 2019-10-14 by AkosLukacs Only mapped the pins available on the Nordic Dongle. For example P0.03 is not accessible on it. Attached the spreadsheet I used to create the pin maps. But yes, I can map the rest of the pins, wanted to do that for the DK as that as all pins routed. Attachments: Posted at 2019-10-14 by tcpipchip Nince @AkosLukacs Please, map them :) Thanks for all your help :) Posted at 2019-10-14 by tcpipchip wich are the default USART gpio txd / rxd used if i dont want USB serial ? Posted at 2019-10-14 by AkosLukacs RX: P0.13 (D13) Posted at 2019-10-14 by tcpipchip Did you enable BLE in on your compile ? Attachments: Posted at 2019-10-14 by tcpipchip The same error to
Posted at 2019-10-14 by AkosLukacs BLE is enabled, I can connect to the dongle via BLE & NUS. Posted at 2019-10-14 by tcpipchip yes, that is a problem :( Maybe gordon can see that SCAN problem :( Posted at 2019-10-17 by @gfwilliams That's a strange one - pretty sure I had stuff like that working just fine on the nRF52840 build. The only thing I knew was broken was setting the Scan Response data. I'm afraid I don't have time to look into that at the moment though Posted at 2019-10-17 by user95229 no problem! Verify when have time! 30 days is enough ? :) Posted at 2020-01-17 by user108516 Hello, good work on this! I ordered an makerdiary nRF52840 MDK USB Dongle (but own it not yet). Do you think this might work too? For a project I need the dongle to connect to a bluetooth device and act as an HID-USB-Device. Does the USBKeyboard-Module work? Do someone ever tested it? Thank you for your reply. Posted at 2020-01-17 by AkosLukacs I have an MDK dongle, but so far I couldn't get either Espruino, or Nordic's official long-range demo to work. Posted at 2020-05-15 by k.zabloudil Hello, I tried to flash AkosLukacs's hex file from this page to my nrf52840 dongle using nrfutil:
it says that the device was programmed succesfully, but I can't connect to it (I do not see any BT device nor any COM port I can connect. the only port I see is the one I used for programming showing nRF52 SDFU USB (COM5)) any hint what can be wrong ? thank your any advice... Posted at 2020-05-15 by AkosLukacs I don't think you need to create a DFU package. I just used the nRF Connect application's programmer. AFAIK that just calls nrfjprog. Posted at 2020-05-15 by k.zabloudil thank you, I was able to flash and connect using nrf connect! Posted at 2020-06-25 by rocksetta I am new to all this, however I have been hacking various nrf5200 boards for a while. Anyone here used the Particle Debugger for $20.00 USD from Adafruit. It is fairly amazing, drag and drop .bin and .hex boot loading. Here is a long blog about what I was trying to do on PlatformIO Since I am new to the forum can someone summarize their experience with the NRF52840 USB dongle or similar with espruino? I have 3 of them. Posted at 2020-06-25 by AkosLukacs You have to build the firmware yourself, but just built one two days ago, see the attached hex. The board file is above somewhere. Attachments: Posted at 2020-06-25 by rocksetta Any extra tricks. I can install your hex file. But my windows 10 computer does not seem to see the port unless I put it in bootloader mode, but then flashing does not work.. Chrome extension seems to work fine. Doesn't help that I haven't even used espruino before so not sure if I am doing anything really silly. Posted at 2020-06-25 by rocksetta @k.zabloudil I am at the same step. Flashing bootloader seems fine. I think windows probably needs a driver. Will look a bit more. Just occurred to me that the problem is probably that I have never ran an official Espruino device. The driver that would normally install on first run is probably not installing. Will try that. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2020-06-26 by AkosLukacs Ok, what do you mean by "flashing does not work" ? If flashing won't work, nothing will work :) So, I'm lazy to type so just use nRF Connect desktop's "Programmer". You can use the command line tools, the GUI is calling that, so the result should be the same...
The programmer's log output should look like this:
Small correction, looks like I lost my latest board file, so BTNs and LEDs are the same as on the devkit, and that's not correct. But for example Attachments: Posted at 2020-06-26 by @fanoush As for bootloader, the one in espruino tree worked for me with Particle Xenon so it is also possible to build the board file with bootloader turned on and then flash it including espruino bootloader and use DFU over ble. I think with generating DFU package it just needed some change to use NRF52840 family for nrfutil when making the zip or bootloader would otherwise not accept it. But SWD is faster anyway (or usb). As for usb console prompt, yes it works somehow but I better disconnect USB as it interferes with ble console and it does something strange for me with Xenon at boot/reset time. Not using Xenon with Espruino very much but so far it mostly worked just fine for testing 52840 capabilities, no rough edges. And BTW with 256K of RAM one can hit Espruino limit that you can't allocate variable over 64KB size like e.g. Posted at 2020-06-26 by @fanoush
It uses CMSIS-DAP, one of possible SWD implementations, feels better than stlink to me, e.g. can erase locked nrf52 chips, also works over USB HID so need no special usb drivers installed, also have UART included, I like it too. Don't have the one from Particle but there are also CMSIS-DAP implemenations for blue pill boards or STLINK V2 clones ($2 items). Interesting that the photo of Particle Debugger shows GD32F103 chip - clone of STM32F103. Posted at 2020-06-28 by parasquid @AkosLukacs just wanted to let you know that your intstructions (and sample .py file) were very helpful :)
Posted at 2020-12-23 by user95229 Hi Posted at 2021-01-06 by tcpipchip i had tried many times! No works! still uses the SDK 15 ? Posted at 2021-01-07 by @fanoush I see no difference building for nrf52840 dongle than building for any other board, yes SDK15 based build works on dongle. after calling BTW as for nrf52840 dongle, there is cheap 'clone' that often sells for $6.65 including shipping https://www.aliexpress.com/item/1005001530238972.html , got few of them and for the price it is good 52840 board. It is clone in the sense that button and LEDs pinout is same and same pins are brought out as on the original dongle. Otherwise it looks different and has also plastic case. Also any nordic firmware and tools made for nrf52840 dongle works on this one too (connectivity fw, bt sniffer,...) Posted at 2021-01-07 by user95229 Thanks for your good explanation!!!! Posted at 2021-01-07 by tcpipchip @fanoush Attachments: Posted at 2021-01-08 by tcpipchip https://u-blox-nina-b112-javascript.blogspot.com/2021/01/compilando-espruino-para-u-blox-nina.html Posted at 2021-01-15 by tcpipchip https://windows7-ble-scan.blogspot.com/2021/01/criando-um-android-app-para-acesso-ao.html NEW BLOG :) Posted at 2022-03-25 by user141817 Is the scan issue fixed in a new hex? I am also seeing this error. Posted at 2023-12-20 by DanDyse Just made a built for nrf52840 without USB/LED. Attachments: |
Beta Was this translation helpful? Give feedback.
-
Posted at 2018-07-26 by Stev
Hey,
just received a few of those "original" nRF Dongles today. Is there already support for those?
-Stev
Beta Was this translation helpful? Give feedback.
All reactions