This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2564C: STM3240G-EVAL and CC256xCFQN-EM problem running demo applications

Part Number: CC2564C

Hello,

I have a question regarding the User's Guide Datasheet:

SWRU498A–November 2016–Revised February 2017: http://www.ti.com/lit/ug/swru498a/swru498a.pdf

I' m using the recommended setup (STM3240G-EVAL, CC256xCFQN-EM and CC256XEM-STADAPT) with IAR studio to test the sample applications provided.

I can flash the demo software as described in the datasheet. I followed the links in the datasheet for the Wiki of demonstration applications.

But I can't verify the program because I don´t see any COM Port (COM X) either using the usb-otg or USART connection port of the evaluation board.

How can I access to the STM3240G-Eval board after flashing the .bin file for the use with a terminal program?

Thanks in advance.

Regards,

Tim G.

 

 

  • What is your hardware setup between your board and computer?
  • Thank you for the fast reply.

    I'm using the following hardware setup between the board and computer:

    1. CN8 (USB-OTG FS) or CN9 (USB-OTG HS) micro USB ports

    2. CN21 ST-Link/V2 USB Type B port for flashing using STM32 ST-Link Utility

    3. CN16 USART connector

    Reference: STM3240G-Eval Manual page 9

    However, after flashing the program and test of these ports, I will not see any virtual com port for communication.

    Any recommendations or suggestions?

    Thanks in advance.

    Regards,

    Tim G.

  • Tim,

    You should be able to see it through the CN16 USART connector. When you go to your computer's Device Manager, is no COM port available with the title "Prolific USB-to-Serial Comm Port"? Which kind of terminal are you trying to use to test?
  • Hi Dale,

    I tried on different computer using RS232-cable (null modem and 1:1) and a USB serial converter.
    Without the serial converter, the STM3240G-EVAL will not even be listed in the device manager in Windows.

    Moreover, I tried several terminal programs like Putty and HTerm using the USB serial converter dongle.
    I'm still not able to establish any communication between the board and the PC.

    Any suggestions?

    Thanks in advance.

    Regards
    Tim
  • Tim,

    I've been using Tera Term, have you tried with that? With the RS232-USB serial combination, and you see the COM port open in device manager, Tera Term will automatically detect ports being used and connect to them.
  • Hi Dale,

    Thank you again for your answer. There should not be any difference using TeraTerm or any other terminal program.
    However, I tried TeraTerm, again without a successful connection to the board.

    If I try to communicate from PC to PC using a RS232 port and RS232-USB serial converter, it works fine.
    So I assume that there might be a problem of the demo application code. Did you test communication over USART using a STM3240G-EVAL board?

    Thanks in advance.

    Regards
    Tim
  • Tim,

    I have no problem connecting to the STM3240G-EVAL board with any of the sample applications. Have you ensured that all the jumpers are placed in the correct position on the board?

  • Hi Dale,

    I checked the jumpers according to the datasheet: UM1641 :

    My board was delivered with the following pin setup:

    - JP1: (2-3) connected (D1 PE4)

    - JP2: (2-3) connected (D0 PE3)

    - JP3: not connected (CAN)

    - JP4: connected (PDR)

    - JP5: (2-3) connected (ETH CLK)

    - JP6: (2-3) connected (ETH_RX CLK)

    - JP7: (1-2) connected (CAN)

    - JP8: not connected (ETH_Mode)

    - JP9: not connected

    - JP10: not connected

    - JP16:(1-2) connected: I2S

    - JP18: (7-8) connected: PSU

    - JP19: (1-2) connected: VBatt

    - JP21: not connected (SMT IO)

    - JP22: (1-2) connected: (RS232)

    - JP24: not connected (EPROM WP)

    - JP26: not connected (CAM_PWDN)

    - JP29: not connected (BL-BTO)

    - JP31: connected: (OTG_HS_CS)

    - JP32: connected (VDD_MCU)

    - JP33: not connected: (MIC_STDBY)

    - JP34: not connected: (BL_RST)

    - Micro SD card is deasserted

    Do you have the same configuration setup?

    Thanks in advance.

    Regards

    Tim

     

  • Tim,

    I'll check those jumpers, but in the meantime, what about the jumpers on the CC256XEM-STADAPT board?
  • Hi Dale,

    Thanks again for your answer. The jumpers on the CC256XEM-STADAPT board are set as follow:

    JP1-JP6: (1-2) connected: (EVAL-CC256xEM)

    JP7-JP9: not connected

    R60,R70,R80,R90: connected via 0 Ohm resistor

    In the datasheet (SWRU417) it is mentioned to have also a brigde on R91 for USART6 working properly. Is this correct? On my adapter board, only R90 is bridged.

    Thanks again.

    Regards

    Tim

  • This is correct: on my board I have it set up with R61, R71, R81, and R91 all connected.
  • Hi Dale,
    I changed all the 0 Ohm resistors R60,R70,R80 and R90 to R61,R71,R81 and R91. So now I should be able to have communication on USART6.
    But I can't see any acitivity on the COM-Port(115200 baudrate, 8n1).
    In the datasheet of the STM3240G-EVAL board, only USART3 is mentioned. Is the USART6 from the adapter board routed to USART3 of the STM3240G-eval board?

    Thanks in advance.
    Tim
  • In HALCFG.h, what are the #define for CONSOLE_UART, CONSOLE_TXD_PORT, CONSOLE_TXD_PIN, CONSOLE_RXD_PORT, and CONSOLE_RXD_PIN? In my setup they read like this:

    #define CONSOLE_UART 3

    #define CONSOLE_TXD_PORT C
    #define CONSOLE_TXD_PIN 10

    #define CONSOLE_RXD_PORT C
    #define CONSOLE_RXD_PIN 11
  • Hi Dale,

    I checked the HALCFG.h file and changed the pin mapping according to your setup:

    From:

    #define CONSOLE_UART 2

    #define CONSOLE_TXD_PORT A
    #define CONSOLE_TXD_PIN 2

    #define CONSOLE_RXD_PORT A
    #define CONSOLE_RXD_PIN 3

    #define HAL_LED_PORT D
    #define HAL_LED_PIN 13

    To:

    #define CONSOLE_UART 3

    #define CONSOLE_TXD_PORT C
    #define CONSOLE_TXD_PIN 10

    #define CONSOLE_RXD_PORT C
    #define CONSOLE_RXD_PIN 11

    #define HAL_LED_PORT D
    #define HAL_LED_PIN 13


    After flashing the new .bin file, I see the following message using TeraTerm terminal:

    OpenStack().
    Stack Initialization on Port 1 115200 (UART) Failed: -4.
    Unable to open the stack.

    I don't know what is causing the error message. Any suggestions?

    Thanks in advance.

    Best Regards
    Tim Gerbert

  • Tim,

    Glad that it looks like we got the UART communication working.

    As far as the initialization error, please check the following: in IAR, right click on the project and go to Options->C/C++ Compiler->Preprocessor->Defined Symbols. If there is not a symbol defined __SUPPORT_CC256XC_PATCH__, try defining it and doing a clean build.

  • Hello Dan,

    I've checked the preprocesspr defined symbols. It already contains the symbol "__SUPPORT_CC256XC_PATCH__"

    Anything more I can do?

    Thanks in advance.

    Regards Tim

  • Hello Dan,

    Thank you very much for your help.

    I can connect right now to the board sucessfully. I downgraded from IAR 8.x to IAR 7.x due to wchar_t linker warnings (8.x uses 32 bit instead of 16 bit): http://netstorage.iar.com/SuppDB/Public/UPDINFO/012120/arm/doc/infocenter/iccarm.ENU.html

    Beside this, the main reason was a loose contact of the header pins from the CC256XEM-STADAPT board to the STM3240G-Eval board. I realized this when I could see LD 4 started to be active.

    After this, the communication via terminal program is possible.

    OpenStack().

    Bluetooth Stack ID: 1

    WBS support enabled.

    Device Chipset: Unknown (greater 4.1)

    BTPS Version : 4.2.1.0

    PLAT Version : 1.0

    App Name : HFPDemo_AG

    App Version : 0.3

    Project Type : 6

    FW Version : 12.12

    Local BD_ADDR: 0x88C255D1DB4D

    GAP_Set_Connectability_Mode(cmConnectable).

    GAP_Set_Discoverability_Mode(dmGeneralDiscoverable, 0).

    GAP_Set_Pairability_Mode(pmPairableMode).

    GAP_Register_Remote_Authentication() Success.

     

    ******************************************************************

    * Command Options: Inquiry, DisplayInquiryList, Pair, *

    * EndPairing, PINCodeResponse, PassKeyResponse, *

    * UserConfirmationResponse, *

    * SetDiscoverabilityMode, SetConnectabilityMode,*

    * SetPairabilityMode, *

    * ChangeSimplePairingParameters, *

    * GetLocalAddress, SetLocalName, GetLocalName, *

    * SetClassOfDevice, GetClassOfDevice, *

    * GetRemoteName, ManageAudio, *

    * OpenAudioGatewayClient, CloseAgClient, *

    * ServiceDiscovery, UpdateControlIndicators, *

    * CallWaiting, SendCallerIdNotification, *

    * SetRingIndication, RingIndication, *

    * SetVoiceRecognitionActivation, *

    * SetSpeakerGain, SetMicroPhoneGain, *

    * DisableRemoteSoundEnhancement, *

    * SendOperatorInfo, SendIncomingCallState, *

    * SendSubNumber, SendCallList, *

    * Help *

    ******************************************************************

     

    HFP AG>

    Thank you very much for your patience and the help.

    Best Regards

    Tim