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

Thingy52 Eclipse debug setup

Hi all,

I have a Thingy52 and a nRF52-DK.

I have successfully setup 2 different Eclipse projects to compile code for both hardware.

On the nRF52-DK, i was able to build the blinky project, run the SEGGER-J-Link debug config and step through the project.

I setup the thingy project in a similar fashion. I can reach to a point where I can build the project, the debug config seems to be able to flash the code onto the board, but the debugger cannot find the main function nor allow me to even step through whatever it is seeing. I simply don't have any control over the debugger.

I was debugging through the nRF52-DK. i.e. using the small thin ribbon cable connecting nRF52-DK debug out to the Thingy52.

With this hardware setup, i am able to read the Thingy52 flash content using the nRF utilities or latest nRF goStudio. With that said, I suppose at least the hardware connection is correct that i can somehow communicate with the Thingy52.

Has anybody have any success setting up a Eclipse project, specifically the debugging part, for the Thingy52 hardware?

I have a feeling that it may be related to the bootloader code that's already in the flash, but not exactly sure if its correct or how to fix it.

Having the debugging capability is definitely ideal, but it is my second priority here.

My first priority is to be able to at least modify the Thingy52 code, change some behaviors and flash it to the HW.

What I attempted was simply changing the Bluetooth disconnect status LED color from Blue to White. I flashed in the new code, but the Thingy52 is still blinking with the blue LED.

I had this default LED config changed:

#define UI_CONFIG_DEFAULT_DISCONNECTED                          \
{                                                               \
    .mode = BLE_UIS_LED_MODE_BREATHE,                           \
    .data =                                                     \
    {                                                           \
        .mode_breathe =                                         \
        {                                                       \
            .color_mix  = (uint8_t)DRV_EXT_LIGHT_COLOR_BLUE,    \
            .intensity  = DEFAULT_LED_INTENSITY_PERCENT,        \
            .delay      = DEFAULT_LED_OFF_TIME_MS               \
        }                                                       \
    }                                                           \
}

I had read the full flash content for both the Blue code and White code. A hex comparison showing there is only that 1 bit difference between the 2 copies. Yet, the Thingy52 did not behave what I expected. I am expecting the LED will slowly blink white given it is not connected to any host device.

 Is it not the right code to change the default setting? What am I missing here?

Any help is appreciated. Thanks!

Ricky

Related