• State Not Answered
  • Replies 3 replies
  • Subscribers 64 subscribers
  • Views 874 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 275399
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Several questions about memfault

Jim

1.At this link https://www.nordicsemi.com/News/2021/06/Memfault-platform-on-the-nRF-Connect-SDK，Nordic customers can register 100 devices for free. How to calculate these 100 devices, is it calculated by the company or by the individual？

2.nRF Connect SDK v1.6.0 has built-in support for the Memfault Firmware SDK on nRF9160-based targets. How to connect nRF53 nRF52 (based on NCS) devices to the memfault platform？

3.Is there a demo project for embedding memfault sdk into nRF5 sdk？

Parents
  • 0

    1. From my understanding the 100 devices is per memfault account. They detect unique devices on the cloud side and max out at 100. I believe each company can have 1 account, but that is something you can talk to memfault about if you have multiple projects.

    2. Currently there is no support for nRF52/nRF53, and I don't have any timeline for when that may be in place. It should be possible to port to nRF52/53, but the way to egress events and what to use as a gateway is not decided on our side to implement samples with it. So the event egress will have to be your own implementation, at least for now.

    3. No.

Reply
  • 0

    1. From my understanding the 100 devices is per memfault account. They detect unique devices on the cloud side and max out at 100. I believe each company can have 1 account, but that is something you can talk to memfault about if you have multiple projects.

    2. Currently there is no support for nRF52/nRF53, and I don't have any timeline for when that may be in place. It should be possible to port to nRF52/53, but the way to egress events and what to use as a gateway is not decided on our side to implement samples with it. So the event egress will have to be your own implementation, at least for now.

    3. No.

Children
No Data
Related

core_v2_widget.Hide()