Fix rx_when_idle never being propagated to radio config #3
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.
radio_conf.rx_when_idleis initialized tofalseand never updated. The ESP radio hardware is never told to keep its receiver on during idle, causing missed 802.15.4 fragments and reassembly-timeout errors.Two issues compound here:
otPlatRadioSetRxOnWhenIdlewas not implementedotPlatRadioSetRxOnWhenIdle(symbol is unreferenced in all shipped.afiles), so implementing it alone is insufficientChanges
platform.rs: AddotPlatRadioSetRxOnWhenIdleextern callback — covers from-source builds where OT calls thislib.rs: QueryotThreadGetLinkMode().mRxOnWhenIdle()inplat_changedand sync toradio_conf— covers precompiled MTD libraries that fire state change callbacks but never callotPlatRadioSetRxOnWhenIdleupdate_rx_when_idlehelper to deduplicate the two update pathsFlow after fix
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.