using internal 32K instead external

6 posts / 0 new
Last post
slava
Offline
Last seen:3 years 7 months ago
加入:2015-04-28 10:35
using internal 32K instead external

I trying to run code from Proximity Tag example on my board. 32K crystall do not fitted on board.
I define CFG_EXT_SLEEP in da14580_config.h file and and set DEVELOPMENT_DEBUG to 0 then burn compiled image in SPI flash.
After reset I can see 5 led flashes and then it turned off. When I press button nothing is happend.
I suppose that da14580 goes into extend sleep mode and cant wake up.

If I right, is it possible to change clock source to internal oscillator? What changes I need to do?
Thank you in advance.

Device:
slava
Offline
Last seen:3 years 7 months ago
加入:2015-04-28 10:35
I solve this problem by

I solved this problem by setting CFG_LP_CLK to 0xAA.

slava
Offline
Last seen:3 years 7 months ago
加入:2015-04-28 10:35
I have new question. After

I have new question. After about 4 minutes without connection smart tag goes to sleep and LED do not blink more. At this state I can see 0.001 mA of board power consumption.
But when it is connected to my smartphone minimum measured value is 0.130 mA. How can I decrease this current?

MT_dialog
Offline
Last seen:3 months 1 day ago
Staff
加入:2015-06-08 11:34
Hi slava,

Hi slava,

The power consumption while connected is depended on the connection interval of your device since the more you sleep the less you consume although there is a tradeoff, that fact that you have so large intervals keeps the receiver of your device more time active in order to poll the master due to innaccurancies of the clock. Therefore you can experiment with the connection intervals of your device and check what suits you best. Please check the Smart Tag application note.

Thanks MT_dialog

slava
Offline
Last seen:3 years 7 months ago
加入:2015-04-28 10:35
Thank you for response.

Thank you for response.
I want to share some test data.
I tried to connect proximity tag with standart firmware with 3 different devices.
1) with smartphone. Power consumption is 130 uA
2) with PC with WIN10. Power consumption is 100uA
3) other DA14580 module with proximity monitor firmware. Power consumption is 50uA.

MT_dialog
Offline
Last seen:3 months 1 day ago
Staff
加入:2015-06-08 11:34
Hi slava,

Hi slava,

I suppose that you are troubled by the different power consumptions of the application on different operating systems. As i ve mentioned in my previous post, in connected state the main power consumption coefficient is the connection parameters. The problem with the connection intervals is that they are not set by the peripheral but by the central. Therefore no matter what are the connection parameters you ve set on your peripheral the central is the one that decides the values of the connection parameters. I suppose this is the reason why you are getting different power consumption on different hosts.

Thanks MT_dialog

Topic locked