已加入：duce that code execution will be possible by use of the OTPC memory bus interface. This would allow for application use of a considerable amount of additional RAM memory at the expense at probably higher power consumption and considerably more difficult software development? Is this assumption correct?
已加入：s the AES engine accessible by user code when the BLE-Stack is running?
已加入：ipherals be operated from the 32 kHz clock source?
已加入：s there a software reference manual available detailing the properties of the peripherals?
已加入：been designed with ultra low power consumption in mind and OTP memory has a higher power consumption than SRAM, therefor it is not possible to run an application directly from OTP memory.
已加入：, I deduce also any read access) is not possible from the OTP, what is the amount of RAM required by the bluetooth stack modules (GATT,GAPP, L2CAP, etc.) together for code and ram (database, state machine, etc.) ?
已加入：nds heavily on the configuration. As an indication, it would, e.g. be helpful to have the figures of the memory requirement for a reference system, e.g. stack consumption for a blood pressure peripheral not supporting encryption.
已加入：orking on a document with the RAM requirement estimations for different profiles. At this moment these figures are not available yet.
已加入：y accessible by the user code when the BLE link is not using encryption.
已加入：Mhz clock.
已加入：SW programming manual is not available yet.
已加入：g up from deep sleep? This would be the time it takes for the application to start when waking up from deep sleep.
已加入：,
我们正在编写一份文件，其中包含不同配置文件的RAM需求估计。ll OTP mirroring action takes about 1.2 milli-second.
已加入：st regards, Dialog Support Team.