- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello everyone,
I'm starting now with Cypress modules and right now having a hard time with debugging.
I'm trying to debug cybt-213043-mesh kit directly with the usb port.
I saw that this kit has a "double usb", one for programming and another for debug. I'm trying to debug over the peripheral port but not's happening, when i open it nothing is shown to me.
I also programed the kit with the usb debug enabled:
And when i try to program the board with the option "BLE_HelloClient Build + Program + Debug" a error is shown:
If i try to "debug attach" another error happens:
I have to install something to run the debug? What's the problem?
Thanks,
Solved! Go to Solution.
- Labels:
-
ispn:40214:1:0
-
l1:314:1:0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You should use 'WICED HCI UART' for programming and 'WICED Peripheral UART' for getting device side traces for debugging.
Demo applications are more complex applications and complete demonstration. So you should select application which is appropriate for the platform. For me, if I select CYBT-213043-MESH kit while importing the project, I could see only 4 mesh demo applications. HelloClient application not listed on CYBT-213043-MESH kit, but it is there in CYBT-213043-EVAL kit.
If you have a CYBT-213043-EVAL kit, you can download HelloClient application and it should also give you debug prints through the peripheral UART. You can use putty, teraterm, etc for reading the serial (UART) data.
For all mesh applications, you can use the below three debug traces which provide insights while debugging any Mesh-related issues. These flags enable traces in pre-built Mesh libraries provided by Cypress. However, enabling these debug traces increases the application size and will limit the flash memory size available for user application code.
MESH_MODELS_DEBUG_TRACES: This box, when checked, turns ON debug traces from the Mesh Models Library.
MESH_CORE_DEBUG_TRACES: This box, when checked, turns ON debug traces from the Mesh Core Library.
MESH_PROVISIONER_DEBUG_TRACES: This box, when checked, turns ON debug traces from the Mesh Provisioner Library.
Please go through https://www.cypress.com/file/473921/download for learning mesh.
To do hardware debugging (Debug option which you have mentioned) you need a separate piece of HW. Current hardware debug support for CYW207xx and CYW208xx devices requires either a Segger J-Link probe or OpenOCD supported probe.Could you please go through https://www.cypress.com/file/462726/download to know about hardware debugging. All the Hardware and software requirements and procedures for hardware debugging is documented here.
Thanks,
-Dheeraj