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

how can I make nRF52832 talk to nRF51822 (BLE)

I want nRF52832 to be a central device which will take an input from nRF51822 (peripheral device). Also, Is it possible to make two nRF51822 talk to each other?

Parents
  • You should be able to do both of those things just fine. It's not clear how you want them to "talk", but you should probably find a starting point in the examples Most of the examples have been around for a long time, so even if you're using s132 on one device and s110 on the other, you can probably just use s132 with an example from the latest SDK and s110 with an example from something older.

  • There is of course no example of exactly BLEnano board in Nordic SDK, because simply Nordic don't produce them However modifying any example to different HW layout (when it shares the chip variant with the original) is super easy: as board headers are included in every project, just define BOARD_CUSTOM globally in your project - e.g. in Makefile - and then create custom_board.h with desired content (e.g. by starting from some Nordic PCAxxxxx.h file as example). You can see more about that construction in .\components\boards\boards.h. I usually use even two stage approach so I define both BOARD_CUSTOM and BOARD_BLENANO (in your case) and then write just basic if/else sequence in custom_board.h pointing to actual header file with all the functional defines and values (e.g. board_blenano.h file in your case).

Reply
  • There is of course no example of exactly BLEnano board in Nordic SDK, because simply Nordic don't produce them However modifying any example to different HW layout (when it shares the chip variant with the original) is super easy: as board headers are included in every project, just define BOARD_CUSTOM globally in your project - e.g. in Makefile - and then create custom_board.h with desired content (e.g. by starting from some Nordic PCAxxxxx.h file as example). You can see more about that construction in .\components\boards\boards.h. I usually use even two stage approach so I define both BOARD_CUSTOM and BOARD_BLENANO (in your case) and then write just basic if/else sequence in custom_board.h pointing to actual header file with all the functional defines and values (e.g. board_blenano.h file in your case).

Children
No Data
Related