• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 280 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.

CC2340R5: Why did UART TX send messages after Board_init()?

YW Lin
Intellectual 540 points
Part Number: CC2340R5


Hi TI members,

Below is my building environment:

Software

Version

Code Composer Studio

12.3.0.00005 

SimpleLink SDK

7.10.00.35

XDCtools

3.62.1.16_core

We are using a project that would call Board_init(); in main() of main_freertos.c.

We had another CPU that would listen to the BLE MCU UART TX and print what it had received.

We found some unexpected messages received by the CPU.

Can we suppress these messages?

Since it might mislead the CPU with messages what it didn't recognize.

Thanks.

BR,

  • 0
    TI__Expert 5354 points

    Hi YuWen,

    Are you sure this is coming from the Board_init() Command? 

    Actually I tried to reproduce it by taking our basic_ble example and remove everything except the board init. 

    There was not output at the UART terminal. 

    Can you please double check if the prints are comming from this function? 

    If not, can you please tell me when it occurs and give some information on how to reproduce it. 

    It would be nice to know which example you used and what caused the occurence of these UART messages.

    Can you also try to check if the same messages occur on a UART terminal at your PC using the uart via XDS? 

    Regards,

    Alex

  • 0 in reply to Alex Paul
    Intellectual 540 points

    Hi Alex,

    I'm using the project that combined data_stream and UART that TI had developed for us.

    I guessed it was produced by Board_init() since I ran the program in debug mode, and right before Board_init(), in the CPU's logs:

    It received "0x00" which was as expected since I saw this everytime I start debugging the program.

    But then after I stepped over Board_init() (haven't step over Line 98):

    0xFD just suddenly came out, and that was why I doubted it was done by Board_init().

    Let me try the XDS and get back to you later.

    Thanks.

    BR.

  • 0 in reply to YW Lin
    TI__Expert 5354 points

    HI YW,

    keep us updated we will have a look into the code we provided to find a solution for this one. 

    Regards,

    Alex

  • 0 in reply to Alex Paul
    Intellectual 540 points

    Hi Alex,

    Thanks for your advice.

    In XDS, we did observed different behavior.

    This was before we stepped over Board_init():

    (Left window was the XDS terminal)

    After steppiing over Board_init(), nothing was printed on the terminal.

    But after the vTaskStartScheduler(), the unexpected symbols appeared.

    We could only confirm that we did print a string "v0.0.0.1" within appMain();

    But the unexpected symbols seemed to overwrite the "v" in the front of the string.

    And we also modified the order of some of the functions used in data_stream+UART.

    Would it be useful for TI if we provide what we had modified?

    (We had modified app_main.c, app_data_stream.c)

    If so, please let me know and I'll send those files that we had modified.

    I think we may have wrongly used any of TI's APIs that made this issue.

    Please help us identify what we had misused.

    Thanks.

    BR,

    YuWen

  • 0 in reply to YW Lin
    TI__Expert 5354 points

    Hi YuWen,

    Yes it would definetly help us to reproduce your issue.

    Regards,

    Alex