Hello Dialog,
Several questions:
1) Sleep mode is the same as Active mode when idle (DA14850 in active mode but no operation running)? Documentation is confusing about this topic. What is the current consumption for this Sleep mode?
2) What is the timing and power profile of the DA14850 from Extended Sleep (and Deep Sleep) up to the point of starting to advertise?
3) It's mandatory to use RivieraWaves Kernel OS in a Fully-Hosted solution, right? but, is it mandatory to use it in the external processor of a Fully-Embedded solution which runs both the profile and the application? and what if the external MCU only implements the application (in this case the profile is run by the DA14850)?
4) OTP memory programming is only possible by using the SmartSnippets software? or there is the possiblility of loading the code to DA14580's OTP memory through a SPI or UART communication by the external MCU (Fully-Embedded solution)? If so, how?
5) How can the transmission output power of the DA14580 be changed in the proximity application project example? I have seen that the proximity application uses an output power of -6dBm aprox. and I would like to test it with 0dBm.
6) UM-B-013 DA14580 External processor interface over SPI document is referred on several documents but it is not available inhttp://support.dialog-semiconductor.com/.
Thanks,
Hi Mamigot,
I am sorry if you find the documentation a bit confusing and I will try to clarify you questions.
1) The current consumption for "sleep mode" is around 600uA and this is where DA14580 is active but the ARM core is in idle.
2) For these timings it will take the DA14580 around 9mS from extended sleep until start advertising and from wake-up until finished the advertising event it will take around 15mS. From Deep Sleep this is longer and the time is around 30mS. For the extended sleep mode timings it's easiest to see if you try to use the Power Profiler in the SmartSnippets tool.
3),您将使用一个独立的应用程序the implemented OS/sequencer which the SDK are built upon. But if you are using an external host for the application and or profiles you can use whatever OS you want to implement. The SDK 3.0.2 does include a windows application.
4) The OTP memory can be programmed by UART or JTAG. We have implemented this function on SmartSnippets but this is not limited to SmartSnippets and you can implement this on your external MCU. I would recommend that you look in xx for further information and if you have questions after that then please ask again. The one thing that you need to make sure is that you can provide a 6.8v supply to VPP and that you can control that this voltage isn't enabled all the time in your product. I will update you on this question when I have got a more detailed description of this.
5) The Transmission output is fixed at 0 dBm so you can't change this to -6 dBm. When measuring this with a frequency analyser make sure that you are measuring on a fixed frequency.
6) The plan was that this document should have been released now but we have had a slight delay and we are currently in the review process of this document. This should be uploaded to this site within the next week.
Best Regards
TN_Dialog