Tips for Nordic’s nRF52840 DK to successfully detect Raytac’s MDBT50Q-DB-40 Demo Board

 WHY Nordic’s DK cannot DETECT Raytac’s modules?

Some tips to fix this problem

Nordic’S board no : PCA10056 (nRF52840)

Raytac’s board no : MDBT50Q-DB-40 (nRF52840)

1. Update the version of nRF Command Line Tools from below link
https://www.nordicsemi.com/Products/Development-tools/nRF-Command-Line-Tools/Download?lang=en#infotabs

2. Update the version of jlink driver from below link.
https://www.segger.com/downloads/jlink/JLink_Windows_V780c_x86_64.exe

3. Update the version of nRF Connect for desktop.
nRF connect for desktop V4.1.2
Programmer V3.0.9

4. Add jumper wire for GND shown as the below red arrow to avoid the different power reference between these 2 boards.

5. Make sure that IDE cable connects correctly. Red edge of IDE cable should connect to PIN 1 of both boards.

6. Supply power to VDD of Raytac’s demo board before flashing.



Edited by Sales Manager: Ms. Gracie Chuang
Raytac Corporation 勁達國際電子有限公司
A BT5.2 & BT5.1 & BT5 module maker based on Nordic nRF53 & nRF52 solution
(nRF5340 & nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52811 & nRF52810 & nRF52805)
http://www.raytac.com email: service@raytac.com Tel: +886.2.3234.0208

BLE Module Firmware Development Q&A: NFC pins creates “Error 404 – signal not found” (technically)

When you start developing your firmware for your Nordic nRF52832 solution-based Raytac BLE module, you will (like on most other projects) bump into some difficulties.

The other day, we had yet another case where a simple thing caused major difficulties for even some of the brightest people – a customer couldn’t get their GPIO direction bit to work.

Although not too difficult to solve, it’s a common error that most customers end up having on our modules and that is because Pin 0.09 & 0.10 are set to NFC per Nordic’s default settings. In order to be able to use these pins as normal GPIOs, you will have to change those settings.

The two pins I am talking about are the ones linked to the NFC-part to the far left in the circuit example below:

So, to convert these two pins to normal GPIOs, here’s what you need to do:

In SES, you’ll need to add CONFIG_NFCT_PINS_AS_GPIOS.

Right-click on the project and click “Edit Options”

Select “Common”, click on “Preprocessor” under “Code” and then click “CONFIG_NFCT_PINS_AS_GPIOS”

Check out the link below for a reference example on Nordic’s DevZone.

Reference link: Nordic DevZone – NFC pins into GPIOs

Raytac Corporation

A Bluetooth Low Energy module maker based on Nordic Solutions!

www.raytac.com          email: cs@raytac.com          

Nordic nRF52832 Module: MDBT42V & MDBT42V-P CE RED Compliance

MDBT42V and MDBT42V is a Raytac's latest BLE module solutioned by Nordic nRF52832 with small form factor. Bluetooth Specification granted based on BT5.0 / BT4.2,

Due to the compact size, it can easy to fit into any IoT appliance and has yet raised the highest interests among developers recently.

Following by Raytac's "Easy Employ" Policy, MDBT42V and MDBT42V-P has started to proceed the safety regulation compliance program. Hereby, we are pleased to announce RED directive has been fully met.

CE regulation

EN 300 328 V2.1.1: 2016

IEC 60950-1

EN 301 489-1 2017-03

EN 301 489-17 2017-03

EN 55032: 2015+AC:2016-07

EN 6100-4-2:2009

EN 6100-4-3: 2006+A1:2008+A2:2010

Nordic launched latest nRF52 series SoC "nRF52810"

CES Asia, Nordic launched latest fruition of nRF52 family: nRF52810
What is it about?
http://www.nordicsemi.com/eng/Products/nRF52810

                

Guess What? Raytac is ready for nRF52840

Raytac now is ready for coming nRF52840 SoC with Bluetooth specification BT5.

The module’s mass production schedule will be ascertained after Nordic IC supplying schedule affirmed. (expected around 2017 Q4 or 2018 Q1)

Nordic nRF52832 UART Service Solution (Module: MDBT42Q)

Raytac Corporation

A BT4.1 & BT4.2 & BT5 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF51802 & nRF52840)

www.raytac.com            Tel: +886.2.3234.0208

email: service@raytac.com

Wordpress

UART service, as known as NUS (Nordic UART Service) is the most common and easy way for BLE relating IoT Implement.

Customers who is familiar with Classic Bluetooth are used to call as SPP service.

nRF52 BLE Module (MDBT42 series) BQB Test & BT4.2 Certification Granted

Raytac Corporation 

Bluetooth module maker based on Nordic nRF51 & nRF52 solution 

(Nordic nRF51822 & nRF51422 & nRF52832 & nRF52840)
Bluetooth Specification Version: BT4.0 & BT4.1 & BT4.2 & BT5

www.raytac.com

Tel: +886.2.3234.0208

email: service@raytac.com

https:/www.raytac.blog

We are pleased to release that Raytac's MDBT42 series module (including MDBT42Q / MDBT42 / MDBT42V) based on Nordic nRF52 series solution has completed the BQB testing and BT4.2 certificated granted.

Customers are welcome to use or relabel the QDID accordingly.

MDBT42 Module QDID: 91882 (Declaration ID: D033661）

MDBT42 Profile Subsystem QDID: 91659 (Declaration ID: D033662)

Nordic nRF5 SDK v.12.1.0 Released

Raytac Corporation

A BT4.1 & BT4.2 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF51802)

www.raytac.com

Tel: +886.2.3234.0208

email: service@raytac.com  
 https://raytacblog.wordpress.com/

Nordic relleased nRF5 SDK V12.1.0

Software Update

nRF5 SDK v.12.1.0

Software Development Kit for the nRF51 Series and nRF52 Series.

Highlights of this release:

• Added serialization of the S132 SoftDevice v3.0.0. Serialization of S130 is now deprecated.
• Included the latest MDK v8.9.0 with a crucial workaround for nRF52832 Errata 108.

More information in the release notes (inside the download).

❱ Download here 

❱ Online documentation here 

Nordic nRF5x MDK v8.9.0 released

Raytac Corporation

A BT4.1 & BT4.2 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF51802)

www.raytac.com

Tel: +886.2.3234.0208

email: service@raytac.com  
 https://raytacblog.wordpress.com/

Nordic has released the nRF5x MDK v8.9.0 in 20 Sep., 2016

Software Update:   The nRF5x MDK v8.9.0 has been released.  Changelog: Updated compiler abstraction header files with __ALIGN macro for IAR compiler and __PACKED macro. Added Baud56000 to UART enumerated values in nrf51_bitfields and nrf52_bitfields. Added missing macro transformations in nrf51_to_nrf52.h compatibility header file. Added missing macros for FPU and SYSTICK in nrf52832_peripheral.h header file. Updated RAM size in nRF52832 device in keil4 device database. No longer reflecting EngA size but EngB and FP1. Renamed some files for IAR EW IDE. Added workaround for Errata 108 into system_nrf52.c. Please choose your download below: ❱ nRF5x MDK for Keil4 and Keil5 compatibility version ❱ nRF5x MDK for GCC ❱ nRF5x MDK for IAR Embedded Workbench ❱ nRF5x MDK pack

MDBT42Q Series Module (Nordic nRF52 Solution) Spec Sheet Updated

Raytac Corporation

A BT4.1 & BT4.2 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF51802)

www.raytac.com

Tel: +886.2.3234.0208

email: service@raytac.com  
 https://raytacblog.wordpress.com/

http://bluetooth.tokyo

MDBT42 and MDBT42Q, solution by Nordic nRF52832, recently has FCC/CE/IC/Telec/SRRC/NCC granted.

We are sincerely invite all developers to download the updated Specification Sheet from below Link.

Products which built by MDBT42 or MDBT42Q now allowed to get rid of annoying safety regulation application and testing but ship and marketing in USA, Canada, Japan, China according to Module Approval Policy.

MDBT42 & MDBT42-P Spec Sheet Download Link

http://www.raytac.com/download/MDBT42/MDBT42Q-Version%20B.pdf

What is the difference between BT 4.1 & BT 4.2

Raytac Corporation

A BT4.1 & BT4.2 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF51802)

www.raytac.com

Tel: +886.2.3234.0208

email: service@raytac.com  
 https://raytacblog.wordpress.com/

http://bluetooth.tokyo

What is BT 4.1 and 4.2~ That is a frequent question for our customers.

Here, we quoted some information from SIG to help readers have easy understanding between different Bluetooth version.

BT 4.1

This updated specification aims to improve consumer usability with increased co-existence support for LTE,  efficient data exchange rates, and aid developer innovation by allowing devices to support multiple roles simultaneously. 

• Improving Usability—extends the brand promise to consumers with an “it just works” experience. This spec is engineered with several new features to make it work seamlessly with popular cell technologies like LTE, maintain connections with less frequent manual reconnection, and deliver a more efficient data exchange.
• Empowering Developer Innovation—provides developers with greater flexibility to create innovative Bluetooth products and solutions through dual-mode topology and link-layer topology software features.
• Enabling the Internet of Things—lays the groundwork for IP-based connections by allowing devices to setup a dedicated communication channel in the future thereby extending the central position for Bluetooth technology in the Internet of Things.

BT 4.2

Key updates in 4.2 improve privacy and increase speed, and a soon-to-be ratified profile will enable IP connectivity.

• Privacy and Security

Bluetooth 4.2 introduces industry-leading privacy settings that lowers power consumption and builds upon the government-grade security features of the Bluetooth specification. The new privacy features put control back into the hands of the consumer by making it difficult for eavesdroppers to track a device through its Bluetooth connection without permission. For example, when shopping in a retail store with beacons, unless you’ve enabled permission for the beacon to engage with your device, you can’t be tracked.

• Speed

Bluetooth 4.2 increases the speed and reliability of data transfers between Bluetooth Smart devices. By increasing the capacity of Bluetooth Smart packets, devices transfer data up to 2.5 times faster than with previous versions. Increased data transfer speeds and packet capacity reduces the opportunity for transmission errors to occur and reduces battery consumption, resulting in a more efficient connection. 

• Internet Connectivity

Building on the capabilities released earlier with Bluetooth 4.1 and the new features released in 4.2, the Internet Protocol Support Profile (IPSP) will allow Bluetooth Smart sensors to access the Internet directly via IPv6/6LoWPAN. IP connectivity makes it possible to use existing IP infrastructure to manage Bluetooth Smart “edge” devices. This is ideal for connected home scenarios that need both personal and wide area control. This profile will be ratified by the end of the year.

What is dBm?

Raytac Corporation

A BT4.1 & BT4.2 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF51802)

www.raytac.com

Tel: +886.2.3234.0208

email: service@raytac.com  
 https://raytacblog.wordpress.com/

http://bluetooth.tokyo

What is dBM?

From Spec sheet, we can find the output power always stated as dBM.

For example:

Nordic nRF52832
Transmitting power (+4dBM~-20dBM) / Receiving Sensitivity (-96dBM)

dBm is the unit for radiowave, it is a way to express the comparison between the reference signal value

The reference value is 0dBM at 1mW, the unit represented as shown below

1/10000 times = -40 dBm
1/1000 times = -30 dBm
1/100 times = -20 dBm
1/10 times = -10 dBm
1mW =     0 dbm ← Reference Signal Value
10 times  =  10 dBm
100 times  =  20 dBm
1000 times  =  30 dBm