Skip to content

Conversation

@chrysn
Copy link
Contributor

@chrysn chrysn commented Nov 11, 2025

This is a do-over of #15 after moving towards a testable application with nrf-modem.

Unlike the original approach it switches (rather than adding) the library; consequently, this needs to be feature-gated to keep the library usable. (The original idea with #15 was to just always link both, let the user decide what they reference and the linker what to gc, but actually the different libmodem.a have different texts for identical symbols).

How much this is additive (as features should be) I can not tell because I don't see into the proprietary libraries, but I guess that using DECT will break the other cases. But we're in low-level embedded crates, and feature additivity is generally not valued so much when there's already a hard decision for which chip is to be selected.

The issue remains that for this to be practically releasable, a firmware would need to be available.


An extra commit switches on short enums. It remains to be tested whether the radio libmodem is built this way as well.

This is backed by observing structs such as nrf_modem_dect_phy_event:
With packed enums, the fields in its nrf_modem_dect_phy_init_event make
perfect sense (plausible voltage and temperatures, and no error); with
long enums, it's all garbage data.
@chrysn
Copy link
Contributor Author

chrysn commented Nov 11, 2025

diondokter/nrf-modem#52 now has an example program for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant