samples: le_periph_blinky: prototype cert boot info on le_periph_blinky - #882
Draft
CijaSathish-AlifSemi wants to merge 8 commits into
Draft
samples: le_periph_blinky: prototype cert boot info on le_periph_blinky#882CijaSathish-AlifSemi wants to merge 8 commits into
CijaSathish-AlifSemi wants to merge 8 commits into
Conversation
Add -DPLAIN_BLINKY=1 build flag to skip the pm-ble snippet and lpgpio.overlay. Without it, pm-ble suspends gpio4 between BLE connection events, silently breaking LED GPIO writes. When pm-ble is active, append a DK-specific overlay after lpgpio.overlay to restore led0/led2 aliases to the gpio4 RGB LED nodes (lpgpio.overlay remaps them to LPGPIO which is not wired to any visible LED on DK). Defer led0 writes to a work item so they run in thread context after device resumption, consistent with how led2 is handled. Also add cert boot info print and suppress pm_device log noise for DK. Signed-off-by: Cija Sathishkumar <cija.sathishkumar@alifsemi.com>
Add NCC (CCAM26LP1230T0) and JP (R 201-260499) cert IDs to all three DK board config files. Signed-off-by: Cija Sathishkumar <cija.sathishkumar@alifsemi.com>
Use "NCC ID" and "MIC ID" instead of "NCC" and "JP" to match the labels as they appear on the certification marks. Signed-off-by: Cija Sathishkumar <cija.sathishkumar@alifsemi.com>
CijaSathish-AlifSemi
requested review from
BhupeshKharwa-AlifSemi and
kshitijvyas-Alifsemi
July 30, 2026 23:22
CijaSathish-AlifSemi
changed the title
… GPIO button_update_handler toggled char0_val on every press edge and ignored release, so the notified button state didn't match the physical button and required two presses to cycle back to 0. Mirror the live GPIO level instead so the characteristic reflects pressed/released in real time. Signed-off-by: Cija Sathishkumar <cija.sathishkumar@alifsemi.com>
VeijoPesonen
previously approved these changes
Aug 7, 2026
VeijoPesonen
left a comment
VeijoPesonen
left a comment
Contributor
There was a problem hiding this comment.
Just drop the two unnecessary overlay files and this is ok.
Contributor
There was a problem hiding this comment.
Chips used with the Balletto devkits are not wounded down so this variant does not need to be supported.
Contributor
There was a problem hiding this comment.
Chips used with the Balletto devkits are not wounded down so this variant does not need to be supported.
Add board conf for alif_b1_sk_ab1c1f4m51820ph0_rtss_he with FCC, IC, NCC and MIC cert IDs for the Balletto StartKit. Signed-off-by: Cija Sathishkumar <cija.sathishkumar@alifsemi.com>
Align the Kconfig symbol name with the printed label so both consistently use MIC instead of JP. Signed-off-by: Cija Sathishkumar <cija.sathishkumar@alifsemi.com>
SW2 (PB_SW1) on B1 SK is wired to P15_0, not P15_1. Add pinctrl pull-up and route button0 to lpgpio 0 with GPIO_ACTIVE_LOW. Signed-off-by: Cija Sathishkumar <cija.sathishkumar@alifsemi.com>
With GPIO_ACTIVE_LOW, gpio_pin_get_dt already returns 1 when pressed and 0 when released. The previous !(button_state & 1) inverted this, causing the notification to be 0 on press and 1 on release. Remove the negation so the notification correctly reflects button state. Signed-off-by: Cija Sathishkumar <cija.sathishkumar@alifsemi.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a prototype/draft to show certification ID printing at boot as requested by @kshitijvyas-Alifsemi (Not intended for merge as-is)
Short description:
printk+SYS_INITPLAIN_BLINKY=1build flag to skip thepm-blesnippet (for making the blinky work on le_periph_blinkyled0/led2aliases afterlpgpio.overlayremaps themBuild command (DK, with LED fix)
Known limitations (what's not right here)
Cert info lives in the app, not the board. Ideally this belongs at the board or subsystem level so it shows up regardless of which app is running. Putting it in
le_periph_blinkymeans every other app has to duplicate it.SYS_INITatPRE_KERNEL_2doesn't guarantee clean output ordering. UART output is DMA-backed on this platform; deferred log messages can interleave with the printk box. There's no clean fix without reworking the logging init order.PLAIN_BLINKY=1is a workaround, not a fix. The real issue ispm-bleenablingCONFIG_PM_DEVICE=y, which suspendsgpio4between BLE connection events and causesgpio_pin_set_dtto fail silently. The right fix is proper PM suspend/resume handling forgpio4in the pm-ble snippet or the GPIO driver.Cert values are hardcoded in board conf files. No validation that the IDs are correct/current. If cert IDs ever change these files need manual updates.
Please use this as a reference for printing certification info on boot - for any Zephyr app that is built for B1.