Dev kits supplied by 3rd party module makers [n00b]

Question

Hi, 
 I attended a training session run by the BT SIG last week and met a helpful Nordic chap who, when I mused about how I was using a programming board to run a sensor and a radio, helpfully suggested that using an NRF52 I "just connect your sensor directly to the chip". This was revolutionary to me. 
 I've been loitering since then in an effort to find out how I might go about that, but not found the answer to this question which is bugging me. 
 I am a BTL n00b, but a programmer all the same - so all the code made sense to me - plus I've used the NRF240L01 in projects previously, and now have my hands on the NRF52 dev kit. 
 Just to get some proof of concepts out of the door I know I will be initially using 3rd party modules containing NRF52 chips, but am getting confused because these suppliers (inevitably) supply their own DKs. 
 Laird is a good example as is Rigado . 
 I've watched videos and read posts and it my understanding that the development process will go something to the tune of: 
 
 programme the nrf52 to do something in the Nordic DK, using the s/w tools from the Nordic site 
 add/remove my sensors and generally play and test in that environment 
 flash that finalised "program" to the nrf52 chip on the module 
 
 
 Q1 Would I need to buy the module makers' DK? 
 Q2 IF NO, would I need to make sure the module exposed jtag connections? 
 Q3 OR Could I not flash the nrf52 over the air? 
 
 I have to imagine all the major steps in my head before I move in a certain direction, and this is blocking me. Thanks for any pointers.

RK · Accepted Answer

Are you talking about how to move from a development environment to a production board using 3rd party modules? If so the answers to your questions are 
 1, 2, 3. Yes. 
 
 
 No. All the manufacturer dev kits are just dev boards with their version of the nRF52 carrier board on board and some LEDs and buttons etc. You're fine just using the Nordic dev kit and then creating a board using the 3rd party kit. 
 
 
 Yes it would need to expose SWD connections, but they all do (see answer below) 
 
 
 That depends. If a module comes without anything on it then no you can't flash it over the air, you have to hook up the debug interface and put some code on it. Some of the modules you can buy have very exposed edge contacts and it would be simple to construct a quick 'bed of nails' board to connect to them and initially program them, then solder them in. The old Rigado BMD-200 module was like that, the new BMD-300, not so. Some of the modules however do come with software pre-installed, again Rigado is an example (sorry but I've used their stuff more than anything else before starting to make my own layouts). If the chip comes pre-programmed with a DFU over the air solution, you can use that.
I always put an SWD interface on my boards because I always want the option of putting a hardware debugger on them if something goes wrong. You can use a small-footprint debug connector if you expect to use it rarely, or put the layout on the board but only populate the connector if you need it.

Dev kits supplied by 3rd party module makers [n00b]

Top Replies