• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 3 answers
  • Subscribers 56 subscribers
  • Views 1267 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.

Original question:

RTOS/LAUNCHXL-CC1352R1: How do I see communication between CC1352 (sensor node) in mmwaveicboost?

RTOS/LAUNCHXL-CC1352R1: The cc1352r1 sensor node does not send commands to the iwr6843isk

chunghee cho
Expert 1180 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: IWR6843ISK, IWR6843, TIDA-010022

Tool/software: TI-RTOS

The cc1352r1 sensor node does not send commands to the iwr6843isk. What should I do?

I connected in the same way TI answered and confirmed that cc1352r1 did not send a command.

https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/801437

dio12, dio13

Nothing is output.

We also tried pressing nRST button and confirmed that it was connected to the connector node.

I connected the iwr6843 and cc1352r1 like the picture.

How do I debug cc1352r1 in this state?

I want to debug the part where cc1352 sends command to iwr6843.

http://www.ti.com/lit/ug/tidued6a/tidued6a.pdf

Define DEBUG_PRINT from the code in this example. How can I read mmwaveLoggerUart?

  • 0
    TI__Mastermind 23356 points
    Hello Chunghee cho,

    I am working to find the appropriate expert to help you. This may take some time to reach the right person depending on availability. I appreciate your patience.

    Regards,

    AB
  • 0
    TI__Expert 8785 points

    Chunghee,

    In CC1352, there are two UART ports used: one to configure the mmWave, another to read the mmWave output.
    In your code screenshot, you will not see those UART output until the mmwave has been configured and running.

    The sensor flow is:

    • Wait 30 seconds for everything to power up
    • Wait for the sensor to connect to the collector
    • Send configuration commands to mmWave using UART0
    • If successful, mmWave will start sending information using UART1

    To verify that the CC1352 is sending the configuration commands, you can do the following:

    • Flash mmwave collector code to one CC1352
    • Flash mmwave sensor code to another CC1352
    • In the sensor board, DO NOT connect the mmWave EVM
    • Probe UART0 on CC1352 sensor board
    • Power on both CC1352 launchpad
    • Pair sensor to collector
    • Wait 30 seconds
    • Check UART0 output
    • You should see "dfeDataOutputMode 1" printed on the screen.  It will stop there, since the mmwave is not connected. 
      • If you see the output, that means the cc1352 is sending out commands. Check Section 3.1.1 (Hardware setup) for more information on how to pair the CC1352 and IWR6843
      • If you do not see the output, then make sure the sensor is paired to collector, you are probing the correct UART pin, and you have waited 30 seconds.

  • 0 in reply to clam
    TI__Mastermind 29111 points
    "You should see "dfeDataOutputMode 1" printed on the screen. It will stop there, since the mmwave is not connected."

    Just one clarification here. The CC1352 will send character by character in the command string and expect an echo for each character. If the mmWave board is not connected, there will be a timeout between each character.
  • 0 in reply to Gus Martinez
    Expert 1180 points

    "dfeDataOutputMode 1" is not displayed on the screen.

       

    "you are probing the correct UART pin"

    > connected dio12, dio13, gnd. The uartecho example worked fine.

    "then make sure the sensor is paired to collector"

    > The red led lights up, so it looks like a connection to the connector.

    " and you have waited 30 seconds"

    > There is no reaction even if I wait more than 30 seconds.

    I manually patched this firmware.

    firmware  : http://www.ti.com/tool/simplelink-cc13x2-26x2-sdk - ti\simplelink_cc13x2_26x2_sdk_2_40_00_81\examples\rtos\CC1352R1_LAUNCHXL\ti154stack\collector and sensor

    patch : http://www.ti.com/tool/TIDA-010022 - ti\TIDA010022-Firmware\0001-mmwave-cc1352-collector.patch and 0001-mmwave-cc1352-sensor.patch

    http://wapeul.com/wifi/collector_CC1352R1_LAUNCHXL_tirtos_ccs.zip

    http://wyplug.com/wifi/sensor_CC1352R1_LAUNCHXL_tirtos_ccs.zip

    Is this a problem?

  • 0 in reply to chunghee cho
    TI__Expert 8785 points

    Just to confirm, nothing is printed at all on the terminal?  Have you tried flashing the pre-built binary provided in the TIDA-010022 firmware?  

    The patch was built on an older simplelink SDK (2.10.00.48).  Therefore, if you patch it on the newer SDK (2.40.00.81), the patch might not implement all the changes.  For anything that was not modified, did you make sure to manually modify the code?

    --Christina

  • 0 in reply to clam
    Expert 1180 points
    Yes, Nothing is printed on the terminals.
    And I modified the code manually.
  • 0 in reply to chunghee cho
    TI__Expert 8785 points
    Can you flash the pre-built binary that is provided in the TIDA-010022 onto your Launchpad? We have verified that those binaries work, so it will be good to know if this is a software or hardware issue.

    How did you manually modify the code? We are unable to download the zip file that you provide.
  • 0 in reply to clam
    Expert 1180 points

    Sorry Link is wrong:
    wyplug.com/.../sensor_CC1352R1_LAUNCHXL_tirtos_ccs.zip
    >> wapeul.com/.../sensor_CC1352R1_LAUNCHXL_tirtos_ccs.zip
    And the binary is not working with your bin. Your bin file is 2.10 based and our EVM HW is 2.40.x based. Therefore, there is no response or result if we use your 2.10.x based bin file.

    When we applied the patch contents in the source code of 2.40.x SDK source, UART TX fails in the following picture. We don't know what to do further in this project. Please guide us in easy step. not sending out packet when we probe it in UART receiver side in 68

  • 0 in reply to chunghee cho
    TI__Expert 8785 points

    Looking at your UART configuration (CC1352R1_LAUNCHXL.c), the UART are configured differently.

    In your code,

    • UART0_BASE points to MMWAVE_UART1_RX
    • UART1_BASE points to CC1352R1_LAUNCHXL_UART1_*.

    In our version,

    • UART0_BASE points to CC1352R1_LAUNCHXL_UART0_*
    • UART1_BASE points to MMWAVE_UART1_RX

    Since the UART pin assignments are different, you will not see the UART output.

    Try the following modifications in CC1352R1_LAUNCHXL.c

    • Line 973-974

    .txPin = CC1352R1_LAUNCHXL_UART0_TX,
    .rxPin = CC1352R1_LAUNCHXL_UART0_RX,

    • Line 989-990

    .txPin = PIN_UNASSIGNED,
    .rxPin = MMWAVE_UART1_RX,