Using MDBT42Q and BLE

RE: Using MDBT42Q and BLE

schosdas — Sat, 31 Oct 2020 13:58:38 GMT

Hello, JimP.

It's been a long time since you posted this article, but I have a question to ask you.
I'm going to use MDBT42Q for the first time, too. When I use this module using SDK, can I do a BLE example of SDK without modifying the pin number of PCA10040?

Thank you.

RE: Using MDBT42Q and BLE

JimP — Tue, 15 Jan 2019 14:02:25 GMT

Thank you all for your patience and help. I'll try your suggestions and let you know how it worked.

RE: Using MDBT42Q and BLE

Einar Thorsrud — Tue, 15 Jan 2019 12:41:09 GMT

The pack installer examples are very outdated and should not be used. They are not compatible with SDK 15. CMSIS Pack have not been used to distribute the SDK for a long time, as it was deprecated with the release of SDK 10 (see Deprecating support for CMSIS Pack in nRF5 SDK).

You will find an updated and compatible ble_app_blinky example in SDK 15 under <SDK>\examples\ble_peripheral\ble_app_blinky. In a nutshell: Unless you are working with legacy code which predates SDK 10 you should never use the pack installer to install or use any SDK component.

RE: Using MDBT42Q and BLE

awneil — Tue, 15 Jan 2019 12:13:00 GMT

[quote userid="71102" url="~/f/nordic-q-a/42212/using-mdbt42q-and-ble/165716"]Tell me how to change to a custom board[/quote]

The "official" way is to add to boards.h:

:
:
#elif defined (BOARD_D52DK1)
  #include "d52_starterkit.h"
#elif defined (BOARD_ARDUINO_PRIMO)
  #include "arduino_primo.h"
#elif defined (CUSTOM_BOARD_INC)
  #include STRINGIFY(CUSTOM_BOARD_INC.h)
#elif defined(BOARD_TOM)
  #include "tom.h"
#elif defined(BOARD_DICK)
  #include "dick.h"
#elif defined(BOARD_HARRY)
  #include "harry.h"
#elif defined(BOARD_CUSTOM)
  #include "custom_board.h"
#else
#error "Board is not defined"

Take, say, your DK board header and use that as the basis for creating your custom one.

infocenter.nordicsemi.com/index.jsp

devzone.nordicsemi.com/.../supporting-a-custom-board-with-nrf5-sdk-examples

Or, for a quick check, just hack the DK file!

[quote userid="71102" url="~/f/nordic-q-a/42212/using-mdbt42q-and-ble/165716"]the example using the SOFTDEVICE_HANDLER works when you change the clock, but the UART example doesn't[/quote]

So step through the code in each case, and see where they diverge?

Because stepping & breakpoints are likely to crash the SoftDevice, you may need to look into Monitor Mode Debugging:

https://devzone.nordicsemi.com/b/blog/posts/monitor-mode-debugging---revolutionize-the-way-you-debug-ble-applications

https://github.com/NordicPlayground/j-link-monitoring-mode-debugging/#monitor-mode-debugging-in-keil-%C2%B5vision5-and-segger-embedded-studio

and/or instrument the code with RTT or whatever ...

RE: Using MDBT42Q and BLE

JimP — Tue, 15 Jan 2019 11:57:18 GMT

That's great. I'm using nRF5_SDK_15.0.0_a53641a. But the example is from the pack installer.

Go to pack installer and under Nordic select nRF52832 on left side. On right side click on Examples tab.

Go down to "Experimental_ble_app_blinky_s132_pca10040" and copy to a folder. Keil will open with the example loaded and you should be able to make the clock change (SOFTDEVICE_HANDLER) without problem. You will need to load the nRF_blinky app on your phone to test.

Tell me how to change to a custom board so I can try that. What board should I put into the header?

The thing I find interesting is that the example using the SOFTDEVICE_HANDLER works when you change the clock, but the UART example doesn't after making the same changes to the config file. I'm sure it must be something simple but haven't figured it out yet.

Thank you for continuing to work on this - much appreciated.

RE: Using MDBT42Q and BLE

etx — Tue, 15 Jan 2019 02:16:54 GMT

I got mine going on the MDBT42Q, i think it was an issue with the default pca10040 board header. After switching to a custom board definition it's working.

I'd love to try loading the same example you are to help but I cannot find that example. I'm using nRF5_SDK_15.2.0_9412b96.zip and building with armgcc for my application. Let me know.

RE: Using MDBT42Q and BLE

etx — Mon, 14 Jan 2019 15:22:07 GMT

He is rude and looking at his post history he has that tone with everyone. I'll just switch to another platform if that is how this community is run.

RE: Using MDBT42Q and BLE

JimP — Mon, 14 Jan 2019 14:30:27 GMT

here is what I've learned.

From the pack installer load the "experimental_ble_app_blinky_s132_pca10040" example.

connect the MDBT42Q and erase the chip with nRFgo Studio.

Load the Softdevice.

In the program comment out //SOFTDEVICE_HANDLER(NRF_CLOCK_LFCLKSCR_XTAL_20_PPM, false);

replace with :

SOFTDEVICE_HANDLER(NRF_CLOCK_LFCLKSCR_RC_250_PPM_250MS_CALIBRATION, false);

load the program. You should be able to connect by running the nRF Blinky app on your phone. The LED on/of will toggle pin 17 and if you ground pin 13 you should see the button pressed/released toggle on the phone.

There is still a problem with UART programs - they don't use SOFTDEVICE_HANDLER. What is the difference between using SOFTDEVICE_HANDLER and the way connection is managed with UART program?

RE: Using MDBT42Q and BLE

Einar Thorsrud — Mon, 14 Jan 2019 07:58:44 GMT

Please keep a civil tone. awneil's questions and suggestions make full sense.

And to sum up: The only relevant difference between the 52832 DK and the MDBT42Q module is that the DK has a 32 kHz crystal and the module does not. So as long as you remember to configure the SoftDevice to use the internal 32 kHz RC instead of the non-existing 32 kHz crystal oscillator everything should work as on the DK.

RE: Using MDBT42Q and BLE

JimP — Sun, 13 Jan 2019 13:20:56 GMT

EXT:

I had the exact same experience.

I'm using version 15 of SDK also. I've noticed a few differences in the code depending on the example you start with and where you get the example code. Some code has SOFT_DEVICE_HANDLER but not all.

I'm planning to test a few variations later today and will post exactly the version I start with, changes I make, and results.

RE: Using MDBT42Q and BLE

etx — Sat, 12 Jan 2019 22:06:00 GMT

Thanks for posting, glad you got it going!

I'll double check my connections but the NRF52-DK seems to be flashing the MDBT42Q with the application and SD without any errors. I'm not connecting the reset pin, is that required?

You much be using an older SDK, I don't see that macro (SOFTDEVICE_HANDLER_INIT) in version 15 of the SDK which is what I'm using. But I have tried setting the equivalent defines in the sdk_config.h so it should equate to the same settings for the clock. Still no love... I'll keep trying.

I should add, like you the examples that don't use the SD work fine. Blinky for example runs fine as I made a board file for the MDBT42Q with proper pin configurations.

RE: Using MDBT42Q and BLE

etx — Sat, 12 Jan 2019 21:32:53 GMT

Thank you for bringing zero value to this thread.

I did everything the OP posted before I found this thread. That's why I posted to see if he had come up with anything.

Yes.

If you're not going to be constructive and act like a neckbeard please just move along.

RE: Using MDBT42Q and BLE

awneil — Sat, 12 Jan 2019 15:10:59 GMT

[quote userid="71102" url="~/f/nordic-q-a/42212/using-mdbt42q-and-ble/165298"]Use the debugger on SDK board instead of the mini JLink I have been using. I don't understand why this worked - but it did.[/quote]

You'd need to take that up with Adafruit.

RE: Using MDBT42Q and BLE

JimP — Sat, 12 Jan 2019 15:02:32 GMT

I haven't tested this extensively but I'm now able to communicate with the MDBT42Q via BLE. It involved 2 steps.

1. you need to change the clock source in the ble_stack_init function (or wherever the soft device handler is located) as follows:

change:

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, false);

to:

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_500MS_CALIBRATION, false);

Use the debugger on SDK board instead of the mini JLink I have been using. I don't understand why this worked - but it did.

I made an 8 pin connector for the 8 pins next to the PCA10040. VDD and VTG are connected to SDK VDD 3.3 V supply. SWDIO connect to MDBT Module SWDIO (pin 37). SWDCLK to MDBT Module SWDCLK (Pin 36) and Reset to MDBT Module reset (Pin 35). SWO not connected. GND detect connected to common ground on both SDK board and Module. In my setup the module is connected to separate 3.3v supply with common ground. VDD nRF is not connected.

Since making those changes I've been able to load programs on the SDK board and test them and then connect the MDBT module (via the 8 pin connector) and load the same softdevice and program. The Module then runs the program the same as the SDK board.

I've tested the BLE_blinky program and that works on MDBT the same as the SDK board using nRF Blinky app on android phone.

RE: Using MDBT42Q and BLE

awneil — Sat, 12 Jan 2019 10:37:40 GMT

[quote userid="76429" url="~/f/nordic-q-a/42212/using-mdbt42q-and-ble/165275"]I'm having the same issue. [/quote]

How do you know it's the same issue?

What debugging have you done to find where the problem is ?

Have you programmed the SoftDevice?

Have you tested with an unmodified Nordic example?

RE: Using MDBT42Q and BLE

etx — Sat, 12 Jan 2019 02:55:30 GMT

I'm having the same issue. Code runs and works well on the PCA10040 but I'd like to flash it to a MDBT42Q. I also tried switching to RC clock but it'd not working out.

Please post if you find a fix. Thanks!

RE: Using MDBT42Q and BLE

Einar Thorsrud — Wed, 09 Jan 2019 08:26:09 GMT

I see. Did you remember to flash the SoftDevice as well as the application? If so yes and it still does not work, have you done some debugging to see what is happening on the target?

RE: Using MDBT42Q and BLE

JimP — Tue, 08 Jan 2019 14:32:52 GMT

Thank you Einar. Based on you comment - In SDK_CONFIG - I set NRF_SDH_CLOCK_LF_SRC 0 //set to RC and NRF_SDH_CLOCK_LF_ACCURACY 1 // set tp 500 ppm - per waring

but still can't connect to the module. I must still be missing something. Any other suggestions?

Thanks for your help.

RE: Using MDBT42Q and BLE

Einar Thorsrud — Tue, 08 Jan 2019 10:28:49 GMT

Hi,

Essentially this is just a nRF52832 module, so I recommend you use the normal nRF5 SDK (latest is 15.2) instead of featherboard (or other) stuff. The module includes the 32 MHz crystal, but there is no 32 kHz crystal (optional). Note that the nRF SDK examples assume that the crystal is present, so you have to adapt the SoftDevice configuration to use the internal RC instead. Other than that, you should expect any SDK examples to work out of the box.

RE: Using MDBT42Q and BLE

JimP — Mon, 07 Jan 2019 15:55:25 GMT

Yes. I'm using the module you show in the link. Yes - I'm using Keil as IDE - supplemented with nRFgo studio.

I haven't configured to use internal oscillator. How would I do that?

The featherboard comes with Arduino IDE. There must be a way to convert for Keil but I don't know how to do that.

Thank you for your help

RE: Using MDBT42Q and BLE

awneil — Mon, 07 Jan 2019 15:07:27 GMT

[quote userid="71102" url="~/f/nordic-q-a/42212/using-mdbt42q-and-ble"]MDBT42Q modules from Mouser (they are made by Seeed Studios)[/quote]

You mean these: https://www.mouser.co.uk/ProductDetail/Seeed-Studio/317030213?qs=sGAEpiMZZMs1xdPSgahjwiL2lJlP6L5V96Mk9IiRNC0%3d ?

[quote userid="71102" url="~/f/nordic-q-a/42212/using-mdbt42q-and-ble"]The datasheet for the MDBT42Q basically says that you don't need any external circuitry to make the module work, so it may not be a clock problem - but I'm not sure[/quote]

Probably means that you have to configure it to use the internal oscillator - have you done that?

[quote userid="71102" url="~/f/nordic-q-a/42212/using-mdbt42q-and-ble"] I believe this is the same module used by Adafruit on their Featherboard 52832[/quote]

Would be a good idea to get an Adafruit Featherboard 52832 - then you'd at least have a know-good hardware platform to start with ...

[quote userid="71102" url="~/f/nordic-q-a/42212/using-mdbt42q-and-ble"]There is a warning that there is a 32Kb limit on evaluation in debug[/quote]

Are you using Keil, then?

Segger Embedded Studio (SES) is free & unlimited for use with Nordic ARM-based SOCs ...