LAUNCHXL-CC1352R1: LAUNCHXL-CC1352R1 + LPSTK-CC1352

Thanks, Arthur. Will try this example.

Hello, Arthur!

I'm working on the Thread CLI Project Zero using a LAUNCHXL-CC1352R1 Launchpad. The CC1352R1F3.ccxml and ot-rcp.out files are set up correctly, and I've also properly configured the terminal settings (115200 baud rate, 8-bit data, 1 stop bit, no parity, and no flow control). However, I'm still not getting any output in the terminal. Any advice would be greatly appreciated! Thank you!

Hi Timothy,

you will not get a human readable serial output with the ot-rcp application, as its serial output is made to be connected to the ot-ctl host application: https://github.com/TexasInstruments/ot-ti/tree/main/examples/apps/rcp

Regards,

Arthur

Thank you, Arthur. Will let you know if this works. :))

Hello, Arthur!Hello! I got it working using your solution.

Currently, I’m working on the Linux Gateway with the LPSTK-CC1352R, LAUNCHXL-CC1352R1, and a Raspberry Pi 4 Model B.

However, when I reach task 5 and try to run ./run_demo.sh, the terminal on my Raspberry Pi starts buffering and stuttering. I tested running run_collector.sh and run_gateway.sh individually, and it appears that the issue is with run_collector.sh, though I’m not sure what’s causing it.

Is there anything I need to modify since I’m using an RPi instead of a BBB?

Hi Timothy,

Are you using the prebuilt binaries? It may be that you have to rebuild those, to target the RPi libraries and architecture.

Regards,

Arthur

Hello!

Are you referring about the prebuilt folder from the `bbb_collector.tar.gz` that contains `run_demo.sh`, or are you referring to the AM335x Sitara Processor SDK for Linux?

I'm currently working on using an RPi, and I skipped the step below because it mentioned that the SDK was specifically for the BBB. I believe that might be why things aren't working as expected.

The instructions state: "To cross-compile for BBB, install TI’s AM335x Sitara Processor SDK for Linux. This SDK includes all the cross-compilation tools, headers, libraries, and other necessary files for the BBB."

Is this SDK also compatible with the RPi?

Thank you for your help!

Hi Timothy,

That's indeed the folder I am referring to.

For the RPi, if you build it on RPi itself (no cross compiling), you should be able to build the projects by running ./build_all.sh host. This will make use of the native gcc version.

Regards,

Arthur

Hello! I tried your suggestions, but it’s still not working.

Here are the steps I followed for reference:

1. I downloaded the TI-15.4 SDK on my Linux machine.
   
   
2. I transferred the files from the SDK folder to the RPi using this command:
   bash

   scp -r ti154stack_linux_x64_4_40_00_03 root@<MyIPAddress>:/path 
3. I rebuilt the prebuilt binaries using this command:
   bash

   ./build_all.sh host
4. After rebuilding, I ran ./run_demo.sh inside the "prebuilt" folder.

However, it’s still showing the same error as in the screenshot above. I think the connection is working, but there seems to be an issue that I can't figure.

Thank you for helping with my questions!

Hi Timothy,

The newly built binaries will not be in prebuilt, but instead under the components paths: ~/ti/ti154stack_linux_x64_4_40_00_03/example/collector (for instance).

This mean that you have to modify the run_demo.sh script to point to those new locations.

Regards,

Arthur

Hello, Arthur!

After updating run_demo.sh to use the correct directories and rebuilding the prebuilt binaries, which version should I use to run run_collector.sh given that I used the command ./build_all.sh host?

Should I continue using bbb_collector or switch to host_collector?

P.S. The host_collector won’t work on the RPi since it’s built for x86_64 architecture.

Hello Timothy,

Host in that case means the host on which it was compiled. If you compiled it on the RPi, it will run on it.

You should then switch to host_collector if that's the case.

Regards,

Arthur