Burn your firmware – onto MDBT50Q-RX that is

Hi there, folks!
So you have hopefully downloaded your IDE, you have written your code which you then plan to copy it over onto your MDBT50Q-RX and make it execute your master plan to take over the world!
Seriously, don’t underestimate the Nordic nRF52840 based MDBT50Q-RX. USB sticks with Bluetooth can do wonders 😉
(I am serious! Just look at Plezmo! You see that USB stick? Yep, that’s another Raytac for ya)So, first of all, in order to be able to burn your code onto the USB Dongle, you will have to know the nerdy parts which includes which pins you will have to connect to. In our very well documented specification sheet for MDBT50Q-RX on section 8 which is called “Reference Circuit”, you will find parts down to the left that has “3.3V/SWDIO/SWCLK/GND” marks on it:
Burning pins on MDBT50Q-RXFurther down in the specification sheet, in section 9, you will find pictures illustrating where exactly on the PCB you can find these pins:
Pin locations

Now we know what to look for and where they are, so now we have only got to tell you how to use them.

Some people might not know this, but for developing these things, you need to get something called J-Link to connect your MDBT50Q-RX to your desktop. However, since this J-Link, when buying the official one from SEGGER, is very expensive, we strongly recommend you to just buy the nRF52840-DK from Nordic Semiconductor as it can be used as a J-Link through their software development kit (SDK) called nRFgo Studio and is MUCH CHEAPER than the official J-Link from SEGGER is.
Sidenote: There are a couple of other reasons why you should just get your hands on a nRF52840-DK from Nordic Semiconductor instead of getting a SEGGER J-Link, but that’s not the topic of this post 😉

When this is done, this is finally how you connect your MDBT50Q-RX to your J-Link to make it all work:

MDBT50Q-RX and J-Link connection

Here you will have to pay attention to the fact that you have to connect J-Link pins 3, 5 & 9 to GND. Otherwise, you won’t be able to burn anything onto your dear MDBT50Q-RX.
The physical connection should look like this:

J-Link Cable Connection

Pay attention to the direction of the cable, because that will also matter. The direction we mean in this case is which way the slim strip of red is facing.

As we have just revised our MDBT50Q-RX, our customers who have been developing firmware for our USB dongle should take a look at our previous blog post in which we explain about the changes made or contact us directly at service@raytac.com

Have a good day and we at Raytac wish you smooth and happy tinkering 🙂

Raytac Corporation 勁達國際電子有限公司
A BT5 & BT 4.2 & BTv4.1 module maker based on Nordic nRF51 & nRF52 solution
(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)
www.raytac.com email: cs@raytac.com Tel: +886.2.3234.0208

 

Raytac Product Change Notice (PCN) Announcement for nRF52840 Dongle: MDBT50Q-RX

Dear Customers,

To enable hardware reset function in Raytac’s nRF52840 dongle (P/N: MDBT50Q-RX), Raytac’s has revised the circuit and issued the PCN accordingly.


Description of the Change:

1. Change circuit design to enable the hardware reset function.
2. Change PCB Imprint
3. Change Label
4. Change Part No.

Here provided the content of the PCN for customer’s reference.

PCN-19031801-1
PCN-19031801-2

Customers who have been developing firmware based on pervious dongle, please contact with service@raytac.com to request the latest sample version for evaluation.
Raytac Corporation 勁達國際電子有限公司
A BT5 & BT 4.2 & BTv4.1 module maker based on Nordic nRF51 & nRF52 solution
(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)
www.raytac.com email: cs@raytac.com Tel: +886.2.3234.0208

Raytac Corporation at IT Week Hall 3 & 4 / 11-22

With over 600 exhibitors gathering in Tokyo, Japan from April 10-12, IT Week has become one of the biggest exhibitions within the IoT Technology sector.
Raytac is pleased to be attending this years IT Week and present our full range of module family based on Nordic nRF51822, nRF52832 and nRF52840.

Meanwhile, the latest product, MDBT50Q-RX, a multi protocol nRF52840 dongle will make its second public appearance which powers up the most advanced IoT and Mesh network implementations.

Raytac Corporation 勁達國際電子有限公司
A BT5 & BT 4.2 & BTv4.1 module maker based on Nordic nRF51 & nRF52 solution (nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)

How To Use MDBT50Q Demo Board (MDBT50Q-DB)

Here provides an easy introduction of How to set up of MDBT50Q-DB!
MDBT50Q-DB, built by Raytac’s MDBT50Q-1M deployed nRF52840 SoC with Bluetooth 5 & Thread Combo module Demo Board. Equipped Raytac’s MDBT50Q-1M  with 1MB Flash Memory and 256KB RAM and Chip Antenna. Certifications include:  FCC, IC, CE, Telec, KC, SRRC, RCM, NCC, WPC 
mdbt50q demo board package 拷貝

MDBT50Q-RX, a nRF52840 USB Dongle, delivers an easy implement for M2M IoT application

Raytac's MDBT50Q-RX, a Nordic nRF52840 USB Dongle

Raytac’s BT5 certified nRF52840 USB dongle, MDBT50Q-RX, eliminating the need for RF design expertise, and speeding time to market for complex M2M IoT applications. The Dongle built by Raytac’s MDBT50Q-P1M module with FCC/IC/CE/Telec/KC/SRRC/NCC/RCM/WPC certification.

Raytac's MDBT50Q-RX, a Nordic nRF52840 USB Dongle
Raytac’s MDBT50Q-RX, a Nordic nRF52840 USB Dongle

Where To Buy Raytac Bluetooth Module Sample?

To enhance the accessibility to Raytac BLE module sample for evaluation and development, Raytac has put effort to corporate with several channels.

Differ channels may carry various items, we encourage developers firstly visiting Raytac official site. The easy link options listed in each product may help customers to select the friendly channel to approach.

螢幕快照 2019-01-21 09.58.27

Bluetooth – Current and soon-to-perish versions

Bluetooth has been around for quite some time, but that doesn’t mean that no one is a beginner when it comes to developing Bluetooth-based products. In fact, due to their recent updates, Bluetooth is becoming increasingly popular as demand for power efficient gadgets and wireless technology is increasing. Smart watches is just one of the many examples out there.

For each and every single one of these devices, you’ll first have to register your new product with Bluetooth-functions built in on Bluetooth SIG’s website. You will eventually register (and pay for) your product based on what version of the Bluetooth protocol that you’re using in the product and do so by purchasing a so called Declaration ID (DID).

Yes, a little exaggeration in the title, but that’s essentially what it comes down to. Bluetooth SIG is doing some major updates and changes to the Bluetooth protocol which includes getting rid of the more outdated versions.

There are quite a few versions of the Bluetooth protocol out there, but nowadays you will basically be advised to choose from 2 versions:
v.4.2 or v.5.0
These two versions would be, as I mentioned in the title, the two current versions of Bluetooth.

Although it might seem very simple at first, there are a few things that you need to understand the content of the announcements to fully grasp what these updates and changes mean. That, my friends, is today’s topic of this post.

Archived specifications

Deprecated and Withdrawn Specifications

When a specification reaches the end of its useful life, the Bluetooth® SIG may choose either to deprecate the specification, ending maintenance and restricting its use, or to withdraw the specification from use.

Bluetooth SIG – https://www.bluetooth.com/specifications/archived-specifications

What has changed recently is nothing new, but it’s big. What I mean is that similar changes have been done in the past, but since the market is more dependent on the technology now than before, it matters far more for people when the Bluetooth SIG do the same changes nowadays. Those changes are as follows:

On 01/28/2019, the following policy changes will be enacted:
– Creating new designs that implement deprecated or withdrawn specifications will not be permitted
– New products cannot be added to designs that implement withdrawn specifications
– You cannot pay a $25,000 fee to qualify a new design that implements a deprecated specification
– Purchased but unused $25,000 Declaration IDs will no longer be valid and the cost of any unused $25,000 Declaration IDs will be credited to your account

 

Bluetooth SIG – bluetooth.com

This piece of information tells us that the process of withdrawing specifications comes down to two different steps, namely deprecation and withdrawal.
While deprecation literally means “to stop use”, it is in this case the first step in the process of making a certain Bluetooth specification obsolete.
Then there’s a time gap between a certain specification gets deprecated until it’s withdrawn. During this gap, as mentioned above, no new designs can be paid for and/or registered and unused DID’s will be invalid. This is only to prevent new devices with deprecated Bluetooth specifications from being produced. To stop the “bloodline” of those specifications if you will. During this gap, however, you are still able to add new products that implement the same fundamental design (e.g. version updates) as you wish.

After this gap is over, when the specification in question is actually withdrawn, you will not be able to add any new products to any existing designs.

Got it? No? It’s alright. In fact, there’s a lot of information and it’s hard to put into context right away. Just to make things clear, let’s make an example:
Company R is currently developing a new device called RIC which implements Bluetooth 4.0 specifications. For now, everything’s alright and Company R can go right ahead with their developments.
When the Bluetooth core specification 4.0 becomes deprecated in Jan 28th, Company R can no longer come up with new product designs such as RIC-2 since that would count as a new design, but Company R can update their original device RIC as long as they don’t change the physical design.
Then, when the Bluetooth core specification 4.0 is finally withdrawn, Company R cannot update their product RIC anymore AND they cannot register new designs under Bluetooth core specification 4.0.

If you’re a developer who is very familiar with Bluetooth already, this information might already be, as certain people refer it as, “peanuts”. If you’re new to the Bluetooth world, however, this is a lot to take in and you might want to read up more about it. We hope this explanation made things clearer for you though 🙂

You can find more info at:
Bluetooth SIG – https://www.bluetooth.com/specifications/archived-specifications

Don’t forget that Raytac Corporation’s modules are all pre-certified with FCC, TELEC, IC, CE, RCM, KC and SRRC. The best part is that more is yet to come!
Take a look at our modules on our website: http://www.raytac.com

 

Come to visit Raytac at Embedded World #Hall 3 / 3-520

With over 1,000 exhibitors gathering in Nuremberg, Germany on 26 Feb.~29 Feb., 2019 , Embedded World has become one of  the biggest trade fair among the IoT Technologies.

RAYTAC27-20181220_lo

Raytac Released nRF52840 USB Dongle “MDBT50Q-RX”

Raytac released nRF52840 USB Dongle which deployed MDBT50Q-P1M module offers a Bluetooth 5 specification granted, FCC/IC/Telec(MIC)/KC/SRRC/NCC/WPC pre-certified, and CE/RCM compliant solution.

Raytac nRF52840 Dongle MDBT50Q-RX
Abstract molecule structure on dark blue color background. Vector illustration of Communication – network for futuristic technology concept

Bluetooth Project: How to program your firmware to module

After setup been done, here comes the next question: How to program the firmware in to the module. We are using some simple instruction in below for reader’s quick reference.

Hardware

You will need a Nordic nRF5X DK or a Segger J-link as programmer to load the firmware. To use Nordic nRF5X DK to debug the SoC as well, you will need to order corresponding nRF5X DK to match the SoC number. For example, order nRF52840 DK to debug nRF52840 SoC or order nRF52 DK to debug nRF52832/52810 SoC. But if you are only using it as programmer, any version of nRF5X DK will work as we only use the J-link on this board.

Software

Please download Nordic nRFGo Studio for programming. Remember to install nRF5X Command Line Tools if the board was not detected by nRFGo Studio. Once they are all connected, you can then start programming. Please make sure to “erase all” every time before programming.

For more tutorials and demo of sample code, please visit Nordic’s DevZone and Infocenter where have ample resources to utilize.

Programing 

SoftDevice + Application

  1. Erase all first. Then program Softdevice and follow by Application code.
  2. Or you may combine code as stated in above. Erase all and follow by programing the combined code.

SoftDevice + Bootloader+ Application

  1. Either Erase all first.  Program the Softdevice and follow by Bootloader. and then use DFU to update the application code.
  2. Or suggested having a combined code (SofDevice+Application+Bootloader) for program. Simply erase all and follow by programming the combined code.
*Remark
Bootloader is needed for DFU (OTA) Function.
SDK 11 (included) and before – a legacy DFU method, which is simple but less security
SDK 12 (Included) and after – a latest DFU method, which has higher security.

 

To easy customer’s IoT device mass production, Raytac provide code pre-program service into module before shipment.  There are requirements listed in below for customers who need the service!

  1. A single, combined hex file is required. Please combine softdevice and application or/and bootloader (depending on your firmware design) together before programming. This will shorten programming time and help to manage your code easier. If you are not familiar with merging firmware, please download the instruction from the link:     https://mega.nz/#!Qg5UBJTQ!POWmmNNdapGqefHpB10YjpcuExLWwXnxDfBzcVrsTOw
  2.  Need a simple method to check programming status. The easiest way is to check the device name if device will broadcast device name after programming is done; or use I/O to trigger LED and its behavior. This does not aim to test any or full function of your device, only a simple method for the operator to know programming status.

nRF52840 MDBT50Q Module
nRF52840 MDBT50Q Module

 

Raytac Corporation
A BT4.1 & BT4.2 & BT5 module maker based on Nordic nRF51 & nRF52 solution 
(nRF51822 & nRF51422 & nRF52832 & nR52810 & nRF52840)
www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208