-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
samples: bluetooth: absolute pin number in conn_time_sync and iso_time_sync #17639
base: main
Are you sure you want to change the base?
Conversation
244c035
to
2eb9cc5
Compare
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 006014ee92a94b7d2742133c8dac575777c61cd0 more detailssdk-nrf:
Github labels
List of changed files detected by CI (2)
Outputs:ToolchainVersion: 9583beca34 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
Do we have the same issue in the iso_time_sync sample? |
2eb9cc5
to
a8e7283
Compare
Had a quick look and it seems like it. Do you know if it is failing the CI somehow or the sample is not run at all? |
a8e7283
to
9146221
Compare
@@ -30,6 +30,15 @@ static struct gpio_dt_spec led = GPIO_DT_SPEC_GET_OR(DT_ALIAS(led1), gpios, {0}) | |||
|
|||
static uint8_t previous_led_value; | |||
|
|||
struct gpio_nrfx_cfg { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed offline:
we should not mirror this type here. Instead, the required functionality could be added to the zephyr driver.
9146221
to
35a06d7
Compare
…e_sync The two samples failed on 54l15 because they were not using the absolute pin number for LED1. Signed-off-by: Yuxuan Cai <[email protected]>
35a06d7
to
006014e
Compare
The sample could not run on 54l15 because the pin number was not converted to the absolute value.