SmartTag problem after update from SDK3.x.x to SDK5.x.x

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
5 posts / 0 new
Last post
slava
Offline
Last seen:3年5个月前
加入:2015-04-28 10:35
SmartTag problem after update from SDK3.x.x to SDK5.x.x

Hello.
I have issue with custom board which has the same schematic as in smart tag reference design.
Software which i download about 1,5 years ago properly work with my board. But after I start use updated software (Smart Tag source code based on 5.20.2 SDK) I have issue.
Device start works (led blinking and device advertise) but after some time it goes to sleep (led stop blinking, about some minutes). Then I push the button, device wake up, but i see that led is blinking same as device without firmware (bootloader is in ptrogress). Any actions with button do not change anything. If I disconnect battery and connect it again device start work.
In code I change only one define (LP_CLK_RCX20 instead LP_CLK_XTAL32 because there is no clock XTAL).

Why updated variant is not work? What I need to do to make it work?

Device:
MT_dialog
Offline
Last seen:1 month 2 days ago
Staff
加入:2015-06-08 11:34
Hi slava,

Hi slava,

Are you using deep sleep or extended sleep ? I am not able to understand your explanation about the LED blinking and the bootloader, when you press the button in order for the device to wake up you see the bootloader executing. The device when it goes to permanent sleep it sets the RESET_ON_WAKEUP (check the user_adv_timer_handler), so when the device is instructed to wakeup, it performs a h/w reset, if there is nothing to boot from it will keep on executing the bootloader. If you remove that instruction (the SetBits16(PMU_CTRL_REG, RESET_ON_WAKEUP,1);) you will be able to wakeup properly without the reset, and also if you dont use deepsleep remove the transition to deep sleep mode as well (that requires a burned OTP).

Thanks MT_dialog

slava
Offline
Last seen:3年5个月前
加入:2015-04-28 10:35
I use extended sleep mode.

I use extended sleep mode. Firmware is stored in external SPI flash, so I do not understand why it can`t boot after wake up.

MT_dialog
Offline
Last seen:1 month 2 days ago
Staff
加入:2015-06-08 11:34
Hi slava,

Hi slava,

因为闪光powered down, after each interaction with the flash the fw sends a power down message to the flash in order to save power, so, when you fall asleep the flash is powered down. So when you wake up and you try to boot (without having anything in your OTP) the scanning sequence starts but there is no flash to respond to the scanning sequence. To overcome that you will have to:

Either leave the flash open in order for the device to boot.

Burn secondary bootloader in the OTP in order to boot from OTP, power up the flash and eventually boot from flash.

Burn the Image to the OTP in order to boot the fw directly from there.

Thanks MT_dialog

DonXavier
Offline
Last seen:1 year 3 months ago
加入:2019-07-22 15:56
hey, slava can you please

hey, slava can you please send me the program files for the DA14580, (donxaviervaliyaparambil@gmail.com)