Hello,
I made a custom PCB without connecting VBAT1V to the ground and I observed the VDCDC voltage comes around 1V.
AS per DA14583 datasheet on page 143 ,Note 17: When VBAT1V > VDCDC_nominal, VDCDC will follow VBAT1V
I searched for way to set VDCDC_nominal but could not find anything .
Inside SDK I could see 3 control registers available named DCDC_CTRL_REG, DCDC_CTRL2_REG, DCDC_CTRL3_REG
有什么办法可以配置这些注册isters in order to get 1.4V at VDCDC.
Keywords:
Device:
Hi Muhammadali,
Please follow the guidelines mentioned on the Tutorial 7: DA1458x prototype bring up guide. Regarding the 1.4V on the DCDC this is the voltage that the DCDC should have when the device is awake. If you are measuring the DCDC close to 1V that means that the device is in sleep mode. Also the VDCDC_nominal is the typical value of the VDCDC and you cannot configure other output values to the VDCDC, this applies on Boost mode since if VBAT1V is larger than the 1.4V that the DCDC can provide as output, then the VDCDC will follow the VBAT1V.
Thanks MT_dialog
Thanks for your prompt response. As per the instructions provided in Tutorial 7: DA1458x prototype bring up guide ,I downloaded empty_peripheral_template.hex file in the SDK . Default sleep mode is ARCH_SLEEP_OFF . Still the measured voltage at VDCDC is 1V. I am powering the device in Buck Mode. But as mentioned earlier I did not connect the VBAT1V to ground and it is not possible to connect it now. So I am wondering if this can be the reason for 1V at VDCDC .
Also my Bluetooth is not powering up. Occasionally Bluetooth pops up in LightBlue App with very good signal strength ,but after few seconds it goes away. So this because linked to the output voltage at VDCDC?
Is there any workaround other than connecting VBAT1V to ground in Buck Mode?
Thanks in Advance
Hi Muhammadali,
Regarding the fact that your central device occasionally picks up the bluetooth, i am not sure what exactly you mean, but this is how the BLE operates, when advertising you set up an advertising interval, that means that the BLE will go to sleep and wake up in that interval, the BLE protocol dicates that a device should have a specifed RF activity and then go back to sleep for a predefined time before waking up again. In the case of the template project the device is going to sleep and wakes up for advertising every 687.5 ms (this is defined in the user_adv_conf structure in the user_config.h file). Also the fact that you are advertising every 687 ms doesn't mean that the central will pick up all the advertising events that the device emmits.
Regarding the fact that if forgetting to connect the VBAT1V to ground while operating in Buck mode and if that can will bring the voltage output of the DCDC close to 1V, i am not aware about that, since this is against the specs that dialog provides, i strongly recommend to change that and manufacture a board according to the guidelines of Dialog. What i can mention about having the VBAT1V pin floating is that the device wont be able to decide on which mode the DCDC should operate since the VBAT1V is the pin that the hw fsm checks in order set the appropriate mode.
Thanks MT_dialog