[embassy-nrf] status of nRF54?

[finalyards]

Noticed that while the README does not mention the nRF54 target, there is embassy-nrf/src/chips/nrf54l15_app.rs, anyhow.

Would someone want to clarify the current state - and perhaps 3..6 months ahead - regarding usability of Embassy on said target? Aiming to buy the development kit.

Thanks!!

[i509VCB]

The readme was probably not updated. You may want to look at https://docs.embassy.dev/embassy-nrf/git/nrf54l15-app-ns/index.html to see what is available at the moment.

[finalyards]

Sure. What I'd like to see is a brief mention e.g. right after this section:

The embassy-nrf HAL supports most variants of the nRF family:

nRF51 ([examples](https://github.com/embassy-rs/embassy/tree/main/examples/nrf51))
nRF52 ([examples](https://github.com/embassy-rs/embassy/tree/main/examples/nrf52840))
nRF53 ([examples](https://github.com/embassy-rs/embassy/tree/main/examples/nrf5340))
nRF91 ([examples](https://github.com/embassy-rs/embassy/tree/main/examples/nrf9160))

This is where I went to see what's available. If there was a paragraph/ sentence below that saying: "nRF54 will eventually be supported by this repo; current status is ..."

..that would do it. Also, having a summary issue about the nRF54 state would be nice. ☀️

[finalyards]

My nRF54 DK arrived and I'll play with it, this week.

In the mean time, nrf-hal added this note to their landing page. That might bring more people to this README, which doesn't currently have any mention about nRF54. I retain that adding a one-liner would be nice, to at least remove the confusion of one repo pointing here, and then feeling like a dead end.

Eventually, I hope, it's going to be possible to develop Embassy applications for nRF54.

[i509VCB]

I retain that adding a one-liner would be nice, to at least remove the confusion of one repo pointing here, and then feeling like a dead end.

I would agree with you there about that. Feel free to open a pull request to change that. Although I wonder if that should note that the support for nrf54 is relatively new.

[finalyards]

I retain that adding a one-liner would be nice, to at least remove the confusion of one repo pointing here, and then feeling like a dead end.

I would agree with you there about that. Feel free to open a pull request to change that. Although I wonder if that should note that the support for nrf54 is relatively new.

So there is support? I crafted a one-liner but it's a little hard for me since I don't know how much... there is support. If one of you who knows can do 1-on-1 chat we me, for example, I'd be better off writing the README change. In the mean time, here would be my initial line:

Ideally, imho, the repo should have a table of maturity for the different supported platforms.

[i509VCB]

While I can see the justification for a table, it's something that someone needs to maintain and update. For nRF where the number of chips is manageable I can see it working. However other HALs can't necessarily scale to that (good luck STM32 and MSPM0 lol). If this was something we wanted, it would probably need to be generated for the bigger HALs.

Although do note I'm not really the maintainer for nRF, I just happen to read into random issues from time to time.

Also you may be interested in #4763

[lulf]

I retain that adding a one-liner would be nice, to at least remove the confusion of one repo pointing here, and then feeling like a dead end.

I would agree with you there about that. Feel free to open a pull request to change that. Although I wonder if that should note that the support for nrf54 is relatively new.

So there is support? I crafted a one-liner but it's a little hard for me since I don't know how much... there is support. If one of you who knows can do 1-on-1 chat we me, for example, I'd be better off writing the README change. In the mean time, here would be my initial line:

Ideally, imho, the repo should have a table of maturity for the different supported platforms.

nrf54 support is ongoing, I can update the table once it's done. Until then, let's not keep it there to avoid false promises.

[finalyards]

nrf54 support is ongoing, I can update the table once it's done.

Great.

There is no table at the moment. I asked Copilot to make one - by reading the code in embassy-nrf - and it made a pretty good job! I can make a PR that stays in draft, and has such a table.