Hostless vs Hosted Bluetooth LE design

I'm trying to go through the proes and cons of a Hosted Vs Hostless Solution for BLE using the nRF52840.  I have an AP thats running a stripped down version of Linux.  Currently I have the Host Stack running on the AP and the nRF52840 configured just as a BLE Controller.  Works fine, however I have to wake-up my AP to perform any BLE operations, so it consumes more power than ideal.  I thought about reconfiguring the nRF52840 to run the full Stack (hostless) and configure an API between the nRF52 and my AP.  However this isn't a design configuration I see often when an AP is present.  Is there any obvious reason for this I'm missing?  Yes I'd have to essential maintain two code streams, but the potential hand-off operations to the nRF52 could save alot of power.  Anyone have good insight into the Pros/Cons of these design configurations? 

  • Hello,

    Think this will be mainly depending on the application, I can see the potential to lower power if you run the host on the nRF52840 and thereby can optimize the serial interface (and lower the current). However, you may end up with a less generic solution if you run the host on the nRF52840, but if you know exactly what peer you want to connect (e.g. in terms of features and behaviour) then it should not be a problem to run the host on the nRF52840 either.

    Kenneth

Related