• Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 191 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.

Power recycling

watson sun
Prodigy 180 points

Dear leo,

      There is a AP as Data Hub and many EDs.The Link Token and Join Token will not be changed after prgrammed in our products.
we had restored the connection info to the flash of CC1110. It could work perfect perfectly after power cycle, but we find a bug, The AP must be ready earlier than the EDs(rx poll), the EDs need to SMPL_Init successful, otherwise the EDs can only send message to AP,not receive message from AP.
    We have question, Not all info of SMPL_Init() can save to flash? We need link to AP successful once,
not need SMPL_Init() successful again next power cycle, after all we can not control which one start up first.
  we try to modify 'sAPAddress', 'sLinkToken', 'sJoinToken' in RAM of cc1110,but it is not helpful.
How can we do to solve it ?

  • TI__Guru 56650 points

    watson,

    I am splitting your post from the other thread, since it is something new to us. So just to make sure, you are using RX_POLLS compile option for this?

    Have you tried to do debugging on the CC1110 ED side? http://processors.wiki.ti.com/index.php/SimpliciTI_FAQ#Debugging_RF_Connection

    What happen if you put a breakpoint at MRFI_RfIsr() function in mrfi_radio.c after power cycle?

  • in reply to Leo Hendrawan
    Prodigy 180 points

    hi Leo,

         YES, we are using ED at RX_POLLS complie option on sleep mode.

    In facts, If the AP start earlier than ED, then system work is normal, ED can  send and receive message from AP.

    On the contrary, If the  ED earlier than AP, the SMPL_Init () of ED is not successful,system is wrong, ED can send message,but can not receive message from AP.

    Best regards

    watson

  • in reply to Leo Hendrawan
    Prodigy 180 points

    hi LEO,

        Our system is based on the AP and a number of EDs, we have use nv_obj_write_nwk_cfg () and save the connection information 'sPersistInfo' to the flash of cc1110.
    It is workable for "simple peer to peer" in this way . But for 'AP as Data Hub', the system will be unable to work. The BUG described as follows:
        Even if the AP and EDs are stored 'sPersistInfo', at the next power cycle,
    If the AP start earlier than ED, then system will work normally, ED can send and receive message from AP.
    On the contrary, If the ED start earlier than AP, the SMPL_Init () of ED will not be successful, 'sAPAddress' in RAM is "0x00,0x00,0x00,0x00", ED can send message,but can not receive any message from AP. we try to modify 'sAPAddress', 'sLinkToken', 'sJoinToken' in RAM of cc1110,but the system is still abnormal.
    (in fact, as you known,the funciton of nv_obj_write_nwk_cfg() is not stored sAPAddress', 'sLinkToken', 'sJoinToken' to the flash.)
         We hope that once our ED and AP have successfully JOIN and Link, we don’t need SMPL_Init () successful and re-Join and link again at the next power cycle whenever AP or ED starts earlier.
    In this case, in addition to storage 'sPersistInfo' at nv_obj_write_nwk_cfg(), what other information such as 'sAPAddress' do we need to store?

    Regards
    watson

  • in reply to Leo Hendrawan
    Prodigy 180 points

    Anybody here？