Start scaning right after starting advertising.

RE: Start scaning right after starting advertising.

Susheel Nuguru — Thu, 22 Oct 2015 07:54:15 GMT

First of all, vrey sorry for coming back to you so late. This thread somehow lost its visibility : ( instead of watchpoints, i guess it useful to insert conditional breakpoints. There is an interesting discussion here and look for the comments from DaveR

Instead of watching the value whe it equals a specific value; you should set a conditional break point on the line where you want to check the value of var1. This should effectively have the same effect

e.g. (gdb) break main.c:123 if (var1 == 0)

RE: Start scaning right after starting advertising.

Al Bundy — Thu, 15 Oct 2015 12:51:16 GMT

I use Linux so my debugging tool is arm-none-eabi-gdb. I have tried watch uart_count if uart_count > 100 to stop my program to see when this value gets so high. Unfortunately gdb stops every time uart_count is changed but because of active soft device I got into hard fault after long breaks. I know that cortex M0 supports hardware watchpoints but do you know if supporting conditional hardware watchpoints is something else ?

RE: Start scaning right after starting advertising.

Susheel Nuguru — Fri, 09 Oct 2015 21:06:55 GMT

no need to apologize ... it good that you managed to narrow down the source of the problem. softdevice RAM address space and application RAM address space is different. If you believe it is a RAM corruption then i am almost sure that it is not the softdevice. Softdevice is compiled with fixed RAM space and if there is a stack corruption, it should be in the lower side of rhe RAM address space and not into the application RAM address space. Softdevice does not use heap memory.

I think the application has sent the address of an uninitialized pointer or similar. If you are using KEIL, you can set a breakpoint on uart_counter with a condition to see what has set the variable to such a high value.

RE: Start scaning right after starting advertising.

Al Bundy — Fri, 09 Oct 2015 13:31:53 GMT

I have made some investigation today and first of all I have to apologize to you. Application crashes also when I start only one of scanning or advertising but it is much more in these cases, it only has 100% correct execution when neither advertising nor scanning is started. In my application I have static variable (uart_counter) which is changed whenever I want to send something using uart. There are only two functions that modifies this value. When program went buggy I stopped it with gdb and it occurred that uart_counter was equal to some huge value thats why almost whole RAM is sent. I init uart and start sending before calling ble_advertising_start and ble_scan_start. Is it possible that softdevice may change value of static variable or automatic variable of function that was interrupted by softdevice ?

RE: Start scaning right after starting advertising.

Susheel Nuguru — Wed, 07 Oct 2015 13:25:03 GMT

you said that the uart sends the whole ram when buggy, I would very much like to know the source of this problem. Please update this thread when you find out. If you need more help, posting some code snippets will speed up our analysis.

RE: Start scaning right after starting advertising.

Al Bundy — Wed, 07 Oct 2015 11:19:56 GMT

Sorry for responding so late. Ok, here is what happens. In my application I use app_uart_fifo.c and I sniff my UART communication that's how I know something is wrong. When application starts correctly I sent just one sentence but sometimes when it gets into that buggy style nordic sends the same sentence but then it sends whole RAM content and gets into Hard Fault. Debugging is rather impossible when softdevice is working and the problems does not appear when I just start one of scanning or advertising. When I stop program in buggy execution Program Counter is in Soft Device or app_uart_fifo.c or some scheduler functions and that's why I still consider it as bug in my code. So far I have added watchdog so that my application restarts when it enters buggy path.

RE: Start scaning right after starting advertising.

Susheel Nuguru — Wed, 30 Sep 2015 10:51:46 GMT

This should have worked fine, I would like to know the what errors you get. Is it possible that the problem is somewhere else? because if there is a problem with this, it should not have worked sometimes. Try to debug and tell us little more clearly what you mean by "sometimes it looks like processor is executing total mess and I have to restart it"

RE: Start scaning right after starting advertising.

Al Bundy — Mon, 28 Sep 2015 21:25:05 GMT

/**< Determines scan interval in units of 0.625 millisecond. */                  
#define SCAN_INTERVAL 0x00A0    /** < 0.1 s */  

                                 
/**< Determines scan window in units of 0.625 millisecond. */                    
#define SCAN_WINDOW 0x0050      /** < 0.05 s */                                  
                                                                             
static ble_gap_adv_params_t bc_adv_params;                                       
                                                                                 
static const ble_gap_scan_params_t scan_params = { 0,// Active scanning not set  
                                                 0,// Selective scanning not set. 
                                                NULL, // White-list not set.     
                                 (uint16_t)SCAN_INTERVAL, // Scan interval.       
                                (uint16_t)SCAN_WINDOW,   // Scan window.         
                         0 /* Never stop scanning unless explicitly asked to */};

#define APP_ADV_FAST_INTERVAL            0x0028 // 25 ms                         
#define APP_ADV_SLOW_INTERVAL            0x0C80 // 2 sec                         
#define APP_ADV_FAST_TIMEOUT             0 // sec                                
#define APP_ADV_SLOW_TIMEOUT             0

I use fast advertising. Sorry Aryan I have not answered in comment but it was easier and more clear.

RE: Start scaning right after starting advertising.

Susheel Nuguru — Fri, 25 Sep 2015 08:13:42 GMT

This should work OK, ofcourse the main factors are the ADV interval and SCAN intervals/Window size. Can you give more details about these settings. if the interval is slow then these two events will compete less with each other for RADIO and CPU resources.