[sdk5]problem about ext_sleep

Hi kurbylee,

我已经测试了你的设置,它似乎工作好。我的年代uppose that you are using Smart Snippets to burn your SPI, do you make your device bootable when you are promted from Smart Snippets ? After burning the flash do you reset your board in order for the bootloader to run and boot from your SPI ? By setting the app_default_sleep_mode to ARCH_EXT_SLEEP_ON is enough to set your device to extended sleep. Are you able to see your device correctly when you dont use sleep mode?

Thanks MT_dialog

Hi kurbylee,

I tested your setup again with a fresh 5.0.3 SDK and burn the image to the flash, it booted normally in reset and by removing the power. Are you able to donwload code by using keil, if yes is the device advertising as it should be ?

Thanks MT_dialog

Hi ggotta,

Can you please explain what your problem is ? In the SDK 5 if you want to enable the 580 in sleep mode all you have to do is to set your default sleep mode to ARCH_EXT_SLEEP_ON. The rf_nfm_disable has to do with the near field mode operation and not the sleep operation. The function isn't invoked in the SDK by default its just the API for disabling the near field mode if enabled.

Thanks MT_dialog

Hi Ggotta,

我遇到和你同样的问题,使EXT_SLE之后EP_ON, my phone can't scan the DA now except power on DA time.

How you solve the issue finally? Is it true to only change:
just chang SetWord16(RF_ENABLE_CONFIG13_REG, PREF_RF_ENABLE_CONFIG13_REG);
to SetWord16(RF_ENABLE_CONFIG13_REG, 0);
in func rf_nfm_disable

Or other time setting is also necessary?

Hi smdzjl007,

As mentioned above in the previous comment, the rf_nfm_disable doesn't have to do with the sleep but with the near field mode which is disabled by default. In order to put the 580 in sleep mode only the app_default_sleep_mode = ARCH_EXT_SLEEP_ON; is enough to put the device in sleep mode. What is the SDK that you are using, and are you experincing this on a dev kit or on a custom board ? If you are able to scan the device only for a couple of seconds, then either something is wrong with your low power clock or the debuuger stays attached to your device and prevents it from going to sleep if you are using an SDK prior to the SDK 5.0.4.

Thanks MT_dialog

Dear MT_dialog team,

Thanks for your help. Yes, I do find out that modification within rf_nfm_disable function doesn't work at all. I am using SDK 5.0.3. How to locate the problem is related with low power clock or other reason? Should I upgrade to SDK 5.0.4?

Another question, after DA14580 enter to sleep mode, what timer setting to control the wake up from sleep? what timer to control wake up duration?

Thanks & Best regards,

Hi smdzji007,

The rf_nfm_disable() function doesn't have to do anything with the sleep, if you move to the new SDK 5.0.4 the debugger isn't disabled during sleep so your device should continue advertise even if the debugger stays attached. If by moving into the new SDK doesn't help and you have a custom board check the setting of your LP clock should be either XTAL or RCX, if you are operating under buck mode and you switch to RCX and then you are able to see advertising, then your problem is the external XTAL32 that you have on your custom board.

The SDK takes care of how long the device will stay in sleep mode and when to wake up, all you have to do is set the advertising and connection intervals and the SDK will take care of the rest and configure the system to wake up on time and sleep as well.

Thanks MT_dialog

Thanks, MT_Dialog team, very timely feedback!

I tried to modify user_config.h for advertising and connection intervals as below, actual user_connection_param_conf is not changed:

static const struct advertise_configuration user_adv_conf = {
.addr_src = GAPM_PUBLIC_ADDR,
.renew_dur = 0,
.addr = {0x1, 0x2, 0x3, 0x4, 0x5, 0x6},
.intv_min = 1000, // 625 ms (1000*0.625ms)
.intv_max = 2000, // 1250 ms (2000*0.625ms)
.channel_map = 0x7,
.mode = GAP_GEN_DISCOVERABLE,
.adv_filt_policy = ADV_ALLOW_SCAN_ANY_CON_ANY,
.peer_addr = {0x1, 0x2, 0x3, 0x4, 0x5, 0x6},
.peer_addr_type = 0,
};

static const struct connection_param_configuration user_connection_param_conf = {
.intv_min = MS_TO_DOUBLESLOTS(20),
.intv_max = MS_TO_DOUBLESLOTS(100),
.latency = 0,
.time_out = MS_TO_TIMERUNITS(125),
.ce_len_min = MS_TO_DOUBLESLOTS(0),
.ce_len_max = MS_TO_DOUBLESLOTS(0),
};

But the test result is still failed, the device can broadcast BLE advertisement message for very short time, then sleep and my smartphone can't scan the device anymore.

what else structure should I modify to make it sleep/wakeup as normal wearable device?

Thanks & Best regards

Hi smdzj007,

I would suggest not to modify anything (in order to verify that the reason for the 580 not advertising is not the fw), just take ble example from the 5.0.4 as is and run it to sleep mode (const static sleep_state_t app_default_sleep_mode = ARCH_EXT_SLEEP_ON;) in the user_config.h file also run the same example with const static sleep_state_t app_default_sleep_mode = ARCH_SLEEP_OFF; and check if you do that is the device advertising and if it does you will have to set the sleeping mode always to off (ARCH_SLEEP_OFF). Do the above and let me know. Also please let me know if you are using a custom board or a dev kit and if you are using an external XTAL or you are operating with the RCX.

Thanks MT_dialog

Thanks, MT_Dialog team!

I upload my .hex file to other dialog support engineer, he see the same result as me.
https://support.dialog-semiconductor.com/smartsnippets-spi-flash-program...

He is using 580 dev kit pro. My design is also use dialog reference design with external XTAL clock. It works fine if switch off sleep.

Anyway, I will try again to download 5.0.4 sdk example to see any difference or not.

In the meanwhile, can you confirm my previous question about advertising and connection intervals adjustment? Are those 2 structures correct? Is my interval setting valid?

Thanks & Best regards

Hi MT_Dialog team,

After checking with previous colleague, he told me that our design is based on dialog wechat sdk reference design:
https://support.dialog-semiconductor.com/connectivity/reference-designs?...

I tried to download wechat sdk reference design and run it to sleep mode (const static sleep_state_t app_default_sleep_mode = ARCH_EXT_SLEEP_ON;) in the user_config.h file. The problem is the same as mine, device sleep and can't be discovered by smart phone app: AirSyncDebugger

Two questions here:
- did wechat SDK reference design tested for extended sleep mode?
- how to replace wechat SDK reference design used dialog SDK to 5.0.4 standard SDK?

Thanks & Best regards,

Hi smdzjl007,

- Yes, the wechat is tested to operate under extended sleep mode and i am also able to see the advertising string when the device is in sleep mode.

——我不问题,你的意思是如何replace the fw ? You can run directly one of the SDK examples via JTAG or you can download the .hex file of the examples via UART or if you have a flash, you can burn the flash and upon power up the 580 will download the code from the flash.

Thanks MT_dialog

Hi MT_Dialog team,

The question is coming from fact that: wechat reference design was released with 14580 SDK version x at Nov'15, as there is new 14580 sdk version 5.0.4 recently, if I need upgrade wechat reference design sdk source into 5.0.4 sdk, what procedure should I do?

Thanks & Best regards,

Hi smdzji007,

Depending on where the the fw is located and if the fw that you are using is the wechat as provided by dialog, you should compile the code and download it to your device. If the device is using a flash memory or an EEPROM memory in order to load the fw you can erase and reburn the device via the Smart Snippets tool, either via JTAG or via UART (depending on the interface your device has available). In case the wechat is burned in OTP you wont be able to update the OTP since you can only program it once. You can also test the new source code via downloading the new fw directly to the sysram via keil and the JTAG interface (again if this interface is available on your device, you can also debug the code in that case) also you can download code into the sysram via UART through the Smart Snippets tool.

Thanks MT_dialog

Dear MT_dialog,

Today I ask my colleague to measure clock output signals. You can find attached 3 jpg.
If disable sleep, we can measure both 32KHz and 16MHz clock: 32K_withoutsleep.jpg and 16M_withoutsleep.jpg
If enable sleep, only can see 32KHz signal:32K_withsleep.jpg

I am using SDK5.0.4, the ble_app_sleepmode from SDK example folder. According to example code, the wakeup duration is 0.5s, so it should be very quick. But my test result looks that the 14580 failed to wakup and I can't scan the 14580 device from my smartphone

Can you help to give hints for more trouble shooting?

BTW, should I config CLK_16M_REG as XTAL16_BIAS_SH_ENABLE register before/after sleep?

Thanks & Best regards

Hi smdzji007,

The ble_app_sleepmode falls to permanent sleep after a specific period of time (a few seconds) and the XTAL16 is disabled when sleep is enabled, you can try using a another project that doesn't sleep constantly but wakes up in predefined periods in order to advertise and check again. You dont have to configure the CLK_16M_REG explictly, the SDK will take care of that in the periph_init() function.

Also the specific project implements a button press that when pressed the device wakes up and continiues to advertise, have to tryied to press that button in order to wake up the device.

Also please dont post questions in irrelevant topics, you can always create a new thread if theres any follow up question.

Thanks MT_dialog

Hi MT_dialog,

Thanks to confirm ble_app_sleepmode behavior is correct in my board, so what should I do to enable automatic wake up after 14580 enter extended or deep sleep? To add one XTL32 timer call back function or what else? Which sample project should I use for reference?

The reason for me to post question here is because I found my problem is relevant with current thread topic, and I can't find where is the button to create new thread. If my posting cause any in-convenience to you, I need say apology to you.

Thanks & Best regards,

Hi smdzjl007,

You could try functionapp_easy_timerif the sleep time you specify is not too long(like under 5min)

BR,

Thanks for feedback, Qinjiny from Dialog team,

As previous support engineer said, the XTAL16 clock is disabled when sleeping is enabled, whether app_easy_timer can work normally? Should I write one call back function to enable XTAL32 clock by registering call back function like below?

static const struct arch_main_loop_callbacks user_app_main_loop_callbacks = {
.app_before_sleep = my_app_enable_XTAL32_clock,
.app_resume_from_sleep = my_app_disable_XTAL32_clock,
};

Hi MT_Dialog,

I re-study the ble_app_sleepmode example and found below definition within da1458x_config_advance.h

/****************************************************************************************************************/
/* Wakeup from external processor running host application. */
/****************************************************************************************************************/
#undef CFG_EXTERNAL_WAKEUP

/****************************************************************************************************************/
/* Wakeup external processor when a message is sent to GTL */
/****************************************************************************************************************/
#undef CFG_WAKEUP_EXT_PROCESSOR

Not sure whether it is aligned with your previous answer that the ble_app_sleepmode fall into permanent sleep until external button press trigger wake up. So, how this example code to undefine the external wake up but using external wake up?

Confusing for me

Best regards,
smdzjl

Hi MT_Dialog,

Now I use Da14580 pro kit, and I set the app_default_sleep_mode to ARCH_SLEEP_OFF. It can work well when I burned hex file to SPI falsh, press reset button and pull the daughter board away from mother board.(It's powered by external battery.) It can be scanned from my cellphone. But when I set app_default_sleep_mode to ARCH_EXT_SLEEP_ON, it cannot be scanned from my phone. Does any else code I have to set? Which oscilator does the chip use when it enter the sleep mode? Thanks.