• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 2 answers
  • Subscribers 55 subscribers
  • Views 278 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2538: CC2538 about ota uart protocol Polling?

userjiabo
Genius 4440 points
Part Number: CC2538

Hi TI team

FE 0A 09 00 14 8A 00 E0 88 00 00 0E 1A 09 E8 /FE 0A 09 00 14 8A 00 C4 EB 00 00 0E 1A 09 AF

I want to know where the data packet on the zstack3.0.2 as above.

or it stands for what meaning? Because I had shielded the timer on the init function(void OTA_Dongle_Init( byte task_id )) 

//osal_start_timerEx( OTA_Dongle_TaskID, OTA_DONGLE_DONGLE_NOTIFY_EVT, 4000 );

but from the serial data result:it also printf on the serial tool with a timer.

Thanks!

  • 0
    TI__Mastermind 28320 points

    Hi,

    Both of those commands still seem to indicate that this is a OTA_DONGLE_DONGLE_NOTIFY_EVT.

    How often do you see these commands at the console?

    Can you debug to see if the device enters the function OTA_Send_DongleInd(.) ?

    Regards,
    Toby

  • 0 in reply to Toby Pan
    Genius 4440 points

    Hi Toby

    yes,it seem that it can enter the function OTA_Send_DongleInd().

    Please check my picture.

    use zstack3.0.2.

    Thanks!

  • 0 in reply to userjiabo
    Genius 4440 points

    Hi Toby

    /*

    if ( events & OTA_DONGLE_DONGLE_NOTIFY_EVT )
    {
    OTA_Send_DongleInd();
    osal_start_timerEx( OTA_Dongle_TaskID, OTA_DONGLE_DONGLE_NOTIFY_EVT, 4000 );
    return ( events ^ OTA_DONGLE_DONGLE_NOTIFY_EVT );
    }

    */

    I shield these code,these commands at the console can not show on the serial tool.

    Thanks!

  • 0 in reply to userjiabo
    TI__Mastermind 28320 points

    What are the values for the other events you've defined and handle in OTA_Dongle_event_loop(.) ? (Such as GENERICAPP_EVT_1, GENERICAPP_EVT_2, ...)

    Make sure these values do not equal OTA_DONGLE_DONGLE_NOTIFY_EVT (default value is 0x0002).

  • 0 in reply to Toby Pan
    Genius 4440 points

    Hi Toby 

    I had tried a oringal example to check it with the same way,also sent serial data with a timer,see the picture.

    Thanks!

  • 0 in reply to userjiabo
    TI__Mastermind 28320 points

    Thanks for confirming values of other events.

    Can you tell what is period of the OTA_DONGLE_DONGLE_NOTIFY_EVT? How many seconds are between each one?

  • 0 in reply to Toby Pan
    Genius 4440 points

    Hi Toby 

    from the packet seem that it is one second between each one.

    I had test it,this is 1 second cycle to connect the otaserver tool.

    The otaserver tool received this can scan the panid network,and so on.

    void OTA_Dongle_Init( byte task_id )

    {

      //osal_start_timerEx( OTA_Dongle_TaskID, OTA_DONGLE_DONGLE_NOTIFY_EVT, 4000 );

    }

    But I shielded the timed event,also appeared the 1 second cycle Heartbeat to PC tool.

    Because I want to add my appilcation code on the dongle-server example code.

    Thanks!

  • 0 in reply to Toby Pan
    Genius 4440 points

    Hi Toby

    FE 06 41 80 00 02 00 02 07 02 C2
    FE 04 09 00 14 83 21 28 93
    FE 04 09 00 14 83 21 28 93

    what these command? 

    I had shielded two parmeters of LCD display.

    xLEGACY_LCD_DEBUG
    xLCD_SUPPORTED=DEBUG

    also printf these command if run on the power.

    Thanks!

  • 0 in reply to userjiabo
    TI__Mastermind 28320 points

    After looking through the values for your events again, I realize that you have GENERICAPP_EVT_2 == 0x0003.
    The event is a bit mask, so that when GENERICAPP_EVT_2 is triggered, bit 0 and bit 1 are set. However, bit 1 is also used for OTA_DONGLE_DONGLE_NOTIFY_EVT, so that may be why you see this over the serial interface.

    I recommend changing definition of GENERICAPP_EVT_2 to a uniqe bit (for example, it looks like you can use 0x0004).
    Also please note that you should not use 0x8000, since this is reserved for SYS_EVENT_MSG event.

  • 0 in reply to Toby Pan
    Genius 4440 points

    Hi Toby

    OK,has modified about this.

    Thanks!