Simon Rühle

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

4 years, 9 months ago.

Problem with custom board

Hello together, I hope I got the correct space. We created a custom board based on a nRF52832. Main difference to the NRF52_DK is another Pin Mapping and that we do not have an external clock. Additionally we program the chip with a JLink via the generated hex file. Unfortunately the LED does not blink with the blinky example. Is there any good entry point on how to debug why it fails.

This is the custom_target is tried to use: { "MYCOOLBOARD": { "inherits": [ "NRF52_DK" ], "release_versions": [ "5" ], "device_name": "MYCOOLBOARD", "config": { "clock_src": { "value": "RC" } }, "features": [ ] } }

1 Answer

Desmond Chen
4 years, 9 months ago.

Hi Simon,

Pin Mapping is always the first one to check when doing porting.

Your config seems not correct, clock source should be set like below.

targets.json

"MCU_NRF52832": {
    ...
    "config": {
            "lf_clock_src": {
                "macro_name": "MBED_CONF_NORDIC_NRF_LF_CLOCK_SRC",
                "help": "Select Low Frequency clock source. Options: NRF_LF_SRC_XTAL, NRF_LF_SRC_SYNTH, and NRF_LF_SRC_RC",
                "value": "NRF_LF_SRC_RC"
            }
    }   
    ...
}

Desmond