• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 38 subscribers
  • Views 620 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.

TIDA-010024: with CC1312R1F3 rev e (CC1312 Rev D LaunchPad)

AllanD
Expert 1085 points
Part Number: TIDA-010024
Other Parts Discussed in Thread: BOOSTXL-SHARP128

I received recently the CC1312R1 LauchPads, revision D, but was happily surprised to find revision E silicon on the kit.

I am attempting to start development of a subgiga mesh network using TIDA-010024 as a starting point.

Has this been tested with the revision E silicon?

I can load it into the LaunchPad, and then in the serial terminal "TI Sensor" is displayed, sometimes LEDs turn on/off, but can't track what is going on.

I have looked over the included PDF file carefully, I am not sure what is expected when the power is applied.

I have tested using the pre-built firmware, and firmware built in CCS 9.

Since support, such as resource explorer, seems to have stopped working in CCS8 I have upgraded to CCS9.

I have also installed SimpleLink CC13x2 26x2 SDK 2.40.0.81 and encounter no build errors.

Please advise a little on what I should expect running the reference design.

I have been attempting by programming one CC1312R1 LaunchPad with the debug_poll, and the other with the debug_root_poll configurations.

I have enabled the serial output in the Application/defines/sensor.opts file.

I also have the LCD BoostPack (BOOSTXL-SHARP128) available which I have also tried, but same output as on serial terminal.

I currently have three revision E silicon LaunchPads with LCD displays available for testing.

Any suggestions are appreciated, thank you!

  • 0
    TI__Mastermind 35030 points

    Hi,

    Yes, Rev E silicon is supported on SDK versions 2.40 and newer (as noted here: e2e.ti.com/.../767777 ).

    CCS 8.3 is still viable for building projects in the 2.40 SDK (see release notes in top SDK directory).

    For default application behavior:
    - debug_root_poll starts polling about 60 seconds after power up, then polls every 10 seconds (see app_task() in 6lowpan/app_task_root.c).
    - debug_poll echos back the received packet (see app_task() in 6lowpan/app_task_node.c).

    You may also try a single channel so a sniffer may be used to show over-the-air traffic, as suggested in section 3.1.2.2.3.2 of www.ti.com/.../tiduef7a.pdf

    Regards,
    Toby

  • 0 in reply to Toby
    Expert 1085 points

    Thank you for your reply.

    I think the application is working correctly, but the LCD or UART is not getting any debug output.

    I can set breakpoints and data is indeed being sent back and forth between the two LaunchPads.

    Either UART or LCD, both show have the same issue, I see "TI Sensor" and that is the extent of the output.

    LEDs on the LaunchPads do show activity, so the MCU defiantly is still running correctly and not frozen.

    I am digging into the code to see where the trouble is but, I believe it is a debug output issue.

    EDIT: UART_write does not appear to be functioning as intended... I am investigating this on my end, any help is appreciated.

  • 0 in reply to AllanD
    TI__Mastermind 35030 points

    Have you defined either BOARD_DISPLAY_USE_UART or BOARD_DISPLAY_USE_LCD?

    Please check Application/Defines/sensor.opts.

  • 0 in reply to Toby
    Expert 1085 points

    Hi Toby,

    Yes, I have tried both, then performed a clean and rebuild as sometimes just a build didn't catch the change.

    "TISensor" is displayed on the selected device (UART or LCD) but then after there is no more output.

    UART_Write is being executed correctly in code, but the message never makes it out to the device.

    I believe the UART or LCD is operating in interrupt mode, perhaps this interrupt is not firing correctly.

    The text "TI Sensor" is written to the display using LCD_WRITE_STRING in 6lowpan_mesh_ti_15_4_cc1312_tirtos_ccs/Application/ssf.c I believe.

    It seems that UART_Write may not be redirected to LCD_WRITE_STRING correctly.

    Can you reproduce the issue on your end by chance?

  • 0 in reply to AllanD
    Expert 1085 points

    Hi Toby,

    I am going to mark this thread as solved as this is apparently not an issue of silicon revision E support, and create a new topic concerning the debug output.

    Thank you for your previous replies.

  • 0 in reply to Toby
    Expert 1085 points

    I set up a new thread to continue the discussion about the debug output issue, when I submitted it it would not go through and said it was blocked for moderation (no reason specified), so until that new thread request is released I can continue discussion here, unless there is a way to release it.

    EDIT: it appears the new thread is now visible, the discussion can be continued there

    https://e2e.ti.com/support/tools/sim-hw-system-design/f/234/t/825610