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.

CC2642R: about use simplelink starter app to OAD for cc2642R

Part Number: CC2642R


Questions are as follows:
1. The chip cannot be automatically reset for the reset command sent by the Android APP, while the IOS can.
2. In the process of upgrading through OAD, if the chip is powered off and re-powered on again, the chip cannot operate normally, it can only be done after re-downloading the program through the burner.
3. After the chip is upgraded through OAD, the content previously written in the flash is gone.

  • Hey Simon,

    In your above questions are you referring to on-chip OAD or off-chip OAD?

    1. The chip cannot be automatically reset for the reset command sent by the Android APP, while the IOS can.

    This issue sounds related to this e2e post. I will investigate this there, please see that post for any follow ups.

    2. In the process of upgrading through OAD, if the chip is powered off and re-powered on again, the chip cannot operate normally, it can only be done after re-downloading the program through the burner.

    In the case of on-chip OAD, a failed OAD should result in BIM executing the persistent app upon restart. In the case of off-chip, a failed OAD should result in the internal flash image being executed, if that is corrupted, it will load the factory imaged stored in external flash. If all images are invalid there is a potential for the device to spinlock. Please see the "BIM for XXXX OAD" pages here (one for on-chip and another for off chip) of our User's Guide that goes over the flow of the BIM. Please ensure you are flashing the BIM project in addition to your application images as required for an OAD.

    3. After the chip is upgraded through OAD, the content previously written in the flash is gone.

    Depending on what OAD you perform (on or off chip), flash storage will be used to download the OAD image. This should be allocated and accounted for in your flash layout. If space is available, you can add certain areas of flash that are effectively untouched by the OAD process as "persistent" storage. Please see the OAD section of our User's Guide for more information.

  • Hi Ammar,

    Yes you are right that the two posts are related. Simon is my customer ^-^

    Please allow me to elaborate on the 2nd and 3rd question:

    2. In this case, on-chip OAD is used. Does that mean reverting to the factory image is not possible? I saw the "Reverting to a Factory Image" chapter in the user's guide, to my understanding it only applys to off-chip OAD, it that right?

    3. Do you have an example or guide for adding an area for the persistent storage?

    Thanks!

    BR,

    Shuyang

  • Hey Shuyang,

    In this case, on-chip OAD is used. Does that mean reverting to the factory image is not possible? I saw the "Reverting to a Factory Image" chapter in the user's guide, to my understanding it only applys to off-chip OAD, it that right?

    This section does apply to off-chip. It should still be possible to implement something like this for on-chip if that's required. In the on-chip OAD process, data is written to the OAD Reset Service that reboots the device into the persistent application. This means there is a way to revert to the persistent image. In on-chip OAD, the persistent image is the factory image. Hopefully this makes sense.

    Do you have an example or guide for adding an area for the persistent storage?

    I don't think we have an explicit guide for this. You would likely need to modify the BIM to make sure it doesn't erase the whole space allocated for the user image. I have not done this before myself, but this should be possible.

  • Hi Ammar, 

    Thanks for the reply. Any update on question 1?

    Best regards,

    Shuyang