For the nRF54 series, how to write logs into ZMS just by changing prj.conf

Question

I am porting a ncs project from nrf52832 into nrf54l15 
 If want to reuse existing Log functions of system of zephyr, like supported by NVS, is there any way to do it? 
 Nordic AI said nrf54l15 should use ZMS to protect flash, and need to manually implement zms_log_store() function to replace all places of zephyr LOG_INF() .Is it the latest truth? 
 
 Thanks & Best Regards 
 -Shawn

AHaug · Accepted Answer

Hi Shawn, 
 I'm sorry for potentially causing an existential crisis heh 
 listplot3d_dev said: 1.<zephyr/logging/log.h> api is a mainstream logging module in NCS 
 Yes, it is 
 listplot3d_dev said: 2.nrf54l15 is a mainstream chip from Nordic 
 Yes it is 
 listplot3d_dev said: 3.nrf54l15 need to use ZMS, if developer want to use zephyr logging API 
 It doesn't need to do this, but it is strongly recommended due to it using RRAM and not Flash 
 listplot3d_dev said: if above three statements are true, then how do developers write logging? I can only think of 2 options: 
 Logging is done regularly with zephyr logging API, but the issue we're discussing in this case is how to "use the logging to file system together with ZMS". This does not have any built in backend per now. Logging over UART/serial is not an issue since this does not use logging to a ZMS file system. 
 Does this make sense to you? I'm more than happy to dive deeper into this. I don't want to have caused any misunderstandings here 
 Kind regards, Andreas

listplot3d_dev · Answer

Thanks Andreas, here is my latest conclusion:) 
 
 for logging API with nRF54L15, there are 3 scenarios: 
 1. output to UART/serial. 
 no problem at all. everybody is happy about that. 
 2.output to local file, with existing prj.conf options 
 mainstream market is happy about that, while Noridc strongly recommends another option 
 3.output to ZMS file 
 which is recommended by Nordic. But currently, only project with scenarios picky enough or with developers geeky enough, would choose this option. 
 
 Please correct me if anything wrong 
 
 Thanks & Best Regards 
 -Shawn

AHaug · Answer

Hi again Shawn 
 listplot3d_dev said: 2.output to local file, with existing prj.conf options 
 mainstream market is happy about that, while Noridc strongly recommends another option 
 I'll just reiterate the previous comment I made about this with one an addition: ZMS is developed and intended to be used to store data in RRAM and not as a logging backend to a file system. If you wish, you can use the FS logging backend instead, but that will introduce extra wear and tear on the RRAM due to this solution isn't using any ZMS implementation. The issue is with the implementation that has the appropriate algorithm to handle reading and writing to RRAM (which the nRF54L15 SoC uses). 
 listplot3d_dev said: 3.output to ZMS file 
 which is recommended by Nordic. But currently, only project with scenarios picky enough or with developers geeky enough, would choose this option. 
 I've never said "we recommend you to a ZMS file". What we've said is that ZMS is better to use with RRAM, but there is no built in logging to file-system backend. 
 Kind regards, Andreas

For the nRF54 series, how to write logs into ZMS just by changing prj.conf

Top Replies