Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connections to TI CC254x break after conn_update #7939

Closed
jonpry opened this issue May 25, 2018 · 3 comments
Closed

Connections to TI CC254x break after conn_update #7939

jonpry opened this issue May 25, 2018 · 3 comments
Assignees
Labels

Comments

@jonpry
Copy link

jonpry commented May 25, 2018

Nordic softdevices have a flag BLE_GAP_OPT_COMPAT_MODE, for ensuring the connection window offset does not become zero because of bugs in TI CC254x stacks. Is there a way to prevent such windows from being used in zephyr?

@nashif nashif added bug The issue is a bug, or the PR is fixing a bug question and removed bug The issue is a bug, or the PR is fixing a bug labels May 29, 2018
@carlescufi carlescufi assigned cvinayak and unassigned carlescufi May 31, 2018
@carlescufi
Copy link
Member

I've assigned this to @cvinayak so he can provide an answer here.

@jonpry
Copy link
Author

jonpry commented May 31, 2018

I put the following in isr_rx_scan()

	if (_radio.scanner.win_offset_us == 0) {
	   _radio.scanner.win_offset_us = 2;
	}		
            {
		conn_space_us = _radio.scanner.win_offset_us;
		while ((conn_space_us & ((u32_t)1 << 31)) ||
		       (conn_space_us < conn_offset_us)) {
			conn_space_us += conn_interval_us;
		}
		pdu_adv_tx->connect_ind.win_offset =
			(conn_space_us - conn_offset_us) / 1250;
		pdu_adv_tx->connect_ind.win_size++;
	}

Now connections to TI devices work, but i doubt this is safe to do. I also considered calling the ticker api and reserving the first time slot for some non existent user function, but wasn't able to figure out the ticker api or the correct constants to make that work.

@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants