Manually start the nRF5 802154 radio

Is there a way to manually initialize the nRF5 802154 radio?. I am using an external NOR flash LittleFS partition for data and the nRF5 802154 radio driver keeps complaining about the mount point not being found. For boot speed reasons, I manually mount the FS later. Even if I used automount, the 802154 driver still gets initialized before the filesystem so this is still a problem. Ideally I would like to be able to mount LittleFS and then enable the radio from my application (post boot).

Parents
  • Hello,

    Are you using the nRF5 SDK or the nRF Connect SDK?

    the nRF5 802154 radio driver keeps complaining about the mount point not being found

    Is it the littleFS that complains about the mount point not being found? Have you tried to debug into why? What function call is it that returns an error, and what is the value of that return?

    Best regards,

    Edvin

  • Edvin,

    It is also possible that I misunderstood the error logs and the mount point error is coming from somewhere else, perhaps another module that requires the settings filesystem. For that, I do not know how to debug an NCS project to step through the Zephyr boot in order to root cause the source of this error. Any help would be appreciated.

Reply Children
  • Tristen said:
    Here is the Zephyr log at boot:

    So you are using Openthread. That answers one of the questions.

    The lines "fs: mount point not found!!" are printed from fs.c in zephyr\subsys\fs\fs.c

    There are 7 functions that can print this, as far as I can see. It is fs_open(), fs_opendir(), fs_mkdir(), fs_unlink(), fs_rename(), fs_stat(), and fs_statvfs().

    Tristen said:
    My project has preparatory code so I'll share the kconfig and board files instead.

    Perhaps you can modify one of the samples from the SDK to use your Kconfig and board files to reproduce the issue, then send it to me, then?

    I am not saying that I do not believe you, but it will be quicker this way. Did you test this in a sample that is not using the openthread stack, and perhaps not the radio at all? Does the issue not occur there?

    BR,

    Edvin

Related