Hi there,
Here introduce the firmware perspective about how to program your code onto MDBT50Q-RX dongle.
Believed all readers have done the hardware setting and now has well prepared to load the code onto the dongle. (If not yet done the hardware setting, pls find it here)
In this blog, we will introduce the procedure based on below 2 scenarios
From the article “Change to nRF52833 module? What the Hardware & Firmware Setting Need To Review?“, Raytac has highlighted Keil users need to update nRF Device Family Pack version to 8.27.1 for SDK16
Here introduced how to change the nRF DeviceFamilyPack version.
Developer who currently are using nRF52840 based modules must be excited waiting for nRF52833’s distribution. Most developers are aware that nRF52833 supports long range, multi protocol and USB interface but has less RAM and Flash memory rather than nRF52840 and no doubt is the best alternative to have cost effective without extra efforts.
Raytac has released 3 models of nRF52833 based modules just at the same time when Nordic released, MDBT50Q-512K / MDBT50Q-P512K / MDBT50Q-U512K. Both nRF52840 and nRF52833 module are based on same form factor and pin out. To have quick visual identification finding the difference, Raytac’s nRF52833 modules are built by Green PCB but nRF52840 modules are Blue.
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
SoftDevice + Bootloader+ Application
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!
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.
Check out the link below for a reference example on Nordic’s DevZone.
Reference link: Nordic DevZone – NFC pins into GPIOs
Setting up Nordic’s IDE (Integrated Development Environment) is the first step into Bluetooth product development, and it’s also where most developers need support.
In order for developers to be able to smoothly set up their IDE, Raytac hereby provide you with a few easy steps.
First and foremost – In terms of IDEs, there are currently four different ones that are all viable; Segger Embedded Studio (SES), Keil C, IAR and GCC. Among these, SES and GCC are IDEs free of charge while Keil C and IAR both require the developer to pay a license fee to their respective company.
We at Raytac generally recommend SES, as it is an IDE brought forth by both Nordic and Segger together and it uses Segger J-Link. Although GCC is a free IDE, it only builds code and is impractical editting make file or debugging firmware. Thus, it’s not our primary choice.
Therefore, we will hereby provide you a step-by-step guide on how to set up your IDE when using SES.
https://www.segger.com/downloads/embedded-studio/
https://developer.nordicsemi.com/nRF5_SDK/nRF5_SDK_v15.x.x/
Key in Name, Company name, Address and PC’s MAC address. Then press “Request License”, the “License key” will send to your mail box automatically.
Tips: How look up PC’s Mac address: Pls enter DOS mode,
Key in ipconfig/all,
The Mac address will be found in Ethernet card.
CMSIS Configuration Wizard,
..\examples\ble_peripheral\ble_app_uart\pca10040\s132\ses\ble_app_uart_pca10040_s132.emProject
Build Code & Debug
Many customers are using Raytac’s Demo board for firmware development and debug.
Here we provide easy setup way for customer reference.
Raytac Corporation 