Chew: It really depends on how you want your stack to operate alongside the bluetooth stack (in the time domain). This is a bit hard to put into words, but an example might help. Consider a bluetooth connection. If you are connected to a bluetooth device do you want your RF stack to run in between the connection events? Or do you run the bluetooth stack, finish up with any connections or other advertising/scanning events, then run your RF stack?
> On Nov 15, 2016, at 10:46 PM, L.M Chew <[email protected]> wrote: > > Hi Aditi, > > Thanks for the welcome. :-) > > Currently we have a proprietary RF Stack firmware (it uses proprietary air > protocol) running on a nRF52 chip, we are using Nordic's SDK + FreeRTOS to > build this. > > Now we want to port part of the RF Stack firmware into Mynewt so that our > nRF52 device can switch between NimBLE stack and our own RF stack to > communicate BLE device and our own proprietary RF device. > > So we like to know what is the best way to do this. > > Best Regards, > Chew > >> Hi Chew, >> >> Welcome to the Mynewt community! Could you provide a little more detail >> about what you’d >> like to do? Do you have a radio with a proprietary implementation of the >> controller that you >> want to integrate with the host portion of the NimBLE stack? The HCI API >> will come in handy >> there. If you want to take our NimBLE stack and tweak it, you can do that in >> a fork of the >> repo. If you tell us a little more we can respond better. >> >> thanks, >> aditi >> >> > On Nov 15, 2016, at 12:18 AM, L.M Chew <[email protected]> wrote: >> > >> > Hi, >> > >> > I like to get some pointer on how to implement my company own proprietary >> > Custom RF Stack >> aside the Nimble BLE Stack. >> > >> > Best Regards, >> > Chew > >
