Using NRF52 (NRF52832) as bluetooth module for my psoc 6

[kjs_eir]

Hi 

I have a mbed application, which runs on a PSOC6 MCU, i am going to be using a fanstel BC832 (which is based of NRF52832)BT module for RF-communication. To verify that my project can run on the fanstel module, I have the nRF52, until I get my board with the fanstel module. I am using mbed 5.14.1, which uses cordio stack for uart communication with the bt module. 

So i got two question: 
1) is there a specfic .hex which needs to be on my nRF52 when using it as a BT module? if, where can i find this? 
2) Might be out of scope, but how do i configure my mbed setup, so i am using the correct nordic drivers? 

Thanks 

[kjs_eir]

Hung Bui  apperently the hci_uart requires additional configuration from the host in order to start advertising. If i add 0x0105200666371104E5E1 (which sets a connection handler, min and max connection interval) and 0x0109202012110723D1BCEA5F782315DEEF12122315000000000000000000000000000000 (which configured my advertising data, and modify 0x0106200FA000F0000001000000000000000700, so that it uses a random address instead of a public, i can make my device advertise and connectable. Otherwise the "0x010A200101"  # HCI LE Enable Advertising is return with a 0x12 error code (invalid HCI command) 
u
I found these missing commands by decoding your scope data, thank you very much. 

But to me it seems weird that a nordic HCI controller behave so differently then other HCI controller which I work with. Additionaly now that the device is connectable, I am facing issue with making my uuids available for the connected device. Indicating that i need to further modify the HCI command sequence. Any helps would be highly appreciated. 

Thanks,

[Hung Bui]

Hi Karl-Johan, 

Our softdevice controller strictly follows the HCI protocol from Bluetooth SIG so I'm quite surprised that it behave differently to other HCI controller. 
It would be easier for me (who doesn't work with raw HCI very often ) if you can translate the commands into readable API commands so I can check why the controller return the error code. Please pay extra attention to the address you use as public address and random address has a different flag bit to indicate if it's random or public (as far as I remember). 

kjs_eir said:

I am facing issue with making my uuids available for the connected device. Indicating that i need to further modify the HCI command sequence.

Please give more info on this issue. My suggestion is to try testing/debugging this with a BLE sample (with host and controller running on the same chip). After you make it work you can intercept the internal HCI communication and find the correct HCI sequence/commands.