LP_CFG_RCX20——醒来可能使用额外的即兴表演ve connection stability?

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
5 posts / 0 new
Last post
uta_lc
Offline
Last seen:11 months 3 weeks ago
Joined:2016-05-03 07:39
LP_CFG_RCX20——醒来可能使用额外的即兴表演ve connection stability?

Dear DLG expert,

On DA14581, we are trying to use internal RC oscillator to achieve relatively long connection interval (2s), is it possible at all?

We've tried using 500ppm SCA configuration but still found BLE connection stability issue with 2s connection interval (we understand that the spec from DLG says 500ppm if wake up period is 1s). After trolling some docs, we've got the following idea and can you please help us to validate if it is doable?

In stead of purely relying on BLE wake up event (for Rx & Tx), we schedule an additional wake up event which performs RCX 32K calibration only (using system provided function which measures the gap between 32K and 16M). In the additional wake up, the next wake up cycle (for BLE rx &Tx) is recalculated and scheduled. This hopefully can achieve more accurate wake up timing, hence can help improve connection stability.

Just wonder if the idea is plausible or not? If yes, can you please point out what should be done to make it happen?

Thanks in advance,
uta_lc

Keywords:
Device:
uta_lc
Offline
Last seen:11 months 3 weeks ago
Joined:2016-05-03 07:39
Can someone from DLG support

Can someone from DLG support comment on this please? It is a bit urgent for us.

Thanks

PM_Dialog
Offline
Last seen:1 day 6 hours ago
Staff
Joined:2018-02-08 11:03
Hi uta_lc,

Hi uta_lc,

If the DA14585 is configured in buck mode, you can use either the RCX or the XTAL32 as a low power clock. Otherwise, if you are in boost mode then your only option is the XTAL32. From my side, I used the RCX as a low power clock, and I was able to have 2seconds connection interval. You don’t need to do the procedure that you have described, as in every wake-up the RCX is calibrated and it is accurate enough for you implementation. The requirement for the usage of the RCX is to have the device configured in buck mode. Also, the XTAL16M adaptive settling algorithm works only with XTAL23K and not with RCX, as the LP clock. So, in order to use the RCX you should do undefine the CFG_XTAL16M_ADAPTIVE_SETTLING in the da1458x_config_advanced.h header file.

Thanks, PM_Dialog

rajucoolsuraj
Offline
Last seen:5 months 3 weeks ago
Joined:2018-12-12 16:09
Hello Dialog,

Hello Dialog,

To enable DA14586 operation in Buck Mode -

PMU_CTRL_REG (FORCE_BUCK, 0x01);

DCDC_CTRL2_REG(DCDC_TON, 0x02);

DCDC_CTRL2_REG(DCDC_AUTO_CAL, 0x01);

the above configuration should be handled from system_init() ??

Is not, what is the procedure to put DA14586 in Buck Mode and where to add code in SDK 6.0.10?

Thanks

Raju

PM_Dialog
Offline
Last seen:1 day 6 hours ago
Staff
Joined:2018-02-08 11:03
Hi rajucoolsuraj,

Hi rajucoolsuraj,

Please try to not duplicate your questions on the forum. Yours questions has been answered in your previous post below:

https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-software/change-system-clocks-internal-rc

Thanks, PM_Dialog