Application not running on a Rigado BMD-300

[drumm3r]

Hi all

Being fairly new to the nRF ecosystem I'm trying to get some basic code up and running on a custom board which uses a Rigado BMD-300. I'm using one of the examples in the SDK, and this runs fine on the Development Kit I have (PCA10040) but not on the BMD-300. I have updated the configuration of the clock sources as per this post (https://rigado.zendesk.com/hc/en-us/articles/225674668-Example-files-will-not-run-on-my-hardware-but-do-on-the-Eval-board-) 

However although the device programs and verifies fine (from both Segger Embedded Studio and nRFgo Studio) I see absolutely nothing - no flashing LEDs and nothing being advertised. Power seems fine, but I don't see a peep from the custom board.

I'm a bit stumped - what should I try next!

Thanks!

[awneil]

drumm3r said:

what should I try next!

Use the debugger to see if the code is getting stuck or crashing somewhere ...

[drumm3r]

Ok, very good point! It seems that although the debugger throws no errors at all (seems to program fine then run) it isn't actually running the code. I can't step through the code, and it doesn't hit any breakpoints at all.

It is weird how I see no errors though!

[awneil]

As Jared, you should contact Rigado to check what specific changes should be made for their particular module.

Do Rigado provide some examples specifically for your module that you could try?

[drumm3r]

Thanks, I will try that. However in the meantime I am wondering whether the issue is to do with the lack of 32kHz crystal on the custom board (which is included on the DK). As per my original post I have updated the sdk_config.h file to reflect this, but do I need to do anything similar for the SoftDevice? If so where can I find this configuration file?

Thanks again

[awneil]

This seems to be quite a frequently recurring question.

Don't Rigado provide an example?

Have you tried looking at the "Related" threads that the forum suggests:

[drumm3r]

Hi

Re Rigado examples, not as far as I can see (though I'm still looking). They state that the examples that run on the DK I have (PCA10040) will also run on the BMD-300.

Yes, I have checked the related threads and have not found an answered question that relates to mine.

As per my post above, I am trying to figure out whether/how the SoftDevice needs to be configured to use the internal RC low frequency oscillator rather than the external 32kHz crystal, which is not present on my board.

[drumm3r]

Ok, just jumping in on my own question: I now have some working code though I'm not entirely clear why!

By using a sample application provided in this thread (https://devzone.nordicsemi.com/f/nordic-q-a/21113/running-basic-tutorial-on-custom-breakout-board), programming both their Softdevice and application my board now advertises. I then used Segger Embedded Studio to debug a different application which (according to the log) overwrote the SoftDevice but despite this the application still runs.

It's not clear to me why programming a SD designed to work with the internal RC oscillator worked, but continued to do so after writing a new SD which I don't believe is set up to use this same oscillator.

Either way, for the moment (until I learn more about configuring the SoftDevice) the issue is solved. Thanks to all for the help (although tips on configuring the SD still welcome!)

[awneil]

AFAIK, there are not separate SoftDevices for working with and without an external crystal - it's just a matter of configuration ?

[drumm3r]

I see. In that case could you point me towards this configuration? I've been searching the forums and although I've found references to the changes needed they all assume you know where to look to actually make these changes!

[awneil]

Sorry - I've always worked with a crystal!

[drumm3r]

No problem - all this digging around at least means I'm getting more familiar with the setup! Thanks again for all your help

[Jared]

The sdk_config file configures which clock source that is used by the project. You can configure it to use the RC by setting it to 0: 

// <e> NRFX_CLOCK_ENABLED - nrfx_clock - CLOCK peripheral driver
//==========================================================
#ifndef NRFX_CLOCK_ENABLED
#define NRFX_CLOCK_ENABLED 0
#endif
// <o> NRFX_CLOCK_CONFIG_LF_SRC  - LF Clock Source
 
// <0=> RC 
// <1=> XTAL 
// <2=> Synth 
// <131073=> External Low Swing 
// <196609=> External Full Swing