This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrdf52840 missing NRF_LOG messages and SD not running on BT840

Hello.  I'm developing a project using nRF52840.  I've been working with the nRF52840Dev Board and I have a BLE project that runs there.  I'm developing in Segger IDE and using J-Link Terminal. Im developing a project based around PCA10056 board and s140.

I have 2 problems, both of which seem to have some feedback here on the Nordicsemi support site, but the instructions that I see haven't led to any success:

1) NRF_LOG messages. I can never find the messages from NRF_LOG (for example NRF_LOG_DEBUG("Notify observer 0x%08X => blocking", p_observer);  They simply don't appear in the RTT Viewer, even though all the settings are intended to direct them there.  To get around this, I have been using sprintf and SEGGER_RTT_WriteString.  However, I think that exposing these messages is important because of problem 2 is a deeper problem.


2) I've developed a custom board using a BT840 module.  I expected that the project that I've made would just run there (it uses SD, as a BLE peripheral).  The project is based on BLE SDK examples (however, the first piece of code to the SD (ble_stack_init() err_code = nrf_sdh_enable_request() hangs, which is different than the dev board.  

I'm now realizing that I need to master the bootloader/SD linkage/app linkage setup in the project download, and  


I've erased the the device (BT840) and loaded the bootloader per the manufacturers instructions, I'm realizing that there is probably more to do than this.  I see some references to options for external clocks and preprocessor directives that need to be set.  

Some direction on either of these 2 problems is helpful.

  • Thanks for your help.  I am posting this here to explain to the larger group what to do to get the code running on the Fanstel BC840.  It appears that the device is supplied with a bootloader that only works with their application, and SES wasn't clearing this factory bootloader.

    All that was needed to get the chip correctly cleared was to do:

    nrfjprog --eraseall

    Then program my application and the SD via the J-Link SWD connection.   

    Somehow the Fanstel bootloader didn't get the SD running, and I was not replacing it without nrfjprog --eraseall 

Related