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 OAD

Part Number: LP-CC1352P7
Other Parts Discussed in Thread: CC1352P7, UNIFLASH, WI-SUN

Hi,

I was trying to do OAD on CC1352P7-1 Dev kit. I did:

1. Programed dev kit with bim_offchip_LP_CC1352P7_1_nortos_ticlang.hex  and ns_coap_oad_offchip_src_LP_CC1352P7_1_tirtos7_ticlang.bin simultaneously with uniflash

2. Then Programmed dev kit with ns_coap_oad_offchip_src_LP_CC1352P7_1_tirtos7_ticlang.hex

3. After getting connected with Border Router 

i executed command 

startoad 2020:abcd::212:4b00:2853:2fe8 CC1352P7 64 ns_coap_node_src_LP_CC1352P7_1_tirtos7_ticlang.bin

I am getting following error. OAD image filesize: 341976 bytes
C:\Ranjit\Workspace\OAD-Spinel\ti-wisunfan-pyspinel\oad_log_2020-abcd--212-4b00-2853-2fe8_2023-05-30-T16-10-42.txt
Sending OAD notification request message
Logging results in C:\Ranjit\Workspace\OAD-Spinel\ti-wisunfan-pyspinel\oad_log_2020-abcd--212-4b00-2853-2fe8_2023-05-30-T16-10-42.txt
spinel-cli >
CoAP packet received from 2020:abcd::212:4b00:2853:2fe8: type: 2 (Acknowledgement), token: 9369953346641921073, code: 2.04 (Changed), msg_id: 0
OAD notification response received
OAD upgrade rejected

please let me know with the steps, If I am doing in wrong way.

  • Hi Ranjit, 

    This Readme file has the steps for Wi-SUN OAD. 

    https://dev.ti.com/tirex/explore/node?node=A__ALTkB7X12rX9POpOsZilZA__com.ti.SIMPLELINK_CC13XX_CC26XX_SDK_WISUNFAN_MODULE__BSEc4rl__LATEST

    Please note, you need to use MCUBoot and not BIM. 

    If the above steps are unclear, please reply here. 

    Regards,
    Sid

  • Hi Sid,

    As suggested in doc , i did the modification and loaded the images in the controller using uniflash.

    After reset i am fiding Red Led flashing continuously. I believe, it is strucked somewhere in MCUBOOT code. 

    what could be the probable root cause and solutions to this?

  • Hi Ranjit, Please can you try adding 0x0 in the Load address for the ns_coap_oad image in uniflash? Force the load address to 0

  • still, situation is same

  • still, issue is same.

  • Hi SId,

    Any Suggestions on this?

  • Hi Ranjit, 

    It seems to be the expected behavior. LED behavior while connecting to a Wi-SUN network, has been updated this quarter.

    The Readme for the ns_br project is updated to reflect this. 

    Please check nanostack_wait_till_connect() function. 

    void nanostack_wait_till_connect()
    {
        uint8_t _net_state;
        if (_blocking)
        {
    #ifdef NWK_TEST
            ticks_before_joining = ClockP_getSystemTicks();
    #endif //NWK_TEST
    
            // wait till connection goes through
            while(connectedFlg == false)
                {
                    /* Toggle red LED at rate of state*100 ms. Slower the blinking, closer it is to joining */
                    _net_state = get_current_net_state();
                    usleep((_net_state + 1) * 100000);
                    // max usleep value possible is 1000000
                    GPIO_toggle(CONFIG_GPIO_RLED);
                }
            /* Solid Green to Indicate that node has Joined */
            GPIO_write(CONFIG_GPIO_RLED, CONFIG_GPIO_LED_OFF);
            GPIO_write(CONFIG_GPIO_GLED, CONFIG_GPIO_LED_ON);
    
    #ifdef NWK_TEST
            ticks_after_joining = ClockP_getSystemTicks();
    #endif //NWK_TEST
        }
    }

    I am really sorry for the inconvenience.

    Regards,

    Sid

  • Hi Sid,

    Whn i run OAD code individually on RN, it runs perfectly, blinking Green while connecting and Sloid green on connection gets established. 

    When i program MCUboot code and OAD code through uniflash, loading both at same time. The ROuter node starts blinking RED LED keeping Green LED off. The RN doesn't gets connected to BR, this time.

  • Hi Ranjit,

    I want to verify a couple of things. Are you still  using the ns_coap_oad_offchip_src project?

    The LED blink behavior is dictated by the code in the function I have attached in my previous response. It is found in application.c source file.

    The RED LED should blink while waiting to join and once the device joins the network, the GREEN LED is switched on. This is the expected behavior. 

    Which project do you use when you see the blinking green LED? Are you using the ns_coap_node project from SDK 6_40?

    Please make sure you use the projects from SDK 7_10 to use OAD and ensure that they use the same PHY.

    I just tested out the example along with MCU Boot . It seems to work fine with RED LED blinking and then solid Green LED after joining the network.

    Regards,

    Sid

  • yes, I am using ns_coap_oad_offchip_src_LP_CC1352P7_1_tirtos7_ticlang . 

    SDK is 7.10.98.

    with NO MCUBoot code and only ns_coap_oad_offchip_src_LP_CC1352P7_1_tirtos7_ticlang  code. i gets this error

    CoAP packet received from 2020:abcd::212:4b00:2853:2fe8: type: 2 (Acknowledgement), token: 9369953346641921073, code: 2.04 (Changed), msg_id: 0
    OAD notification response received
    OAD upgrade rejected

    This mean stack in 7.10.98. Though i know, I have updated stack. with the same code, LED blinking is green when connected.

    Problem comes, when i program both at same time. 

    Let me know, which two codes you are using,. I will verify with that example.

  • Hi Ranjit, 

    My SDK version: 7_10_00_98.

    Border Router Project: ns_br_LP_CC1352P7_1_tirtos7_ticlang

    MCU_BOOT project: mcuboot_LP_CC1352P7_1_nortos_ticlang

    OAD project: ns_coap_oad_offchip_src_LP_CC1352P7_1_tirtos7_ticlang

    UniFlash Settings:

    After switching on the Border Router, after a couple of minutes, the node joins the network. At the point the RED LED stops blinking and the green LED turns on Solid Green.

    MCUBoot is needed for the device to boot into the correct image for the OAD to work. Please make sure you have configured the MCUboot according to the Readme steps. 

    The following error is a different issue. 

    CoAP packet received from 2020:abcd::212:4b00:2853:2fe8: type: 2 (Acknowledgement), token: 9369953346641921073, code: 2.04 (Changed), msg_id: 0
    OAD notification response received
    OAD upgrade rejected

    Have you upgrade the version number in the post build step before performing OAD. It is described in the Readme. 

    The Node will reject the firmware with the same version number. It only accepts firmware with a higher version number.

    Regards,

    Sid