3 Replies Latest reply on Nov 25, 2014 11:33 AM by mkim

    20732 stop scanning at all after 'bleprofile_connDown stop Idle Timer'

      Hi,

       

        I'm using 20732 as central role in creating connection to peripherals which is also 20732.

        But one critical issue I found is that after connection down event occurs, the 20732 as the central role is not able to scan anymore.

        I've checked post Re: unexpected "bleprofile_connDown stop Idle Timer", and also adding the retry (creating connection again), but still got the same issue.

       

        Some clue as I found in my trial:

        1. retry upon the disconnection cause (0x3e) is working. but failed in cause (0x08)

      Retry is made as below:

      blecm_CreateConnectionCancel ();

      blecm_CreateConnection (

              blecen_cen_cfg.high_scan_interval,

              blecen_cen_cfg.high_scan_window,

              blecen_cen_cfg.init_filter_policy,

              HCIULP_PUBLIC_ADDRESS,

              (char *) addr,

              HCIULP_PUBLIC_ADDRESS,

              blecen_cen_cfg.high_conn_min_interval,

              blecen_cen_cfg.high_conn_max_interval,

              blecen_cen_cfg.high_conn_latency,

              blecen_cen_cfg.high_supervision_timeout,

              blecen_cen_cfg.conn_min_event_len,

              blecen_cen_cfg.conn_max_event_len);

        2. when issue happen (no more scanning working), I can't enable the scanning again by doing disable scan and enable it again:

       

      a. blecm_setScanEnable (0, blecen_cen_cfg.filter_duplicates)

      b. blecm_startScan (

          blecen_cen_cfg.scan_type,

          blecen_cen_cfg.high_scan_interval,

          blecen_cen_cfg.high_scan_window,

          blecen_cen_cfg.scan_adr_type,

          blecen_cen_cfg.scan_filter_policy,

          blecen_cen_cfg.filter_duplicates);

       

      Any solution or workaround for this case? At least I need central to be able to scan and make connection to peripheral again.