SDK 6.0.8.
Hi
我根据您的参考设计开发了PCB，包括I2C传感器设备。
我已经将SW刻录到OTP，在功能上，设备似乎按预期运行，在按钮上唤醒并执行POR。然而，设备的当前测量报告了110A的读数，延伸和深度睡眠模式。
I have removed the sensor from the board, and the current usage is still high.
This current reading is taken with a CR2032 cell powering the device, with no debugger etc connected at all - just the bare device, using an accurate DMM.
I can send details of my design if there is a location I can send them direct to.
任何想法吗?
谢谢！
设备：
Hi boydy1989,
The 110uA is an unexpected current consumption in both extended and deep sleep mode configuration. I strongly suggest you to read theTutorial 4 : configuring sleep mode on DA1458x从我们的支持页面中，以确保使用正确的方式测量当前消耗。此外，请注意，您定制PCB上的某些内容可能会增加当前的消耗，因此请先查看它。
Thanks, PM_Dialog
你好
I have followed this tutorial in some detail already, in fact I used it as the basis for establishing these measurements.
I have also removed everything else from the PCB that could draw current - the only thing that reduces the current usage is removing the power to the DA14585.
Please can you offer some more thoughts, again I am happy to send schematic or code over privately if this is possible.
谢谢！
Hi boydy1989,
如果您正确地正确地进行了参考设计，则在睡眠模式配置中不应具有太多的电流消耗。你能否请确保芯片睡觉？
Thanks, PM_Dialog
你好
I have just checked, and changing
static const sleep_state_t app_default_sleep_mode = arch_ext_sleep_on;
to
static const sleep_state_t app_default_sleep_mode = arch_sleep_off;
makes the device draw ~550uA, rather than the ~110uA with pulses for advertising packets. This would suggest to me that the device is entering extended sleep in at least some form.
Anything further I can check?
谢谢！
我已经运行了更多的测试。使用Prox_reporter项目，我获得了〜250A的更高睡眠电流绘制。
The only difference between the packaged project and what I have flashed is that I am using the internal LF clock, not a 32k crystal.
I have attached a current trace showing an advertising package. (Red line is raw data, green line is a 10 sample rolling average)
Reverting to my code, I see ~110uA again. I have also attached a trace of an advertising package. (second page)
接下来，我会用DA14585子板尝试相同，而不是使用自己的PCB比较。
In the meantime, can you please offer some more ideas?
谢谢！
Hi boydy1989,
As I am able to understand from you post, the current consumption is 550 nano Ampere in active mode configuration? Did I understand correctly? Be aware that is a wrong measurement, because in active mode the current consumption is ~0,6mA. Did you use power profiler from SmartSnippets studio in order to check if the device advertises? If yes, the current consumption is 550nA? With our DA14585 DK, what current consumption did you get? If I understood correctly from your second post, you do not have an external XTAL32, so are you using the internal RCX20 clock as low power clock?
Thanks, PM_Dialog
道歉 - na是一个错误，the correct value is 550uA (0.6mA) for active mode, 110 uA for sleep. I have corrected the post above.
I am using my own power profiler to take the advertising current, using a self designed tool. I have verified the accuracy, and can confirm that it is accurate enough for what I require.
I can confirm the device advertises correctly, and all other functions work as expected - I have verified this with a bluetooth scanner and our own in house app which is in development. The current spikes visible in my previously attached PDF align with the received advertising packets.
Your understanding is correct, I am using the internal RCX20 for the low power clock.
谢谢！
你好
I think I have solved this. On my PCB I had connected pin 5 (VCC_FLASH/P3_0) to 3.3v. If I cut this track, the current during sleep drops to ~3uA as expected.
Can you please suggest why this may be?
谢谢！
Hi boydy1989,
您可以澄清您在您的定制董事会中使用哪种芯片？DA14585或DA14586？在您发布的线程中，您已标记DA14585 SoC。虽然，DA14585没有VCC_FLASH。只有DA14586 VCC_FLASH GPIO，因为它具有嵌入式SPI Flash。如果您使用DA14586，根据数据表，VCC_FLASH应提供1.8 V至3.6 V.如果切割此曲目，则无法访问SPI Flash，因此我建议您将其保持为3.3V.最可能的原因是您没有为SPI闪光灯供电，所以这就是为什么获得高电流消耗。请尝试将其供电并再次检查当前的消耗。
Thanks, PM_Dialog
你好
我正在使用da14585。我的初始原型使用了586，但我意识到我不需要SPI闪光，所以我切换到585。
I have verified the fix on a second PCB now, and the current is also reduced to ~3uA.
谢谢！
Hi boydy1989,
Glad that your problem has been fixed. If you found any of the above answers useful please mark one of them as accepted.
Thanks, PM_Dialog