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

Can I directly start programming a nrf51822 breakout board

Hi guys, I want to know if it is possible to get started on developing applications for nRF51822 without using the evaluation kit. I want ot have a couple of breakout boards made and buy a debugger to flash the code on the board. Is this even possible? Also are there are good docs which tell us how to get started?

  • Yes and no.

    You could buy a Segger programmer and flash the chip with it. I don't know of any open source debugger (like OpenOCD) that can yet flash/debug the nrf51822 part (it has some special characteristics like combining RESET and SWDIO). It would be awesome to make this happen though (I have high hopes for the mchck in this regard).

    I have an example project here that demonstrates using the Segger programmer and GCC. You'll need to edit the Makefile to set NRF51_USE_SOFTDEVICE=0.

    However, the soft device binary that includes the bluetooth stack is only available with the eval kit or dev kit. You need an alphanumeric product key from the kit to access the download links on Nordic's site (and the license prohibits redistribution) I've asked Nordic a couple of times to release the soft device freely on their web site and they've said they'd consider it but haven't done so yet. So as of right now, if you want bluetooth, you'll need a Nordic Dev or Eval kit.

    Honestly, the Dev Kit is a pretty great deal: 5 chips, a Segger debugger (alone worth >$70) and a very convenient USB dongle, for $99. Until the open source community catches up with this chip (which I'm hoping will happen very soon), I'd recommend spending the $99.

    Hope this helps. I'd really love to see a strong open source community around this awesome chip.

    -c

  • Thanks a lot for the reply. Also I was just curoius, cant we use some other open source Bluetooth stack instead of SoftDevice like https://code.google.com/p/btstack/wiki/BLE as long as we have access to the packet frame ?

  • In theory, I suppose you could write your own (or adapt an existing) stack for this chip. I'd guess it would a whole lot of work. The peripherals and setup of this chip are like nothing else I've ever seen.

  • Because that's an API not a "stack". It relies on third party PHY and radio layers.

    Of course, you're welcome to implement your own silicon, PHY and other radio components :)

    -m

  • I've made some limited progress towards using the McHck to program and debug an nRF51822 dev board. I don't have breakpoints working yet, but I'm hopeful that with some help from the McHck folks, we'll get that working.

    For those of you following along at home, however, I still recommend the Dev Kit as the best way to get started, and the only way to get legal access to the soft device BLE stack.

    I'm hoping that Nordic will take notice of the fact that a fully-open-source toolchain exists for their great chip, and allow access to the soft device binary without a Dev Kit license.

    I'll keep this updated as we progress.

    Thanks,

    -c

    PS– @marc, you don't need special PHY, etc to write an open source BLE stack for the nRF51822. The existing, closed source stack uses the well documented radio, address resolver, etc features of the nRF51822 chip. It would be a lot of work though to reimplement this well.

Related