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.

[FAQ] CC1352P7: Is ti-wisunfantund working with the newly released BeaglePlay? (yes)

Part Number: CC1352P7

Hello all E2E Community Members,

Lately, we have been asked a lot whether ti-wisunfantund would work on the BeaglePlay using its embedded CC1352P7, or not.

The answer is yes, it does work, even from the default Debian image that comes loaded in its eMMC memory. No need to create a bootable SD card.

Here is a quick start guide that describes the process:

  1. Disable the bcfserial driver, and reboot the BeaglePlay according to the following instructions:

    This will allow us to gain access to /dev/ttyS4, which is the UART interface connected to the embedded CC1352P7.

  2. Flash the embedded CC1352P7 with the ns_br example, from the SIMPLELINK-LOWPOWER-F2 SDK:
    1. Using the TagConnect JTAG connection present on the BeaglePlay.
    2. Using the script mentioned in the BeaglePlay documentation. This will flash the chip using its internal bootloader.
  3. With the BeaglePlay connected to Internet, install libcoap2-bin from apt, to acquire coap-client:
    sudo apt install libcoap2-bin

After completing all of the above steps, follow the instructions from, and you should have a working ti-wisunfantund setup!

NOTE: In ti-wisunfantund/ti-wisun-webapp/server/src/AppConstants.js, we recommend changing the default CONSTANTS to the following:

 * Program-wide options
const CONSTANTS = {
  OUTPUT_DIR_PATH: '/tmp/ti-wisun-webapp/output',
  PING_RESULTS_FILE_NAME: 'PingResults.csv',
  WFANTUND_PATH: '/usr/local/sbin/wfantund',
  BR_FILE_PATH: '/dev/ttyS4',
  PORT: 81,
  HOST: ['', 'localhost', '']

This will automatically using /dev/ttyS4, and expose the web server on most of the BeaglePlay's network interfaces.