{"id":36624024,"url":"https://github.com/memfault/mtb-example-memfault","last_synced_at":"2026-01-12T09:29:49.922Z","repository":{"id":51964196,"uuid":"499259063","full_name":"memfault/mtb-example-memfault","owner":"memfault","description":null,"archived":false,"fork":false,"pushed_at":"2024-12-19T19:28:50.000Z","size":479,"stargazers_count":0,"open_issues_count":0,"forks_count":1,"subscribers_count":13,"default_branch":"main","last_synced_at":"2024-12-19T20:18:12.935Z","etag":null,"topics":["memfault","sample"],"latest_commit_sha":null,"homepage":"","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/memfault.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2022-06-02T19:09:52.000Z","updated_at":"2024-12-19T19:02:24.000Z","dependencies_parsed_at":"2024-12-19T20:18:06.238Z","dependency_job_id":"dead203c-fe46-49ac-a1ff-fce772e3e991","html_url":"https://github.com/memfault/mtb-example-memfault","commit_stats":null,"previous_names":[],"tags_count":10,"template":false,"template_full_name":null,"purl":"pkg:github/memfault/mtb-example-memfault","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/memfault%2Fmtb-example-memfault","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/memfault%2Fmtb-example-memfault/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/memfault%2Fmtb-example-memfault/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/memfault%2Fmtb-example-memfault/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/memfault","download_url":"https://codeload.github.com/memfault/mtb-example-memfault/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/memfault%2Fmtb-example-memfault/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28337723,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-12T06:09:07.588Z","status":"ssl_error","status_checked_at":"2026-01-12T06:05:18.301Z","response_time":98,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["memfault","sample"],"created_at":"2026-01-12T09:29:49.862Z","updated_at":"2026-01-12T09:29:49.915Z","avatar_url":"https://github.com/memfault.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Memfault Network Example\n\nExample application for ModusToolbox, loosely based on the\n[mtb-example-anycloud-secure-tcp-client ](https://github.com/Infineon/mtb-example-anycloud-secure-tcp-client)\napplication.\n\nThis code example demonstrates the integration of Memfault with PSoC™ 6 MCU\nwith AIROC™ CYW43xxx Wi-Fi \u0026 Bluetooth® combo chips.\n\nFor step by steps on how to integrate the\n[memfault-firmware-sdk](https://github.com/memfault/memfault-firmware-sdk/commits)\ninto your own project, see the following guide:\nhttps://mflt.io/mtb-integration-guide\n\nThis example application was tested with the following setup:\n\n- [PSoC™ 62S2 Wi-Fi Bluetooth® pioneer kit](https://www.cypress.com/CY8CKIT-062S2-43012)\n- (`CY8CKIT-062S2-43012`) using GNU Arm® embedded compiler v10.3.1 (`GCC_ARM`)\n\n## Requirements\n\n- [ModusToolbox™ software](https://www.infineon.com/cms/en/design-support/tools/sdk/modustoolbox-software/)\n  v3.0 or later (tested with v3.0)\n- PSoC™ 6 Board support package (BSP) minimum required version: 4.0.0\n- Programming language: C\n- Associated parts: All\n  [PSoC™ 6 MCU](https://www.infineon.com/cms/en/product/microcontroller/32-bit-psoc-arm-cortex-microcontroller/psoc-6-32-bit-arm-cortex-m4-mcu)\n\n## Hardware setup\n\nThis example uses the board's default configuration. See the kit user guide to\nensure that the board is configured correctly.\n\n**Note:** The PSoC™ 6 Bluetooth® LE pioneer kit (CY8CKIT-062-BLE) and the\nPSoC™ 6 Wi-Fi Bluetooth® pioneer kit (CY8CKIT-062-WIFI-BT) ship with KitProg2\ninstalled. The ModusToolbox™ software requires KitProg3. Before using this code\nexample, make sure that the board is upgraded to KitProg3. The tool and\ninstructions are available in the\n[Firmware Loader](https://github.com/Infineon/Firmware-loader) GitHub\nrepository. If you do not upgrade, you will see an error like \"unable to find\nCMSIS-DAP device\" or \"KitProg firmware is out of date\".\n\n## Software setup\n\nInstall a terminal emulator if you don't have one such as\n[minterm](https://github.com/pyserial/pyserial/blob/master/serial/tools/miniterm.py)\nor [Tera Term](https://ttssh2.osdn.jp/index.html.en).\n\nInstall a Python interpreter if you don't have one. This code example is tested\nusing [Python 3.7.7](https://www.python.org/downloads/release/python-377/).\n\nInstall the Python package `mflt_build_id` in your Python system packages.\n\n## Using the code example\n\n## Operation\n\n1. Connect the board to your PC using the provided USB cable through the\n   KitProg3 USB connector.\n\n2. The kit is configured to run in Wi-Fi STA interface mode.\n\n   1. Modify the `WIFI_SSID`, `WIFI_PASSWORD` macros to match that of the Wi-Fi\n      network credentials that you want to connect to. These macros are defined\n      in the [source/memfault_example_app.h](source/memfault_example_app.h)\n      file.\n   2. (Optional) If compile-time configuration is not available, the commands\n      `wifi_scan`, `wifi_join`, `wifi_save` are provided to scan for networks,\n      join a found network, and save a network for auto-conneciton at boot.\n\n3. If you already have a Memfault account, navigate\n   [here](https://mflt.io/project-key) to create a project key. (If you do not\n   have an account sign up for a Memfault account [here](https://mflt.io/signup)\n   and create a project). Modify the `MEMFAULT_PROJECT_KEY` macro in\n   [source/memfault_example_app.h](source/memfault_example_app.h) file.\n\n4. Setup up the application using one of the following:\n\n   \u003cdetails\u003e\u003csummary\u003e\u003cb\u003eUsing Eclipse IDE for ModusToolbox™ software\u003c/b\u003e\u003c/summary\u003e\n\n   1. Select New Application from the Quick Panel\n   2. Select your board\n   3. Select Memfault Network Example from the Wi-Fi section\n   4. After the application is created, with the application selected in the\n      projects panel, click Build Application from the Quick Panel\n\n   \u003c/details\u003e\n\n   \u003cdetails\u003e\u003csummary\u003e\u003cb\u003eUsing CLI\u003c/b\u003e\u003c/summary\u003e\n\n   1. Create a workspace directory. This workspace directory will contain both\n      the application and the shared libraries setup by ModusToolbox.\n   2. Clone the application into your workspace directory.\n\n      ```bash\n      # From your workspace directory\n      git clone https://github.com/memfault/mtb-example-memfault.git\n      ```\n\n   3. Navigate into the application root and run:\n\n      ```bash\n      # modify the BSP name as necessary\n      BSP_NAME=\"CY8CKIT-062S2-43012\"\n      \u003cPATH_TO_MODUS_TOOLS\u003e/library-manager/library-manager-cli --project . --add-bsp-name ${BSP_NAME} --add-bsp-version latest-v4.X --add-bsp-location \"local\"\n      \u003cPATH_TO_MODUS_TOOLS\u003e/library-manager/library-manager-cli --project . --set-active-bsp APP_${BSP_NAME}\n      make build\n      ```\n\n   \u003c/details\u003e\n\n5. Open a terminal program and select the KitProg3 COM port. Set the serial port\n   parameters to 8N1 and 115200 baud.\n\n6. Program the board using one of the following:\n\n   \u003cdetails\u003e\u003csummary\u003e\u003cb\u003eUsing Eclipse IDE for ModusToolbox™ software\u003c/b\u003e\u003c/summary\u003e\n\n   1. Select the application project in the Project Explorer.\n\n   2. In the **Quick Panel**, scroll down, and click **\\\u003cApplication Name\u003e\n      Program (KitProg3_MiniProg4)**.\n\n   \u003c/details\u003e\n\n   \u003cdetails\u003e\u003csummary\u003e\u003cb\u003eUsing CLI\u003c/b\u003e\u003c/summary\u003e\n\n   From the terminal, execute the `make program` command to build and program\n   the application using the default toolchain to the default target. The\n   default toolchain and target are specified in the application's Makefile but\n   you can override those values manually:\n\n   ```bash\n   make program TARGET=\u003cBSP\u003e TOOLCHAIN=\u003ctoolchain\u003e\n   ```\n\n   Example:\n\n   ```bash\n   make program TARGET=CY8CPROTO-062-4343W TOOLCHAIN=GCC_ARM\n   ```\n\n   \u003c/details\u003e\n\n7. Upload the symbol file to see decoded data on the Memfault web app (upload\n   the .elf file, either via the web app or using the\n   [Memfault CLI tool](https://docs.memfault.com/docs/mcu/symbol-file-build-ids/#upload-symbol-files-cli))\n\n## Running the Example Application\n\nThe board will automatically attempt to bring up the network interface on boot.\nIf it fails, posting data from the board will not work, but the CLI will still\nbe available for manually uploading chunk data. On success you should see\nsomething like the following:\n\n```plaintext\n[I] Memfault Build ID: 1d63b5daaa91c74ad352d16533417604219beec1\n[I] S/N: DEMOSERIAL\n[I] SW type: app-fw\n[I] SW version: 1.0.0-dev\n[I] HW version: dvt1\n[I] Reset Reason, Cy_SysLib_GetResetReason=0x10\n[I] Reset Cause:\n[I]  Software Reset\n[I] Memfault Initialized!\n\nWLAN MAC Address : C4:AC:59:9C:5C:5C\nWLAN Firmware    : wl0: Apr 12 2022 20:39:36 version 13.10.271.287 (760d561 CY) FWID 01-b438e2a0\nWLAN CLM         : API: 18.2 Data: 9.10.0 Compiler: 1.36.1 ClmImport: 1.34.1 Creation: 2021-04-26 04:01:15\nWHD VERSION      : v2.3.0 : v2.3.0 : GCC 10.3 : 2022-04-13 14:02:24 +0800\n[I] Wi-Fi Connection Manager initialized.\n[I] Successfully connected to Wi-Fi network\n[I] IPv4 address assigned: 192.168.1.19\n\n[I] Secure Socket initialized\n[I] Global trusted RootCA certificate loaded\n[I] Posting Memfault Data...\n[D] Response Complete: Parse Status 0 HTTP Status 202!\n[D] Body: Accepted\n```\n\nTo see debug options, run the `help` command:\n\n```plaintext\nmflt\u003e help\nget_core: Get coredump info\nclear_core: Clear an existing coredump\ncrash: Trigger a crash\ntrigger_logs: Trigger capture of current log buffer contents\ndrain_chunks: Flushes queued Memfault data. To upload data see https://mflt.io/posting-chunks-with-gdb\ntrace: Capture an example trace event\nget_device_info: Get device info\nreboot: Reboot system and tracks it with a trace event\nexport: Export base64-encoded chunks. To upload data see https://mflt.io/chunk-data-export\nhelp: Lists all commands\n```\n\nAn example crash can be forced using the `crash` command:\n\n```plaintext\nmflt\u003e crash 1\n[... device will reboot and post data on reboot ...]\n[I] Memfault Build ID: 5f455f3ce017f5f93666dfbc6fa016b680b72901\n[I] S/N: DEMOSERIAL\n[I] SW type: app-fw\n[I] SW version: 1.0.0-dev\n[I] HW version: dvt1\n[I] Reset Reason, Cy_SysLib_GetResetReason=0x10\n[I] Reset Cause:\n[I]  Software Reset\n[I] Memfault Initialized!\n\nmflt\u003e WLAN MAC Address : C4:AC:59:9C:5C:5C\nWLAN Firmware    : wl0: Apr 12 2022 20:39:36 version 13.10.271.287 (760d561 CY) FWID 01-b438e2a0\nWLAN CLM         : API: 18.2 Data: 9.10.0 Compiler: 1.36.1 ClmImport: 1.34.1 Creation: 2021-04-26 04:01:15\nWHD VERSION      : v2.3.0 : v2.3.0 : GCC 10.3 : 2022-04-13 14:02:24 +0800\n[I] Wi-Fi Connection Manager initialized.\n[I] Successfully connected to Wi-Fi network 'MyCharterWiFif2-2G'\n[I] IPv4 address assigned: 192.168.1.19\n\n[I] Secure Socket initialized\n[I] Global trusted RootCA certificate loaded\n[D] Response Complete: Parse Status 0 HTTP Status 202!\n[D] Body: Accepted\n[D] Response Complete: Parse Status 0 HTTP Status 202!\n[D] Body: Accepted\n```\n\nAnother way to trigger a crash is via the user buttons. User Button 1 will\ntrigger a hard fault, while User Button 2 will trigger an assertion.\n\nA 1-minute timer runs that will attempt to upload any data generated by the\nMemfault library (core dumps, metrics, etc). For more information about how to\nuse the demo CLI, refer to https://mflt.io/demo-cli\n\n## Debugging\n\nYou can debug the example to step through the code. In the IDE, use the\n**\\\u003cApplication Name\u003e Debug (KitProg3_MiniProg4)** configuration in the **Quick\nPanel**. For details, see the \"Program and debug\" section in the\n[Eclipse IDE for ModusToolbox™ software user guide](https://www.cypress.com/MTBEclipseIDEUserGuide).\n\n**Note:** **(Only while debugging)** On the CM4 CPU, some code in `main()` may\nexecute before the debugger halts at the beginning of `main()`. This means that\nsome code executes twice – once before the debugger stops execution, and again\nafter the debugger resets the program counter to the beginning of `main()`. See\n[KBA231071](https://community.cypress.com/docs/DOC-21143) to learn about this\nand for the workaround.\n\n## Design and implementation\n\n### Resources and settings\n\n**Table 1. Application resources**\n\n| Resource   | Alias/object            | Purpose                                                 |\n| :--------- | :---------------------- | :------------------------------------------------------ |\n| SDIO (HAL) | sdio_obj                | SDIO interface for Wi-Fi connectivity                   |\n| UART (HAL) | cy_retarget_io_uart_obj | UART HAL object used by retarget-io for debug UART port |\n| LED (BSP)  | CYBSP_USER_LED          | User LED to show output                                 |\n\n---\n\nThis example uses the Arm® Cortex®-M4 (CM4) CPU of PSoC™ 6 MCU to execute an\nRTOS task (TCP client task). At device reset, the default Cortex®-M0+ (CM0+)\napplication enables the CM4 CPU and configures the CM0+ CPU to go to sleep.\n\nIn this example, the TCP client establishes a secure connection with a TCP\nserver through SSL handshake. During the SSL handshake, the client presents its\nSSL certificate (self-signed) for verification and also verifies the server's\nidentity to which it is connecting. Once the SSL handshake completes\nsuccessfully, the TCP client controls the user LED ON or OFF based on the\ncommand received from the TCP server.\n\n---\n\n## Related resources\n\n| Resources            | Links                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |\n| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Application notes    | [AN228571](https://www.infineon.com/dgdl/Infineon-AN228571_Getting_started_with_PSoC_6_MCU_on_ModusToolbox_software-ApplicationNotes-v06_00-EN.pdf?fileId=8ac78c8c7cdc391c017d0d36de1f66d1\u0026utm_source=cypress\u0026utm_medium=referral\u0026utm_campaign=202110_globe_en_all_integration-an_vanitylink) – Getting started with PSoC™ 6 MCU on ModusToolbox™ software \u003cbr\u003e [AN215656](https://www.infineon.com/dgdl/Infineon-AN215656_PSoC_6_MCU_Dual-CPU_System_Design-ApplicationNotes-v09_00-EN.pdf?fileId=8ac78c8c7cdc391c017d0d3180c4655f\u0026utm_source=cypress\u0026utm_medium=referral\u0026utm_campaign=202110_globe_en_all_integration-an_vanitylink) – PSoC™ 6 MCU: Dual-CPU system design | [Using ModusToolbox™ software](https://github.com/Infineon/Code-Examples-for-ModusToolbox-Software) on GitHub \u003cbr\u003e [Using PSoC™ Creator](https://www.infineon.com/cms/en/design-support/software/code-examples/psoc-3-4-5-code-examples-for-psoc-creator/?utm_source=cypress\u0026utm_medium=referral\u0026utm_campaign=202110_globe_en_all_integration-code_example) |\n| Device documentation | [PSoC™ 6 MCU datasheets](https://www.infineon.com/cms/en/search.html#!view=downloads\u0026term=psoc6\u0026doc_group=Data%20Sheet) \u003cbr\u003e [PSoC™ 6 technical reference manuals](https://www.infineon.com/cms/en/search.html#!view=downloads\u0026term=psoc6\u0026doc_group=Additional%20Technical%20Information)                                                                                                                                                                                                                                                                                                                                                                                     |\n| Development kits     | Select your kits from the [Evaluation board finder](https://www.infineon.com/cms/en/design-support/finder-selection-tools/product-finder/evaluation-board)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |\n| Libraries on GitHub  | [mtb-pdl-cat1](https://github.com/Infineon/mtb-pdl-cat1) – PSoC™ 6 peripheral driver library (PDL) \u003cbr\u003e [mtb-hal-cat1](https://github.com/Infineon/mtb-hal-cat1) – Hardware abstraction layer (HAL) library \u003cbr\u003e [retarget-io](https://github.com/Infineon/retarget-io) – Utility library to retarget STDIO messages to a UART port                                                                                                                                                                                                                                                                                                                                            |\n| Middleware on GitHub | [capsense](https://github.com/Infineon/capsense) – CAPSENSE™ library and documents \u003cbr\u003e [psoc6-middleware](https://github.com/Infineon/modustoolbox-software#psoc-6-middleware-libraries) – Links to all PSoC™ 6 MCU middleware                                                                                                                                                                                                                                                                                                                                                                                                                                               |\n| Tools                | [Eclipse IDE for ModusToolbox™ software](https://www.infineon.com/cms/en/design-support/tools/sdk/modustoolbox-software/) – ModusToolbox™ software is a collection of easy-to-use software and tools enabling rapid development with Infineon MCUs, covering applications from embedded sense and control to wireless and cloud-connected systems using AIROC™ Wi-Fi and Bluetooth® connectivity devices.                                                                                                                                                                                                                                                                    |\n\n---\n\n## Other resources\n\nInfineon provides a wealth of data at www.infineon.com to help you select the\nright device, and quickly and effectively integrate it into your design.\n\nFor PSoC™ 6 MCU devices, see\n[How to design with PSoC™ 6 MCU – KBA223067](https://community.infineon.com/t5/Knowledge-Base-Articles/How-to-Design-with-PSoC-6-MCU-KBA223067/ta-p/248857)\nin the Infineon community.\n\n---\n\n© Cypress Semiconductor Corporation, 2020-2022. This document is the property of\nCypress Semiconductor Corporation, an Infineon Technologies company, and its\naffiliates (\"Cypress\"). This document, including any software or firmware\nincluded or referenced in this document (\"Software\"), is owned by Cypress under\nthe intellectual property laws and treaties of the United States and other\ncountries worldwide. Cypress reserves all rights under such laws and treaties\nand does not, except as specifically stated in this paragraph, grant any license\nunder its patents, copyrights, trademarks, or other intellectual property\nrights. If the Software is not accompanied by a license agreement and you do not\notherwise have a written agreement with Cypress governing the use of the\nSoftware, then Cypress hereby grants you a personal, non-exclusive,\nnontransferable license (without the right to sublicense) (1) under its\ncopyright rights in the Software (a) for Software provided in source code form,\nto modify and reproduce the Software solely for use with Cypress hardware\nproducts, only internally within your organization, and (b) to distribute the\nSoftware in binary code form externally to end users (either directly or\nindirectly through resellers and distributors), solely for use on Cypress\nhardware product units, and (2) under those claims of Cypress’s patents that are\ninfringed by the Software (as provided by Cypress, unmodified) to make, use,\ndistribute, and import the Software solely for use with Cypress hardware\nproducts. Any other use, reproduction, modification, translation, or compilation\nof the Software is prohibited. \u003cbr\u003e TO THE EXTENT PERMITTED BY APPLICABLE LAW,\nCYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS\nDOCUMENT OR ANY SOFTWARE OR ACCOMPANYING HARDWARE, INCLUDING, BUT NOT LIMITED\nTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR\nPURPOSE. No computing device can be absolutely secure. Therefore, despite\nsecurity measures implemented in Cypress hardware or software products, Cypress\nshall have no liability arising out of any security breach, such as unauthorized\naccess to or use of a Cypress product. CYPRESS DOES NOT REPRESENT, WARRANT, OR\nGUARANTEE THAT CYPRESS PRODUCTS, OR SYSTEMS CREATED USING CYPRESS PRODUCTS, WILL\nBE FREE FROM CORRUPTION, ATTACK, VIRUSES, INTERFERENCE, HACKING, DATA LOSS OR\nTHEFT, OR OTHER SECURITY INTRUSION (collectively, \"Security Breach\"). Cypress\ndisclaims any liability relating to any Security Breach, and you shall and\nhereby do release Cypress from any claim, damage, or other liability arising\nfrom any Security Breach. In addition, the products described in these materials\nmay contain design defects or errors known as errata which may cause the product\nto deviate from published specifications. To the extent permitted by applicable\nlaw, Cypress reserves the right to make changes to this document without further\nnotice. Cypress does not assume any liability arising out of the application or\nuse of any product or circuit described in this document. Any information\nprovided in this document, including any sample design information or\nprogramming code, is provided only for reference purposes. It is the\nresponsibility of the user of this document to properly design, program, and\ntest the functionality and safety of any application made of this information\nand any resulting product. \"High-Risk Device\" means any device or system whose\nfailure could cause personal injury, death, or property damage. Examples of\nHigh-Risk Devices are weapons, nuclear installations, surgical implants, and\nother medical devices. \"Critical Component\" means any component of a High-Risk\nDevice whose failure to perform can be reasonably expected to cause, directly or\nindirectly, the failure of the High-Risk Device, or to affect its safety or\neffectiveness. Cypress is not liable, in whole or in part, and you shall and\nhereby do release Cypress from any claim, damage, or other liability arising\nfrom any use of a Cypress product as a Critical Component in a High-Risk Device.\nYou shall indemnify and hold Cypress, including its affiliates, and its\ndirectors, officers, employees, agents, distributors, and assigns harmless from\nand against all claims, costs, damages, and expenses, arising out of any claim,\nincluding claims for product liability, personal injury or death, or property\ndamage arising from any use of a Cypress product as a Critical Component in a\nHigh-Risk Device. Cypress products are not intended or authorized for use as a\nCritical Component in any High-Risk Device except to the limited extent that (i)\nCypress’s published data sheet for the product explicitly states Cypress has\nqualified the product for use in a specific High-Risk Device, or (ii) Cypress\nhas given you advance written authorization to use the product as a Critical\nComponent in the specific High-Risk Device and you have signed a separate\nindemnification agreement. \u003cbr\u003e Cypress, the Cypress logo, and combinations\nthereof, WICED, ModusToolbox, PSoC, CapSense, EZ-USB, F-RAM, and Traveo are\ntrademarks or registered trademarks of Cypress or a subsidiary of Cypress in the\nUnited States or in other countries. For a more complete list of Cypress\ntrademarks, visit cypress.com. Other names and brands may be claimed as property\nof their respective owners.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmemfault%2Fmtb-example-memfault","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmemfault%2Fmtb-example-memfault","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmemfault%2Fmtb-example-memfault/lists"}