Raytac MDBT50Q-RX Dongle (nRF52840) LED problem

[Thierry]

Hello!

I managed to flash my Raytac dongle with debugging going using the SWD on a nrf52 DK.
I am mainly working with SEGGER Embedded Studio and nRF Connect on Mac.
However, it seems any function from simple_hal simply won't work...

I created a new header file in SDK/components/boards/ which defines the only LED of the Raytac MDBT50Q-RX Dongle:

...
// LED definitions for MDBT50Q-RX
#define LEDS_NUMBER    1

#define LED_1          NRF_GPIO_PIN_MAP(1,13)

#define LED_START      LED_1
#define LED_STOP       LED_1

#define LEDS_LIST { LED_1 }
...

Sadly, my application (using the mesh SDK) just won't light up with the Raytac dongle, while working perfectly with the nRF52840 DK (PCA10056) and the nordic nRF52840 Dongle (PCA10059)

Until I included these 2 lines in my main.c:

nrf_gpio_cfg_output(LED_1);
nrf_gpio_pin_write(LED_1, value);

I could reproduce this on both the light_switch server & client.

If anyone could enlighten me.. ^^

Thank you!

PS: if this is truly impossible, could someone guide me onto how to write an async blink?
This is blocking the process quite a bit:

for(int i=0; i<10; i++) {
  nrf_gpio_pin_write(LED_1, i%2);
  nrf_delay_ms(500);
}

[Vidar Berg]

Hi,

I'm not sure why it's not working. The pin assignment seems to be correct since nrf_gpio_pin_write() works. Can you try to debug the app and check whether bsp_board_led_on() calls nrf_gpio_pin_write() with the correct parameters? Also, try to program hex file attached below to see if it works. It's using BSP to toggle the LED @ 1 s intervals. 

bsp_pca10056.hex

[Thierry]

Hello, thank you for your time.
The hex file is working!

However, bsp_board_led_on() does not seem to be called.
boards.c wasn't even in my project nor the other mesh example projects...

Calling the function in main, I actually found out that

bsp_board_led_off(LED_1);

turns the led on, and

bsp_board_led_on(LED_1);

turns the led off...

Once again after

nrf_gpio_cfg_output(LED_1);

I am still looking into it.

[Thierry]

So we have the pin (1,13) for this LED, which with the function NRF_GPIO_PIN_MAP(1,13) translates to 45.

Then, in simple_hal.c in the function hal_leds_init :

NRF_GPIO->OUTSET = 1UL << i;

Which becomes 00000000000000000000000000000001 << 45;
This would exceed the capacity and become 0. Am I right?


So the LED is never "initialized"?

[Vidar Berg]

Yes, seems like the project is not set up correctly for the 52840 which has 2 GPIO ports. The bit should have been written to NRF_P1, not NRF_GPIO. Are you testing this with a SDK example? 

[Thierry]

My application is derived from a bunch of them. Mainly the light switch.

I have found a little work around.
In SDK_15.3.0/modules/mdk/nrf51_to_nrf52840.h line 144 : 

/* GPIO */
/* GPIO port was renamed to P0. */
#ifndef NRF_GPIO
    #define NRF_GPIO        NRF_P0
#endif
#ifndef NRF_GPIO_BASE
    #define NRF_GPIO_BASE   NRF_P0_BASE
#endif

If I change p0 to p1,
and also change my pin definition (1,13) to 

NRF_GPIO_PIN_MAP(0,13)

Everything seems to work.

[Vidar Berg]

This workaround may be problematic if you want to use port 0. I would suggest to go over the project setup and compare it to a 52840 SDK project to find out why the wrong header files are being included.