Forums - Debugging Issue

10 posts / 0 new
Last post
Debugging Issue
bcoffman
Join Date: 13 Jul 16
Posts: 1
Posted: Wed, 2016-07-20 12:35

Cannot seem to get debug statements written to Putty Console.
Running CSRMeshTempSensor example project...

#define DEBUG_ENABLE is set up in user_config.h
Debug stmts are in place like DEBUG_STR("Hello");

USB>SPI Programming Board is set to 3v3 UART and 3v3SPI

Windows 10 Laptop sees virtual USB Serial port COM3 which is 9600 8,1,N,N

Connect Putty to serial>COM3 9600 8,1,N,N

No output when in debug>run

I also tried putty at 2400 14400 - no success.

What am I missing? Thanks

Bill

 

 

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Wed, 2016-07-20 14:58

Maybe you have to solder the 2 bridges that CSR left open on PCB (SB1 SB2)

  • Up0
  • Down0
chiruru
Join Date: 24 Dec 16
Posts: 9
Posted: Mon, 2016-12-26 06:09

My situation is same, I can't print Debug on PuTTy.

I have soldered SB1 and SB2 of mesh_board, But Also There are nothing on PuTTY.

I think that mesh_2.1 Source Code has the problem about printing Debug message(using UART) on PuTTy.

Any ideas?

  • Up0
  • Down0
Loris
Join Date: 27 Jul 16
Posts: 35
Posted: Tue, 2016-12-27 23:50

Please see the configuration of UART baudrate. The temp sensor default use 0x0ebf that means baudrate is 921600, that's why you can't see any printf log even if you defined the DEBUG_ENABLE macro

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Wed, 2016-12-28 01:53

You maust buy USB-UART

CSR PCB do not provide that.

See https://goo.gl/hriT8H

 

 

Set the CSR1010 to the right baud_rate  in the *.key file. 

 
 *
 *      - UART_RATE_2K4    = 0x000a
 *      - UART_RATE_9K6    = 0x0028
 *      - UART_RATE_19K2    = 0x004e
 *      - UART_RATE_38K4    = 0x009e
 *      - UART_RATE_57K6    = 0x00eb
 *      - UART_RATE_115K2 = 0x01d9
 *      - UART_RATE_230K4 = 0x03af
 *      - UART_RATE_460K8 = 0x0760
 *      - UART_RATE_921K6 = 0x0ebf
 *      - UART_RATE_1382K4 = 0x161f
 *      - UART_RATE_1843K2 = 0x1d7e
 *      - UART_RATE_2764K8 = 0x2c3d
 *      - UART_RATE_3686K4 = 0x3afc
  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Wed, 2016-12-28 01:55

See https://goo.gl/hriT8H CSR PCBs has no USB UART. YOU need to buy and connect that by yourself,

  • Up0
  • Down0
DS.Hwang
Join Date: 30 Aug 16
Posts: 6
Posted: Wed, 2016-12-28 20:29

Hi, Nissim,

I have same exprience about above situation,

I have no problem CSRmeshv1.3 or CSRmeshv2.0 or CSRmeshv2.0.1

but in case of CSRmeshv2.1, &uart_rate = 0x0ebf and the latest SDKv2.6.2.9, I think there are no message in Putty(9216000)

Would you try and let me know what we are dong some wrong ?

Thanks,

Hwang 

  • Up0
  • Down0
Dr. Nissim Zur
Profile picture
Join Date: 6 Jun 16
Location: Skype: nissim.test CSR1010 External design house
Posts: 235
Posted: Wed, 2016-12-28 23:34

Please call my Skype nissim.test There is no need for 9216000 Bit/sec use 115200 Bit/sec

  • Up0
  • Down0
DS.Hwang
Join Date: 30 Aug 16
Posts: 6
Posted: Wed, 2017-01-04 01:19

This issue is closed, it were minor differences from previous

==============================================

Main_app.c -> AppInit() -> DebugWriteString(“AppInit\r\n”); 

  • Up0
  • Down0
Sandro
Join Date: 14 Feb 18
Location: Curitiba
Posts: 1
Posted: Sat, 2018-05-19 05:07
Nissim,
 
Please, could you clarify a doubt, .. can I share the debug pins (Pio5 .. Pio8) with my application during the debug? thank you,
  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.