Repository navigation
Start device drivers under RTOS and enable RTC - #131
Merged
Merged
Conversation
JaxCalder
changed the title
This was referenced Oct 16, 2026
Merged
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.
Device creation ran before dmosi_init started the scheduler, so a driver waiting for hardware through a semaphore could not initialize during boot. Queue a kernel boot task, start the scheduler, then mount filesystems/create devices, process startup modules and launch the main application in that task. The worker stack is reclaimed when it returns; the kernel owns its retained handle until scheduler shutdown.
Enable dmrtc with the board LSE preset, generic rtc console tool and test_dmrtc. The driver uses RCC IRQ plus an ISR-safe semaphore for oscillator readiness, with sleeping short waits for flags that have no IRQ. There is no busy-wait fallback.
Validation on STM32F746G-DISCO: flashed with Verified OK; latest RTC suite 11/11, dmdrvi diagnostic 6/6 and RNG regression 6/6. /dev devices and DHCP remain available. Starting with LSE disabled (BDCR=0x8100) confirmed a real RCC IRQ wake in the ST-Link log ring. Calendar rollover, year 2000 and powered reset retention are covered by the driver's validation report. The latest generic ioctl/CLI test transcript is linked in choco-technologies/dmrtc#1.
Integration requires releases of choco-technologies/dmdrvi#29 (RTC header), choco-technologies/dmdevfs#72 (r+b access mapping), then choco-technologies/dmrtc#1 and registration choco-technologies/dmod-registry#16. Local unpublished packages were used for hardware validation; no local paths or dependency version pins are committed. The extra test_dmdrvi diagnostic was staged only in the local validation image.