• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 51 subscribers
  • Views 1901 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RTOS/CC2640: CC2640F128, CC2650

Maximilian
Intellectual 360 points

Part Number: CC2640

Tool/software: TI-RTOS

Hi,

i'm trying to add UART to the Simple Peripheral Projekt out of the SimpleLink 2.01.00 Version. 

If i add UART_init(); to main.c it compiles but the device stucks immediately after flashing.

I'm using the correct Board.h for my CC2640F128 5x5. 

If i try adding uart to the empty CC2650DK 5XD example, everything works fine.

I'm facing the similar problem which is descripted in this thread: 

CC2650 Trying to add Simple to Uart to Simple Peripheral Example

The solution which is provided there, is not enough for my use case. 

How can i add UART to my project?

regards Maximilian

  • 0
    TI__Guru 56590 points

    Hello Maximilian,

    Please review these steps:

    - Review the uartecho code example.

    - Add your specific board file and make sure the project include path is set to your board file location and no other:

    - Make sure that your board file has an UART configuration. Refer to the UART begin section in the

    C:\TI\tirtos_cc13xx_cc26xx_2_20_01_08\products\tidrivers_cc13xx_cc26xx_2_20_01_10\packages\ti\boards\CC2650DK_5XD\CC2650DK_5XD.c

    /*

    *  ============================= UART begin ===================================

    */

    ....

  • 0 in reply to Eirik V
    Intellectual 360 points
    Hi Erik,

    thanks for the hint.

    The same error occurs if i use a untouched simple peripheral project and change the following things:
    1. Changing the include path from CC2650EM_7ID to CC2650EM_5XD which comes with the sdk
    2. adding uart_init() to main.c

    I've checked the board files and the uart echo example. The UART begin section looks exactly like the one in the uart echo example.

    best regards


    Maximilian
  • 0 in reply to Maximilian
    TI__Guru 56590 points
    Hello Maximilian,
    Have you tried with the latest, ble_sdk_2_02_01_18 SDK?
  • 0 in reply to Eirik V
    Intellectual 360 points
    Hi Erik,

    I've also tried the latest version. The same problem. If i add UART_init() the device hangs straight after debugging.

    It seems, it stucks while flashing.
  • 0 in reply to Maximilian
    TI__Guru 56590 points
    Hello,
    Which IDE are you using?

    Have you review the debugging steps in our latest SDG?
    software-dl.ti.com/.../ble-debugging.html
  • 0 in reply to Eirik V
    Intellectual 360 points

    Hi,

    Eirik V said:
    Have you review the debugging steps in our latest SDG?
    software-dl.ti.com/.../ble-debugging.html

    no i didn't it before. But now i've checked the CFSR Register and the IMPRECISERR is set:

    Eirik V said:
    Which IDE are you using?

    I'm using CCS 7.2.

    best regards

  • 0 in reply to Maximilian
    TI__Guru 56590 points
    This smells like either some problem with illegal PIN configuration or using incorrect peripheral driver initialization objects in the board file (perhaps from another installation?). Did you follow all the steps in section 10.1 Adding a Board File in the CC2640 BLE Software Developer’s Guide (SWRU393)? If so I can try the same to verify on my end. I have not tried CCS 7.2 on that older installation myself yet. Make sure to use the TI Compiler version specified in the Release Notes for the respective SDK.
  • 0 in reply to Eirik V
    Intellectual 360 points

    Hi Eirik,

    for the first time, i didn't use a custom Board file. I only select the one how comes with SimpleLink for the 5x5 package:

    I've also done a complete new installation of the IDE and SimpleLink. 

    Concerning the Compiler i only get the hint, that i use a little bit higher version. Do you think that this could be a problem?