nRF52833 is a powerful solution which supports multiprotocol such as Bluetooth, Zigbee, and Thread but also qualified for industrial operation at an extended temperature range of -40°C to 105°C.
Raytac’s MDBT50Q and MDBT50 module employed nRF52833 solution offering 2 kinds of form factor with either 48 or 18 GPIO option for selection. 3 antenna options helps developers to find the best balance between performance and budgetary for projects.
MDBT50Q and MDBT50 modules are BT5.2 qualified supports direction finding and Bluetooth long range feature. Both are built around 128K RAM, 512K Flash memory with I2C, SPI, I2S, UART, NFC, USB interface. A 1.7V to 5.5V supply voltage range enables powering the device from rechargeable batteries or over USB and +8dBm output power has significantly enhance the bluetooth long range coverage which is suitable for outdoor or smart home applications.
The modules are FCC/IC/CE/Telec/KC/SRRC/NCC/RCM pre-certified and in mass production for volume shipment. EVK demo board is also available for quick debug and evaluation. Developers who are interested in nRF52833 module MDBT50Q and MDBT50 are welcome get in touch with Raytac for immediate service support.
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 😉
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:
Further down in the specification sheet, in section 9, you will find pictures illustrating where exactly on the PCB you can find these pins:
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:
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:
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.
After Nordic released nRF52840, the confusion raised what the difference between nRF52832. Raytac provided an easy comparison chart based on module solution hopes to provide a quick understanding in between.
MDBT50Q Module Series Mass Production has completed, customers who are interested in nRF52840 solution may contact with firstname.lastname@example.org for further information.
Raytac’s MDBT50Q module deploy Nordic nRF52840 is a Bluetooth 5 (BLE), Zigbee and Thread (802.15.4) modular solution and is an advanced multi-protocol SoM with anARM® Cortex™-M4F CPU and featured built-in USB and 5.5V compatible DC/DC supply.
The compact size 10.5 x 15.5 x 2.0 (2.2)mm incorporates 48 GPIO, integrated various antenna types option (Chip Antenna, PCB antenna, u.FL connector) provides developers flexibility to meet most IoT Application Demanding, Connectivity Range Requirement, BOM Cost Saving, Designs Simplifying, and Time-TO-Market Efficiency.