Porting a program from NRF52 DK to NRF52 Thingy.

[Niranjan Pandian]

I am trying to port a tested program from NRF52 DK to NRF Thingy. To do the same I had changed the board to PCA20020. After I do that, I program using the NRF52 debug out pin. The outcome is, Green Light on the Thingy is blinking, not sure why though. I am trying to scan the device using nrf connect ios app, which couldnt detect. 

Its a simple broadcaster of a value over GAP advertising. I am using SDK 16, SD 132 version 7 and Segger embedded studio. the following are my questions / doubts.

1. I am trying to go through the SDK 16 support for the thingy 52 on the documentation, but i couldn't find any specific support, although I could find PCA20020 board file on the SDK, i just want to ensure that SDK 16 supports Thingy board. Is there any other SDK configuration needs to be done?

2. I am not sure y the RGB LED is blinking? Any reasons? I havent included the Thingy SDK. 

3. Does Jlink RTT viewer does work through the debug out port in NRF52 DK? 

[awneil]

Niranjan Pandian said:

I am trying to go through the SDK 16 support for the thingy 52 on the documentation, but i couldn't find any specific support,

There isn't any - the thingy is in a "world of its own"

Niranjan Pandian said:

i just want to ensure that SDK 16 supports Thingy board

It "supports" it in exactly the way that it "supports" any other custom board.

Niranjan Pandian said:

I am not sure y the RGB LED is blinking?

Because you're toggling the pin(s) that drive it!

Niranjan Pandian said:

Does Jlink RTT viewer does work through the debug out port in NRF52 DK? 

Yes - you're just using the DK as a J-Link.

[Niranjan Pandian]

Thank you for the reply. follow up question.

1. SDK16 "supports" thingy as a custom board or PCA20020 board? 

awneil said:

Because you're toggling the pin(s) that drive it!

I am not doing it on my program and thats I was unsure. 

[awneil]

Niranjan Pandian said:

1. SDK16 "supports" thingy as a custom board or PCA20020 board? 

Depends what you mean by "supports" ?

The SDK actually supports the chip - the board it's on is irrelevant to how the chip works.

The Thingy LEDs are on an I2C IO expander - you must be doing something to that ...