Using MDBT42Q and BLE

user71102 said:

MDBT42Q modules from Mouser (they are made by Seeed Studios)

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

user71102 said:

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

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

user71102 said:

I believe this is the same module used by Adafruit on their Featherboard 52832

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 ...

user71102 said:

There is a warning that there is a 32Kb limit on evaluation in debug

Are you using Keil, then?

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

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

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!

user76429 said:

I'm having the same issue.

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?

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);

2.

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.  

user71102 said:

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.

You'd need to take that up with Adafruit.

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.

Yes.

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

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.

Yes.

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

Please keep a civil tone. user6462'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.

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?

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.

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.

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.