app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

Karl Ylvisaker — Thu, 15 Jul 2021 13:35:40 GMT

[quote user="luqman"]I think the issue is resolved, now the RTC2 is running and the device is not reset.[/quote]

Great, I am glad to hear that! :)

[quote user="luqman"]Thanks a lot, Karl[/quote]

No problem at all, I am happy to help!

Please do not hesitate to open another ticket if you should encounter any issues or question in the future.

Good luck with your development!

Best regards,
Karl

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

luqman — Thu, 15 Jul 2021 13:27:28 GMT

Thanks a lot, Karl I think the issue is resolved, now the RTC2 is running and the device is not reset.

Here is the main now.

int main(void)
{
    ret_code_t err_code;
    bool erase_bonds;

    // Initialize.
    log_init();
    timers_init();
    power_management_init();
    ble_stack_init();
    gap_params_init();
    gatt_init();
    advertising_init();
    services_init();
    conn_params_init();
    peer_manager_init();

    // Start execution.
    NRF_LOG_INFO("Template example started.");
    application_timers_start();
    advertising_start(erase_bonds);

    APP_ERROR_CHECK(err_code);
    gpio_init();  ///init interrupt on button 1
          ////oled init ////
   uint8_t address;
   uint8_t sample_data;
   bool detected_device = false;

ssd1306_init_i2c(SSD1306_CONFIG_SCL_PIN, SSD1306_CONFIG_SDA_PIN);
ssd1306_begin(SSD1306_SWITCHCAPVCC, SSD1306_I2C_ADDRESS, false);


   NRF_LOG_INFO("TWI scanner started.");

          ///clcok//

  uint32_t p_is_running = 0;
  sd_clock_hfclk_request();
 while(! p_is_running) 
 {  							//wait for the hfclk to be available
	sd_clock_hfclk_is_running((&p_is_running));
 }
 NRF_LOG_INFO("clock started.");

 nrf_cal_init();
 nrf_cal_set_callback(calendar_updated, 4);
//////////////////

ssd1306_clear_display();
ssd1306_set_textsize(2);
ssd1306_set_textcolor(WHITE);
ssd1306_set_cursor(8, 20);


ssd1306_putstring( "Ble_watch");
ssd1306_display();
nrf_delay_ms(2000);
ssd1306_clear_display();
while (true)
{ 
//do something
}

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

luqman — Thu, 15 Jul 2021 13:12:49 GMT

I'm using S132 Segger embedded studio with nrf52832 dev kit

The operation you are trying to do should be done through the sd_clock_hfclk_request call, to request that the hfclk is kept running.

I try to do using sd_clock_hfclk_request but if you have an example related to a specific task let me know

it's helped me a lot

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

Karl Ylvisaker — Thu, 15 Jul 2021 11:20:47 GMT

Hello,

[quote user="luqman"]I try to reply to the below question but I don't get a reply option on there,[/quote]

I have heard about this issue before, and reported it to the site administrators for examination. In the meantime, it seems that the workaround for this is to click on the timestamp of the comment you would like to reply to, to have the buttons show up again. Sorry for the inconvenience.

[quote user="luqman"]As I use to monitor time by using Internal RTC. For this purpose, I use NRF_calender_example so I just use that code in order to clockwork properly if I don't use enable clock the RTc didn't start count. If I remove those lines from the code the working of the clock stuck. Is there any way I use both nrf_calender_example and ble_template examples in the same code?[/quote]

Thank you for elaborating.
As written in the Restricted definition, the restricted peripherals are available to the application, but they must be accessed through the SoftDevice API, so that the SoftDevice remains in control of what the peripherals are doing.

Since I do not know exactly which SoftDevice and version you are working with I can not link you to the exact documentation, so the following links are for the S140 v7.2.0.:
The operation you are trying to do should be done through the sd_clock_hfclk_request call, to request that the hfclk is kept running.
Just remember that this will keep the HFCLK running until you manually release it.

Best regards,
Karl

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

luqman — Thu, 15 Jul 2021 09:20:45 GMT

It automatically came below X:D

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

luqman — Thu, 15 Jul 2021 09:14:41 GMT

Hi Karl.

I try to reply to the below question but I don't get a reply option on there,

so read the doc "The CLOCK peripheral is classified as restricted when the SoftDevice is enabled."

why I use the 'clock start'

As I use to monitor time by using Internal RTC. For this purpose, I use NRF_calender_example so I just use that code in order to clockwork properly if I don't use enable clock the RTc didn't start count. If I remove those lines from the code the working of the clock stuck. Is there any way I use both nrf_calender_example and ble_template examples in the same code?

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

Karl Ylvisaker — Wed, 14 Jul 2021 16:21:45 GMT

Hello again,

[quote user="luqman"]Thanks for the tips I make it clear next time.[/quote]

No problem at all, I am happy to hear that you found the tips helpful! :)
Thank you for clearing up the code.

[quote user="luqman"]

i try to clear the code now look,

the code is stuck on that line below

[/quote]

Could I ask why you have included the 'clock start' section?
The SoftDevice restricts access to the CLOCK peripheral when it is enabled, which is likely the cause of these fatal errors. As mentioned in the SoftDevice's hardware peripheral requirements, restricted peripherals should only be accessed by the application through the SoftDevice API when the SoftDevice is enabled.

The relevant exempt reads:

Table 1. Hardware access type definitions
Access type	Definition
Restricted	The hardware peripheral is used by the SoftDevice and is outside the application sandbox. When the SoftDevice is enabled, it shall only be accessed through the SoftDevice API. Through this Application Programming Interface (API), the application has limited access.

The CLOCK peripheral is classified as restricted when the SoftDevice is enabled.

If you tell me more about the functionality you are looking to implement with these lines, or why you have added them in the first place, I could maybe come up with an alternative approach, that will be OK with the SoftDevice.

Best regards,
Karl

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

luqman — Wed, 14 Jul 2021 14:17:43 GMT

int main(void)
{
    ret_code_t err_code;

    bool erase_bonds;
    log_init();
    timers_init();
    power_management_init();
    ble_stack_init();
    gap_params_init();
    gatt_init();
    advertising_init();
    services_init();
    conn_params_init();
    peer_manager_init();

    // Start execution.
   NRF_LOG_INFO("Template example started.");
   application_timers_start();
   advertising_start(erase_bonds);

   APP_ERROR_CHECK(err_code);
   gpio_init(); 

                   //oled init //
  uint8_t address;
  uint8_t sample_data;
  bool detected_device = false;


ssd1306_init_i2c(SSD1306_CONFIG_SCL_PIN, SSD1306_CONFIG_SDA_PIN);
ssd1306_begin(SSD1306_SWITCHCAPVCC, SSD1306_I2C_ADDRESS, false);


NRF_LOG_INFO("TWI scanner started.");

             ///internal clcok//

  NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
  NRF_CLOCK->TASKS_HFCLKSTART = 1;
  while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);
  
  NRF_LOG_INFO("clock started.");

nrf_cal_init();
nrf_cal_set_callback(calendar_updated, 4);

            //// oled output data///////

  ssd1306_clear_display();
  ssd1306_set_textsize(2);
  ssd1306_set_textcolor(WHITE);
  ssd1306_set_cursor(8, 20);


  ssd1306_putstring( "Ble_watch");
  ssd1306_display();
  nrf_delay_ms(2000);
  ssd1306_clear_display();
while (true)
{ 
//do something
}

i try to clear the code now look,

the code is stuck on that line below

NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;

when I going to click on the definition of a function, it's pushed me to the definition of so I don't understand how to go exact error

when ic click on NRF_CLOCK its move to

#define NRF_CLOCK                   ((NRF_CLOCK_Type*)         NRF_CLOCK_BASE)

when ic click on EVENTS_HFCLKSTARTED its move to

__IOM uint32_t  EVENTS_HFCLKSTARTED;          /*!< (@ 0x00000100) HFCLK oscillator started

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

luqman — Wed, 14 Jul 2021 12:58:16 GMT

Thanks for the tips I make it clear next time.

I try breakpoints and find the exact line where the error and come back.

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

Karl Ylvisaker — Wed, 14 Jul 2021 12:51:01 GMT

Please try to put some breakpoints in your code, to see where the fatal error occurs.
I see now that you are triggering the HFCLKSTART task after having enabled the SoftDevice, this may be causing the error.

Use the breakpoints to see how far you are getting in your code, to pinpoint exactly which line is causing this. Do you for example ever enter into the nrf_cal_init function?

For the record, your code includes a lot of commented out code, clutter, and improper formatting (such as the uneven indentations and missing closing curly braces) which makes your code a lot harder to read, and spot errors in. Please consider cleaning up the code, both for your own future sake (increasing readability and maintainability), and for anyone else who will be reading it. This makes it a lot easier to debug.

Looking forward to resolving this issue together!

Best regards,
Karl

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

luqman — Wed, 14 Jul 2021 12:20:35 GMT

No, it's still the same as I change the RTC- ----> RTC2

I use nrf_calender_example and here I change the clock

#define CAL_RTC                 NRF_RTC2
#define CAL_RTC_IRQn            RTC2_IRQn
#define CAL_RTC_IRQHandler      RTC2_IRQHandler
#define CAL_RTC_IRQ_Priority    3

here the main();

 bool erase_bonds;

    // Initialize.
    log_init();
    timers_init();
    //buttons_leds_init(&erase_bonds);
    power_management_init();
    ble_stack_init();
    gap_params_init();
    gatt_init();
    advertising_init();
    services_init();
    conn_params_init();
    peer_manager_init();

    // Start execution.
    NRF_LOG_INFO("Template example started.");
    application_timers_start();

    advertising_start(erase_bonds);

     //Enter main loop.
    //for (;;)
    //{
    //    idle_state_handle();
    //}


ret_code_t err_code;

//log_init();
APP_ERROR_CHECK(err_code);

//clocks_start();

gpio_init();  ///init interrupt on button 1
//NRF_LOG_INFO("TWI scanner started.");

///////////oled init ////
uint8_t address;
uint8_t sample_data;
bool detected_device = false;

////APP_ERROR_CHECK(NRF_LOG_INIT(NULL));
////NRF_LOG_DEFAULT_BACKENDS_INIT();

ssd1306_init_i2c(SSD1306_CONFIG_SCL_PIN, SSD1306_CONFIG_SDA_PIN);
ssd1306_begin(SSD1306_SWITCHCAPVCC, SSD1306_I2C_ADDRESS, false);


NRF_LOG_INFO("TWI scanner started.");

//////////////////////////

//////clcok//



NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
NRF_CLOCK->TASKS_HFCLKSTART = 1;
while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);
NRF_LOG_INFO("clock started.");

nrf_cal_init();
nrf_cal_set_callback(calendar_updated, 4);
//////////////////

ssd1306_clear_display();
ssd1306_set_textsize(2);
ssd1306_set_textcolor(WHITE);
ssd1306_set_cursor(8, 20);


ssd1306_putstring( "Ble_watch");

ssd1306_display();

nrf_delay_ms(2000);

ssd1306_clear_display();



while (true)

{ 
}

this is output response

<info> app_timer: RTC: initialized.
<info> app: Template example started.
<info> app: Fast advertising.
<info> app: TWI scanner started.
<error> app: Fatal error

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

Karl Ylvisaker — Wed, 14 Jul 2021 11:40:34 GMT

[quote user="luqman"]thanks for the answer Karl.[/quote]

No problem at all, I am happy to help!

[quote user="luqman"]when the code redirects to the advertising mode function this makes reset the microcontroller I don't understand.[/quote]

If the microcontroller resets that usually means that a non-NRF_SUCCESS error code has been passed to an APP_ERROR_CHECK, like mentioned in my previous reply.
Rebooting the device is the default error handling, when no specific error handling has been implemented.

[quote user="luqman"]I use RTC0 for clock count is there any possibility that the ble advertising conflict with the RTC or maybe some thing else [/quote]

Yes, RTC0 is blocked by the SoftDevice. You will have to use another RTC instance.
Try this, and let me know if it resolves your issue.

Best regards,
Karl

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

luqman — Wed, 14 Jul 2021 11:25:21 GMT

thanks for the answer Karl.

I added that the the debug window shows this

<info> app_timer: RTC: initialized.
<info> app: Template example started.
<info> app: Fast advertising.
<error> app: Fatal error

when the code redirects to the advertising mode function this makes reset the microcontroller I don't understand.

I use RTC0 for clock count is there any possibility that the ble advertising conflict with the RTC or maybe some thing else

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

Karl Ylvisaker — Tue, 13 Jul 2021 14:09:51 GMT

[quote user="luqman"]Thanks for the answer I just added the path and enable App_time and now it's working[/quote]

I am happy to hear that it resolved the issue, great!

[quote user="luqman"]When I debug the program nrf52832 kit reset when it reached the clock code. [/quote]

That sounds like a non-NRF_SUCCESS error code being passed to an APP_ERROR_CHECK. Please make sure to have DEBUG defined in your preprocessor defines, like shown in the included image.

This will make the logger output a detailed error message whenever a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK. Check the error code in this error message against the API Reference of the function that returned it, to see why it generated the error.

Best regards,
Karl

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

luqman — Tue, 13 Jul 2021 13:57:42 GMT

Thanks for the answer I just added the path and enable App_time and now it's working but I have another issue now :(

Combine ble_app_template example with clock code which is nearly run separately. After combining

Code is compiled properly .. but the clock is not working,

When I debug the program nrf52832 kit reset when it reached the clock code.

 bool erase_bonds;

    // Initialize.
    log_init();
    timers_init();
    //buttons_leds_init(&erase_bonds);
    power_management_init();
    ble_stack_init();
    gap_params_init();
    gatt_init();
    advertising_init();
    services_init();
    conn_params_init();
    peer_manager_init();

    // Start execution.
    NRF_LOG_INFO("Template example started.");
    application_timers_start();

    advertising_start(erase_bonds);

     //Enter main loop.
    //for (;;)
    //{
    //    idle_state_handle();
    //}


ret_code_t err_code;

//////log_init();
APP_ERROR_CHECK(err_code);
//clocks_start();
gpio_init();  ///init interrupt on button 1


///////////oled init ////
uint8_t address;
uint8_t sample_data;
bool detected_device = false;

////APP_ERROR_CHECK(NRF_LOG_INIT(NULL));
////NRF_LOG_DEFAULT_BACKENDS_INIT();

ssd1306_init_i2c(SSD1306_CONFIG_SCL_PIN, SSD1306_CONFIG_SDA_PIN);
ssd1306_begin(SSD1306_SWITCHCAPVCC, SSD1306_I2C_ADDRESS, false);


NRF_LOG_INFO("TWI scanner started.");

//////////////////////////

//////clcok//



NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
NRF_CLOCK->TASKS_HFCLKSTART = 1;
while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);


nrf_cal_init();
nrf_cal_set_callback(calendar_updated, 4);
//////////////////

ssd1306_clear_display();
ssd1306_set_textsize(2);
ssd1306_set_textcolor(WHITE);
ssd1306_set_cursor(8, 20);


ssd1306_putstring( "Ble_watch");

ssd1306_display();

nrf_delay_ms(2000);

ssd1306_clear_display();

RE: app_timer_t' has no member named 'handler' (I got this error after merge the I2c OLED project with ble_template example)

Karl Ylvisaker — Tue, 13 Jul 2021 10:58:19 GMT

Hello,

Could you confirm for me that you have also added the drv_rtc.c file to your project as well, and that you have defined APP_TIMER_V2 in your project preprocessor defines, like detailed in the Migration note?

Best regards,
Karl