| 24 Jun 2024 |
 dirbaio | https://github.com/nrfconnect/sdk-nrfxlib/tree/main/nrf_modem/lib | 19:57:28 |
| dirbaio | There's cellular/nrf9120 and dect-phy/nrf9120 | 19:59:52 |
| dirbaio | No idea what the difference is or which one you need | 20:00:09 |
|  @dbrgn:matrix.coredump.ch left the room. | 20:16:16 |
 diondokter | Probably the cellular one if you're using nrf-modem.
But the underlying nrfxlib-sys crate probably has to be updated to use that binary.
I don't have the time to do that, but if fuse117 wants to do it I can guide and review it | 21:16:42 |
| 25 Jun 2024 |
 fuse117 | I am updating both nrfxlib-sys and nrf-modem. I have nrfxlib-sys pointing to cellular/nrf9120/soft-float/libmodem.a in release 2.7.0-rc2. This aligns with a basic modem example in the 2.7.0-rc2 SDK. | 18:09:45 |
| diondokter | Cool! | 18:10:10 |
| fuse117 | thus far, everything is aligned as best i can tell | 18:10:23 |
| fuse117 | the nrfxlib_sys::nrf_mode_init() hangs still | 18:11:04 |
| fuse117 | i can contrive errors out of it, but when providing it valid params, nothing | 18:11:38 |
| diondokter | One thing though is that for an actual release we probably don't want to use a release candidate. So for any update we'd have to wait a little bit | 18:11:56 |
| diondokter | In reply to @fuse117:matrix.org
i can contrive errors out of it, but when providing it valid params, nothing contrive? | 18:12:04 |
| fuse117 | provide null or invalid control shemem size and get the right error codes | 18:12:37 |
| diondokter | Ah | 18:12:46 |
| fuse117 | im using a custom memory layout not much different than the defaults. they align with the SDK project uses. | 18:13:46 |
| diondokter | So, one thing to check is whether the IPC is right for your chip. The IPC peripheral is used to talk between the user and modem core.
If the IPC isn't triggered I can imagine it would hang.
So one way to figure this out is by looking at the current IPC code they use for their code connecting the modem to Zephyr and see if there are any differences | 18:14:55 |
| fuse117 | cool... that is what i was starting to look at. | 18:15:40 |
| fuse117 | okay. seems to be working. i foobar-ed the ipc binding | 19:01:55 |
| dirbaio | it's working? coool | 19:02:33 |
| dirbaio | I wonder what the difference is | 19:02:44 |
| fuse117 | yes, at least what basic functionality i have tested thus far. | 19:19:21 |
| 28 Jun 2024 |
| fuse117 | I am working on an nrf9151, which internally is an nrf9120. I just submitted a PR to the nrf-pacs repo. I have tested it within the nrf-hal and embassy projects, but I am not sure what else is needed. Also, I'm not sure what to put into the top-level README https://github.com/nrf-rs/nrf-pacs/pull/21 | 13:20:06 |
| dirbaio |
I'm not sure what to put into the top-level README
not sure, just do same as the other PACs? copy then change the partnumber
| 13:35:16 |
| dirbaio | btw can an admin change https://github.com/nrf-rs/nrf-pacs to not require approval to run CI? James Munns ? | 13:35:29 |
 James Munns | 
Download Screenshot 2024-06-28 at 15.36.55.png | 13:37:07 |
| James Munns | it's just on first time contribs? | 13:37:10 |
| dirbaio | yeah that | 13:37:15 |
| dirbaio | pick the 1st option | 13:37:32 |
| James Munns | don't we usually want that on, so we don't become coin miner bait? | 13:37:33 |
| dirbaio | github has magic algos where the "who are new to github" thing does magic to prevent that | 13:37:52 |
