• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 433 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.

LP-CC1352P7: CC1352P7 Wi-SUN OAD failed

Tim Cruise
Intellectual 978 points
Part Number: LP-CC1352P7
Other Parts Discussed in Thread: CC1352P7

Dear TI Engineers,

I am facing difficulty running the Wi-SUN OAD demo:
https://dev.ti.com/tirex4-desktop/content/cc13xx_cc26xx_simplelink_academy_7_40_01_00/_build_cc13xx_cc26xx_simplelink_academy_7_40_01_00/source/ti_wisunfan/wisun_oad/wisun_oad.html

This is my setup:

  1. BeaglePlay with BeaglePlay Debian OS 2023 October as boarder router host
  2. on-board CC1352P7 flashed with CCS Wi-Sun broader router firmware
  3. a CC2352P7-1 launchpad flashed as off-chip OAD COAP wi-sun router node
  4. CCS 12.7.1, SDK is also the newest 7.40.00.77

I followed the procedures described in the tutorial above.  I could ping the COAP router node from my BeaglePlay host within spinel-cli.py.  However, when I issued

getoadfwver <ipv6 address>

spinel-cli reported that it was not a COAP node.

Another problem is: my COAP node was connected to a windows desktop.  When I ran spinel-cli.py to connect to it and enter command role, it did not respond at all.

So what did I do wrong?  How do I correct my procedures?

Yours faithfully,
Timmy

  • 0
    Intellectual 978 points

    Here is another error reported by this script:

    sudo /usr/local/ti-wisunfantund/coap-client-scripts/run_coap_get.sh 2020:abcd::212:4b00:14f9:675c

    Starting the COAP Process with IP Address 2020:abcd::212:4b00:14f9:675c
coap-client -m get coap://[2020:abcd::212:4b00:14f9:675c]/led -o c.bin
/usr/local/ti-wisunfantund/coap-client-scripts/run_coap_get.sh: 21: [: 1: unexpected operator
/usr/local/ti-wisunfantund/coap-client-scripts/run_coap_get.sh: 35: [: 1: unexpected operator
/usr/local/ti-wisunfantund/coap-client-scripts/run_coap_get.sh: 21: [: 2: unexpected operator
/usr/local/ti-wisunfantund/coap-client-scripts/run_coap_get.sh: 35: [: 2: unexpected operator

  • +1
    Intellectual 978 points

    OAD upgrade worked after I did a hard reset of the COAP Launchpad.

    The problem is:

    The previous firmware is non-oad.  A hard reset is required in order to activate the newly flashed oad firmware.

  • 0 in reply to Tim Cruise
    Intellectual 978 points

    Please also solve these errors.  These are produced by ti wisunfantund scripts.

    Regards.