The problem about the Power Profiler in SmartSnippets tool.

2 posts / 0 new
Last post
Bean
Offline
Last seen:3 years 6 months ago
Joined:2014-07-24 08:51
The problem about the Power Profiler in SmartSnippets tool.

Hi,Dialog!

I recently tested the Power Profiler, using DA1458x_DSPS_v_5.150.2, SmartSnipppets and DA14580 Bluetooth® Smart Development Kit - Expert ,like the attachment 1.

In my project,
(1) Configuration GPIO in user_periph_setup.h :
#define GPIO_CON_PORT GPIO_PORT_0
#define GPIO_CON_PIN GPIO_PIN_6
#define GPIO_BLOOD_CON GPIO_CON_PORT,GPIO_CON_PIN
(2) Map port pins in set_pad_functions() in user_periph_setup.c
GPIO_ConfigurePin(GPIO_BLOOD_CON, OUTPUT, PID_GPIO, false);
(3)编译DA1458x_DSPS_v_5.150.2 sps_device_580.hex file.
(4) Download sps_device_580.hex file to DA14580 Bluetooth® Smart Development Kit - Expert by SmartSnipppets. Then, start ‘Power Profiler’ and find the Avg Current(mA) is 0.0235mA.

And only change the GPIO_PIN_6 to GPIO_PIN_3, then recompile the program, and download sps_device_580.hex file to DA14580 Bluetooth® Smart Development Kit - Expert by
SmartSnipppets. In the ‘Power Profiler’ , I found the Avg Current(mA) is 0.5889mA.

My problem ,as the attachment:
I onl change the gpio P06 to P03, and get a different value. Why this is?

Attachment:
Device:
MT_dialog
Offline
Last seen:1 month 3 weeks ago
Staff
Joined:2015-06-08 11:34
Hi Bean,

Hi Bean,

The GPIO_PIN_3 is allready used by the DSPS software as the RTS pin, if you have previously reserved your pins before configuring them this shouldn't have worked at all, since the SDK would have warned you that the specific pin is allocated twice. Although i ve tested the above configuration without reserving the pin i couldn't see any additional current in smart snippets when the GPIO_PIN_3 is used as a normal gpio output.

Thanks MT_dialog

Topic locked