Catch advertising timeout in main

RE: Catch advertising timeout in main

Vidar Berg — Mon, 02 Nov 2020 11:04:11 GMT

Hi,

Thanks for the update, glad to hear the programming part working again. For other questions I'd prefer you post it in a new thread as we have already moved away from the original topic.

RE: Catch advertising timeout in main

Olfox — Mon, 02 Nov 2020 09:38:29 GMT

Hi Vidar,

It's ok i can work again. i had to check an option and remove the ldo on vdd pin into my jlink programmer.

Now i'm using my Power Profile Kit to supply and analyse my power consumption.

I had some trouble at the begining with the fact that i was enter into sleep mode (32uA) , timer wake up and execute the callback ( communication with the sensors , setitng some io...) , but after this callback execution, impossible to enter into sleep mode and program doesn't return to main. I don't know what uC was executing, but consumption was 7mA but i can't reach breakpoint into the main loop.

After debugging, I found that issue comes from the fact that one IO was set to 1 , and avoid to enter system in low power... Strange because wake up is only allowed when pin30 rise from to 1 ...

I also wanted to send 16bit buffer into my characteristic , but i had to manage by spliting into two byte because it was crashig when i tried to upload my uint16 table directly.

I have also reach the limit of the number of data into the service (256?) in three characeteristics.

Now my systeme has all the feature i will work on imporving power consumption, but i create a new topics i think :) .

RE: Catch advertising timeout in main

Olfox — Fri, 30 Oct 2020 17:29:53 GMT

Ok after replacing a mux that was ded on my custom production board, i can flash with nrfConnect programmer the four files with succes and the program run fine. I still have issue in debug mode with SES.

I can connect to jlink, but i click on run degug, i get an error :

RE: Catch advertising timeout in main

Olfox — Fri, 30 Oct 2020 16:34:21 GMT

I'm using a jlink programmer like this :

it is connected to my nrf52833 via a custom production board. But recently i mak etwo times a short to gnd by accident because of a gnd debug wire that touch some voltage on the board so i wonder about something broken. This short has shutdown my laptop because of impact on USB i guess...

I already ordered a new segeer programmer . For the moment i will come back on the developpement board i think ... 😞

But i'm surprised because i was able to debug two or three times this morning but then, impossible.

The led of the jlink programme blink one time each second , with green color. Its seems to indicate according to documentation

GREEN, switched off for 10ms once per second J-Link heart beat. Will be activated after the emulator has been in idle mode for at least 7 seconds.

RE: Catch advertising timeout in main

Vidar Berg — Fri, 30 Oct 2020 12:35:54 GMT

[quote user="Olfox"]does the systeme goes automatically to sleep ? [/quote]

You still have to call idle_state_handle() again after when the program execution returns back to your main loop.

[quote user="Olfox"]. I can connect with jlink commander[/quote]

Jlink commander is too failing to connect to the target based on the log you posted. Can you describe the programming setup you use (connections, voltage, etc)?

RE: Catch advertising timeout in main

Olfox — Fri, 30 Oct 2020 11:46:08 GMT

Yes tha's exactly what i did and it works fine. After handler function is finished, does the systeme goes automatically to sleep ? I also have a proble with my jlink connexion now , i don't know why, I have tried several boards always the same issue. I can connect with jlink commander but impossible with nordic tool like nrf Connect or SES. What is strange is taht i didn't get error in the past.

C:\Users\flo>nrfjprog --version
nrfjprog version: 10.8.0
JLinkARM.dll version: 6.82c

J-Link>connect
Please specify device / core. <Default>: CORTEX-M4
Type '?' for selection dialog
Device>?
Please specify target interface:
  J) JTAG (Default)
  S) SWD
  T) cJTAG
TIF>S
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "NRF52833_XXAA" selected.


Connecting to target via SWD
InitTarget() start
InitTarget() end
Found SW-DP with ID 0x2BA01477
SWD speed too high. Reduced from 4000 kHz to 853 kHz for stability
Failed to power up DAP
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
InitTarget() start
InitTarget() end
Cannot connect to target.
J-Link>

RE: Catch advertising timeout in main

Vidar Berg — Fri, 30 Oct 2020 08:44:18 GMT

No worries. For wakeup I would suggest you set up a repeated app timer instance like most of our BLE examples do.

RE: Catch advertising timeout in main

Olfox — Thu, 29 Oct 2020 14:32:02 GMT

... Sorry Vidar ... you are right it was the problem ... I was so focused on it that i didn't see this obvious mistake !

Now next let's go to the next feature to implement: wake up the system each two days with a timer to measure a sensor , log into ram ( that is always on because of my power management mode), and go back to sleep. So i should be able to wake my system on gpio OR eache two days with a timer.

RE: Catch advertising timeout in main

Vidar Berg — Mon, 19 Oct 2020 06:15:54 GMT

It looks like you are missing the two hyphens ('--') in front of "app-boot-validation"

RE: Catch advertising timeout in main

Olfox — Fri, 16 Oct 2020 13:33:31 GMT

Ha could be great but it generate en error.

I tried to move the argument in each place but same result. I also tried to remove application version argument etc but i always have this error:

fw_no_signed>nrfutil settings generate app-boot-validation NO_VALIDATION --family NRF52 --application ble_app_buttonless_dfu_pca10100_s113.hex --application-version 6 --bootloader-version 1 --bl-settings-version 2 settings.hex


Usage: nrfutil settings generate [OPTIONS] HEX_FILE
Try 'nrfutil settings generate --help' for help.


Error: Got unexpected extra arguments (NO_VALIDATION settings.hex)

RE: Catch advertising timeout in main

Vidar Berg — Fri, 16 Oct 2020 13:17:29 GMT

Excellent! Regarding the CRC check, if you are on SDK 15.3.0 or later, you can disable it by specifying --app-boot-validation NO_VALIDATION when you generate the settings page.

nrfutil settings generate help menu:

RE: Catch advertising timeout in main

Olfox — Fri, 16 Oct 2020 08:56:31 GMT

Ok, it is working fine !

Is it possible to disable check of CRC in secure bootloader during debug ? Else, i always have to build a new setting page with new hex built.

RE: Catch advertising timeout in main

Olfox — Fri, 16 Oct 2020 07:34:49 GMT

Hi Vidar,

Yes I see now I have implemented it, i try to run my software but i'm stuck with some configuration issue, i guess with settings page. I'm using softdevice s113, secure_bootloader_s113 to perform dfu that worked in the past ( ota worked, but i couldn't flash by jlink cable anymore lol ).

I try to solve this and i come back to you to tell you if spinlock is working :) . Again, thanks Vidar for your support !

RE: Catch advertising timeout in main

Vidar Berg — Fri, 09 Oct 2020 08:25:14 GMT

The event register is internal and not exposed to the CPU. To clear it you must call __WFE/sd_app_evt_wait(). This is the reason why sd_app_evt_wait() has to be called twice after servicing an application interrupt.

[quote user="Olfox"]imagine for any reason even after calling two times this function product doesn t enter into low power mode ... [/quote]

This is why I suggested that you placed the "wait for event" call in a spinlock loop earlier. You want to be sure the correct interrupt/event was triggered before you transition to the next state.

RE: Catch advertising timeout in main

Olfox — Thu, 08 Oct 2020 09:34:57 GMT

Hi Vidar,

Thanks for the link.

I have found the problem. As my software is based on sdk example, bsp function managing leds and button were called with timer. When i connected scope on debug sleep pin ,i have seen the uC going into sleep for around 0.3sec. Then I thought to someting linked to timer and i have found the leds stuff. So i have set LEDS_NUMBER to 0 and now i'm not waken by this anymore and product is sleeping as i want.

I should clean all the function linked to bsp button and leds to be sure it will not happen anymore.

I'm still not sure whitch register to look at to mastered the enable source of wake up, and i still don't know why i have to call two times idle_state_handle function. I'm really afraid to put a mass production product without be sure of this. imagine for any reason even after calling two times this function product doesn t enter into low power mode ...

RE: Catch advertising timeout in main

Vidar Berg — Wed, 07 Oct 2020 13:50:11 GMT

__WFE will execute as a __NOP instruction after servicing an interrupt because the Event register will be set. Please take a look at the ARM documentation here for a more detailed explanation as to how this works: https://developer.arm.com/documentation/ka001269/1-0/?search=5eec6e71e24a5e02d07b259a

RE: Catch advertising timeout in main

Olfox — Wed, 07 Oct 2020 13:42:55 GMT

The problem is that i can enter without issue in System ON idle( what i call low power) the first time. But then , after advertsing timeout , i can't. If you go deeper in the idle function you can see that __WFE is called into nrf_pwr_mgmt_run so that's not the issue i think.

I think the source of the probleme is that somthing is blocking the possibility to enter into System ON idle mode. But what or how can i know which interupt service is not served to clear the flag i don't know where to look in whitch register for example

RE: Catch advertising timeout in main

Vidar Berg — Wed, 07 Oct 2020 12:03:21 GMT

So the problem is that you have to call the "idle" function to enter System ON idle? I think the safest method may be to add a spinlock loop in this case. Something like this maybe:

static volatile bool m_acc_wakeup_triggered;

void acc_wakeup_callback()
{
    m_acc_wakeup_triggered = true;
    ...


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

  //  etat = START;

    for (;;)
    {
        switch (etat){

            ...

            case LOW_POWER:

                    NRF_LOG_INFO("State Machine : LOW POWER");


                    accel_goto_mode_power(MODE_LOW_POWER);    // attention si echec recommencer 
                  

                    while(!m_acc_wakeup_triggered)
                    {
                        __WFE();
                    }
                    
                    m_acc_wakeup_triggered = false;
               
                    //ZZZZZZZZZZ... Program sleep here, will continu after this comment on wake up

                     bma400_goto_mode_power(MODE_SLEEP);    

                    etat = EVENT_WAKE_UP_MOVE;

                    break;

                /**/case EVENT_WAKE_UP_MOVE:
                
                        NRF_LOG_INFO("State Machine : WAKE UP on move!");
                        etat = ADVERTISING;

                        break;

            case ADVERTISING:
                NRF_LOG_INFO("State Machine : ADVERTISING...");

                // Start execution.
                advertising_start(erase_bonds);


                etat = WAIT_USER_CONNECT_OR_TIMEOUT;
                NRF_LOG_INFO("State Machine : Wait USER CONNECT or TIMEOUT...");
                    break;

        /**/case WAIT_USER_CONNECT_OR_TIMEOUT:
          

                
                    break;

                      /**/case EVENT_USER_BLE_CONNECT:
                              NRF_LOG_INFO("State Machine : CONNECTED");
                             
                          
                              etat = INIT_SENSORS;
                              break;

                      /**/case EVENT_ADVERTISING_TIMEOUT:
                              NRF_LOG_INFO("State Machine : ADVERTISING TIMEOUT");
                          
                              etat = LOW_POWER; //nobody is connected go back to sleep
                              break;

            case INIT_SENSORS:

                   
               
                    start_timer();
  
                    
                    etat = RUN;
                    break;

            case RUN:
                    //Sensors are measured in their timer interrupt
                    break;

            case EVENT_USER_BLE_DISCONNECT:

                  
                    NRF_LOG_INFO("State Machine : DISCONNECT");

                    etat = LOW_POWER;
                    break;

        }//end switch machine d'etat
   }//end for infinite
}

RE: Catch advertising timeout in main

Olfox — Tue, 06 Oct 2020 09:37:38 GMT

I call it in the main already, in my state machine, so i guess timeout advertising as raised an interrupt flag that as not been cleared as you said. How to know which flag has been set ? I think i have the same the issue at the first low power entering, because i need to call two times idle_state_handle();

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

  //  etat = START;

    for (;;)
    {
        switch (etat){

            case START:

                 log_init();

                NRF_LOG_INFO("State Machine : START!");

                // Initialize the async SVCI interface to bootloader before any interrupts are enabled.
                err_code = ble_dfu_buttonless_async_svci_init();
                APP_ERROR_CHECK(err_code);

                timers_init();

                power_management_init();
                buttons_leds_init(&erase_bonds);
                ble_stack_init();
                peer_manager_init();
                gap_params_init();
                gatt_init();

                services_init();

                advertising_init(); //fle advertising init should be called after services init else error
                conn_params_init();


                // ACCEL INIT

                acceel_init_spi();
                accel_goto_mode_power(MODE_LOW_POWER);           

                err_code = nrf_drv_gpiote_init();
                APP_ERROR_CHECK(err_code);

                nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(true);
                in_config.pull = NRF_GPIO_PIN_NOPULL;

                err_code = nrf_drv_gpiote_in_init(30, &in_config, in_pin_handler);
                APP_ERROR_CHECK(err_code);
                nrf_drv_gpiote_in_event_enable(30, true);

                    etat = LOW_POWER;
                    break;

            case LOW_POWER:

                    NRF_LOG_INFO("State Machine : LOW POWER");


                    accel_goto_mode_power(MODE_LOW_POWER);    // attention si echec recommencer 
                  

                    idle_state_handle();
                    idle_state_handle();    //why two times ? but it works...
               
                    //ZZZZZZZZZZ... Program sleep here, will continu after this comment on wake up

                     bma400_goto_mode_power(MODE_SLEEP);    

                    etat = EVENT_WAKE_UP_MOVE;

                    break;

                /**/case EVENT_WAKE_UP_MOVE:
                
                        NRF_LOG_INFO("State Machine : WAKE UP on move!");
                        etat = ADVERTISING;

                        break;

            case ADVERTISING:
                NRF_LOG_INFO("State Machine : ADVERTISING...");

                // Start execution.
                advertising_start(erase_bonds);


                etat = WAIT_USER_CONNECT_OR_TIMEOUT;
                NRF_LOG_INFO("State Machine : Wait USER CONNECT or TIMEOUT...");
                    break;

        /**/case WAIT_USER_CONNECT_OR_TIMEOUT:
          

                
                    break;

                      /**/case EVENT_USER_BLE_CONNECT:
                              NRF_LOG_INFO("State Machine : CONNECTED");
                             
                          
                              etat = INIT_SENSORS;
                              break;

                      /**/case EVENT_ADVERTISING_TIMEOUT:
                              NRF_LOG_INFO("State Machine : ADVERTISING TIMEOUT");
                          
                              etat = LOW_POWER; //nobody is connected go back to sleep
                              break;

            case INIT_SENSORS:

                   
               
                    start_timer();
  
                    
                    etat = RUN;
                    break;

            case RUN:
                    //Sensors are measured in their timer interrupt
                    break;

            case EVENT_USER_BLE_DISCONNECT:

                  
                    NRF_LOG_INFO("State Machine : DISCONNECT");

                    etat = LOW_POWER;
                    break;

        }//end switch machine d'etat
   }//end for infinite
}

RE: Catch advertising timeout in main

Vidar Berg — Tue, 06 Oct 2020 09:07:38 GMT

Hi,

Could you call idle_state_handle() from your main loop instead? If not you should consider placing it inside a spinlock loop that doesn't exit until the GPIOTE interrupt is triggered.

idle_state_handle() may return immediately if you call it after servicing an interrupt because the internal event register is not cleared.

RE: Catch advertising timeout in main

Olfox — Tue, 06 Oct 2020 08:57:23 GMT

Hi Vidar,

I'm in system On to keep ram retention and clock because i should wake up every day. My system start, do all peripherals init, go in low power with idle_state_handle(); called two time because first time it jump over i don't know why.

Then I wake up with GPIOTE ( accelerometer connected to one input pin). It toggle from low to high. Once wake up, nrf52833 start advertising. If nobody connect, it raise timeout event, and i call idle_state_handle() to enter in low power, but it doesn't work this time. It jump over the the function without going into low power mode.

How to know why it is impossible to enter into sleep mode ?

Thanks for the tips to use port event

RE: Catch advertising timeout in main

Vidar Berg — Tue, 06 Oct 2020 08:46:48 GMT

Hi,

What kind of sleep are you trying to enter, System OFF or System ON. If it's system ON I would just recommend calling idle_state_handle() from the main loop like we do in our SDK examples.

Also noticed that you were using GPIOTE IN events. This increases the idle current in SYSTEM ON. You may consider using GPIOTE port events instead:

nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(true); // <-- Set to false to use low power PORT events. GPIOTE IN vs PORT event: Sleep

RE: Catch advertising timeout in main

Olfox — Mon, 05 Oct 2020 16:16:35 GMT

After wake up , i did the test to come back again in low power and i can still wakeup with my accelerometre, so what is sure, is that advertising timeout event change the condition to go into low power again.

RE: Catch advertising timeout in main

Olfox — Mon, 05 Oct 2020 15:47:23 GMT

I'm using a gpio to enter low power mode:

I tried to call again thi init sequence but it doesn't allow to enter a second time in low power:

                nrf_drv_gpiote_in_config_t in_config = GPIOTE_CONFIG_IN_SENSE_LOTOHI(true);
                in_config.pull = NRF_GPIO_PIN_NOPULL;

                err_code = nrf_drv_gpiote_in_init(30, &in_config, in_pin_handler);
                APP_ERROR_CHECK(err_code);
                nrf_drv_gpiote_in_event_enable(30, true);

RE: Catch advertising timeout in main

Olfox — Mon, 05 Oct 2020 13:21:26 GMT

Great that's works i can reach the event in main.c now. I had also this feeling before to read your answer that program was stopped lol.

Now i have a second issue: after advertising timeout, i set ma state machine to enter low power with the call 2time to function idle_state_handle();:

 case LOW_POWER:

                    NRF_LOG_INFO("State Machine : LOW POWER");
            
                    bma400_goto_mode_power(MODE_LOW_POWER);    // attention si echec recommencer 

                    idle_state_handle();
                    idle_state_handle();    //why two times ? but it works...

From a power on sequence this go into low power mode works. But after timeout advertising, it jump over the two function wihtout going into low power mode.

Is there a link with the fact that we were in timeout advertising event previously may be ?

Thank you Vidar !