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

What is the difference between PCA10040 and PCA20020?

PCA10040 and PCA20020 both use nrf52832 and s132 softdevices but still when I try to run the code for PCA10040 on PCA20020 it does not work? 

Parents Reply Children
  • That's right. Thanks. What board header file are you using? Which SDK are you currently running? You might have more luck if you add the pca20026 header file from the thingy sdk & try running an sdk example. The SDK examples will most likely not work out of the box with the Thingy device though. I would recommend starting with downloading the thingy sdk & take that as a starting point. The Thingy SDK is based on sdk 13 & is the normal FW that is loaded on the Thingy:52 device when you receive it.

    My guess is you would need to make quite a few changes to get the mesh sdk to work on the Thingy. If you really want to run mesh on multiple Thingy devices, you could take a look at this source code here.

  • Hello,

    Just a minor point, but would be good for anyone else accessing this post... I believe that the Nordic Thingy:52 is marked up as PCA20020 (and not PCA20026)

    Regards,

  • I am using SDK 15.0.0, I have added the board file and   yes the board is PCA20020 sorry for that.

    I have tried the mesh sdk for Thingy 52 so I have successfully run the thingy bridge and thingy node setup..but only thing is lets say I want to run the light server example from mesh sdk on thingy then what all changes do I have to make(Please give me steps involved in setting up a mesh network). I have put the header file for pca20020 in the code and tried to run 1 thingy as provisioner and 2 other as server but the thingy's with server code on it is not getting provisioned which has been verified by the nrf connect app.

  • I would use the thingy mesh demo that you mention instead. The mesh sdk has not been made for the Thingy:52, as the Thingy:52 is more of a prototype demo kit, while the dev kits are full out development kits made for development. If you really want to run the mesh sdk, I would take a look at the difference between the thingy bridge & thingy node setup & compare that with the light switch provisioner, client & server examples from the mesh sdk.

    Have you tried debugging the Thingy code to see why the server does not get provisioned? Are you using mesh sdk v1 or v2? Take a look at the mesh documentation for more info on building a mesh network.

  • I am using the latest mesh sdk i.e 2.0.1.

    I just found out while debugging nrf52 dk (which is used as provisioner) that I can provision the thingy's but the only thing was in light switch example it initially provisions the client and then the servers. I saw in the log that all thingy got provisioned which was verified in nrf Connect app as well. But yeah I cannot control the leds through the thingy's button. So as you have suggested I probably have to tweak thingy bridge and thingy node code to make it work for light switch example.

Related