app_easy_timer error

Hi,
Do you try running the "prox_reporter" reference software with the app_easy_timer feature in SDK5 ? Your described observation cannot conclude the issue is due to "app_easy_timer" function. More information is required such as how you run your test, on what software, ....
Regards,

Hi,
Your issue is properly related to where you put your "LedBlink(20,35,1000)" statement. It is because app_easy_timer and malloc() require the kernel timer and heap service. Your function can only be called after the kernel is initialized and activated. It is suggested to put your statement after system_init() and make your LedBlink function blink forever to ease your debugging.

int main_func(void)
{
sleep_mode_t sleep_mode;

//global initialise
system_init();

LedBlink(20,35,1000);

/*
************************************************************************************
* Platform initialization
************************************************************************************
*/
while(1)
{
.....
}
}

Regards,

Hi,

Fixed the mistake as follows:
// get the allowed sleep mode
// time from rwip_power_down() to WFI() must be kept as short as possible!!
sleep_mode = rwip_power_down();
/* statement added */
if ((sleep_mode == mode_ext_sleep) || (sleep_mode == mode_deep_sleep))
{
sleep_mode = mode_idle;
}

Regards,

Hi,
The technique to verify your LedBlink() function and its behavior can be done by simply forcing the sleep_mode not going into mode_ext_sleep or mode_deep_sleep. To integrate the LED blinking function and let it behaves in what you intended, you need to understand how the software is structured.
In real application, there is two (2) threads running independently, BLE stack and User application. Kernel provides only the services and user application requires to manages and supervise all resources usage and monitor all activities to determine the device can go into sleep mode or not.

int main_func(void)
{
sleep_mode_t sleep_mode;

//global initialise
system_init();

/*
************************************************************************************
* Platform initialization
************************************************************************************
*/
while(1)
{
do {
// schedule all pending events
schedule_while_ble_on();
}
while (app_asynch_proc() != GOTO_SLEEP); //grant control to the application, try to go to power down
//if the application returns GOTO_SLEEP
.....
}
}

app_asynch_proc()函数是一个检查的用户application whether any activity is on-going that prevents the device goes into sleep mode while BLE stack thread is ready to go into sleep.

typedef enum {
GOTO_SLEEP = 0,
KEEP_POWERED
} arch_main_loop_callback_ret_t;

In your case, this function can return "KEEP_POWERED" as long as LED is blinking not allowing the device into sleep.

static inline void schedule_while_ble_on(void)
{
// BLE clock is enabled
while (ble_is_powered())
{
// BLE event end is set. conditional RF calibration can run.
uint8_t ble_evt_end_set = ke_event_get(KE_EVENT_BLE_EVT_END);

//execute messages and events
rwip_schedule();

if (ble_evt_end_set)
{
uint32_t sleep_duration = 0;
rcx20_read_freq();

//if you have enough time run a temperature calibration of the radio
if (lld_sleep_check(&sleep_duration, 4)) //6 slots -> 3.750 ms
// check time and temperature to run radio calibrations.
conditionally_run_radio_cals();
}

//grant control to the application, try to go to sleep
//if the application returns GOTO_SLEEP
if (app_asynch_trm() != GOTO_SLEEP)
{
continue; // so that rwip_schedule() is called again
}
else
{
arch_printf_process();
break;
}
}
}

The app_asynch_trm() function handles user application while BLE stack is running. The rwip_schedule() will process all messages in the queue till completion and the control will pass to app_asynch_trm() function and based on the returned value "KEEP_POWERED" or "GOTO_SLEEP" to decide to keep alive or go to sleep accordingly.

Please notice that there is no function to keep track any software timer is running or not. It is the responsibility of the owner of the soft timer is to keep track its activity.

To develop your application in SDK5, it is recommended to study the following structure and understand how it works as it is the key of the SDK5 structure.

struct arch_main_loop_callbacks {
void (*app_on_init)(void);
arch_main_loop_callback_ret_t (*app_on_ble_powered)(void);
arch_main_loop_callback_ret_t (*app_on_system_powered)(void);
void (*app_before_sleep)(void);
sleep_mode_t (*app_validate_sleep)(sleep_mode_t sleep_mode);
void (*app_going_to_sleep)(sleep_mode_t sleep_mode);
void (*app_resume_from_sleep)(void);
};

static const struct arch_main_loop_callbacks user_app_main_loop_callbacks = {
.app_on_init = default_app_on_init,

/ /默认情况下看门狗定时器重载和resumed when the system wakes up.
// The user has to take into account the watchdog timer handling (keep it running,
// freeze it, reload it, resume it, etc), when the app_on_ble_powered() is being
// called and may potentially affect the main loop.
.app_on_ble_powered = NULL,

/ /默认情况下看门狗定时器重载和resumed when the system wakes up.
// The user has to take into account the watchdog timer handling (keep it running,
// freeze it, reload it, resume it, etc), when the app_on_system_powered() is being
// called and may potentially affect the main loop.
.app_on_system_powered = NULL,

.app_before_sleep = NULL,
.app_validate_sleep = NULL,
.app_going_to_sleep = NULL,
.app_resume_from_sleep = NULL,
};

Regards,