cancel
Showing results for 
Search instead for 
Did you mean: 

why bluenrg1 Controller privacy requires 32MHz High Speed Crystal?

Hi :

I noticed that Controller privacy requires 32MHz High Speed Crystal in BlueNRG-1_2 DK 3.2.3\Project\BLE_Examples\BLE_Privacy\src\BLE_Privacy_main.c, but I don't find any document about this.

Meanwhile, my platform has 16M high speed crystal, I modify HS_SPEED_XTAL_32MHZ to HS_SPEED_XTAL_16MHZ then flash this demo and can't scan the bluenrg1 device(the demo has name "pslave"). is there any workaround so that I can use Controller privacy with 16M high speed crystal?

Comment.png

@LauraCx @Rene Lenerve @Laurent LOUAZON 

4 REPLIES 4
Laurent LOUAZON
ST Employee

Hello,

This is right, privacy requires 32MHz xtal as more PIPS are required.
A 32MHz xtal is mandatory for such application. No workaround.

Regards
Laurent

 

 

Hi @Laurent LOUAZON 

Thank you for your reply.

But according to BlueNRG Errata sheet, ADC does not work properly when a 32 MHz system clock is being used. Does this mean we can only choose one between ADC and Controller privacy?

Laurent LOUAZON
ST Employee

Hello,

 

Yes this is unfortunately correct.

 

Laurent

Hi @Laurent LOUAZON :

accroding to following clock tree, 32M XO can be devided with 2. Do you mean even if I use 32M XO then devided with 2, ADC and Controller privacy still can't work together?

meanwhile, Is there any method that I can enable bonding with 16M XO? I can't enable bonding using BlueNRG1 and android 13. Attachment is my code.

clock tree.png