• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 307 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.

MSP432P4011: extending oad_simple_peripheral

Laurent van Poppelen69
Expert 1020 points
Part Number: MSP432P4011


Hi, we wrote software based on the oad_smple_peripheral sdk example connected to a CC2640R2 as network processor(np). It al works fine but instead of updating the ble image(cc2640r2) and the oad_simple_peripheral we also want to update two other processors in the system. Since we extended the functionality with additional BLE characteristics and other functionality we first set a charcteristic bit which holds all other tasks and then we use SDK EXPLORER to OAD. This works ok! 

Our question is:

As the sample uses /* Image types */
#define FL_OAD_IMG_TYPE_APP 1
#define FL_OAD_IMG_TYPE_STACK 2
#define FL_OAD_IMG_TYPE_NP 3

could we just extend this with f.i.:

#define FL_OAD_IMG_TYPE_AP2
#define FL_OAD_IMG_TYPE_AP3

and adapt the relevant functions to achieve this?

regards, Laurent

  • 0
    TI__Guru** 101460 points

    Hi Laurent,

    Give me a day or two to identify an expert that could comment on this one.

    Please bear with me.

    Best regards,

  • 0
    TI__Mastermind 25045 points

    Hi Laurent,

      This should be fine. Please let us know if you run into any issues.

        Best regards,

         David

  • 0
    Expert 1020 points

    Hi, thanks for reply. Our point is that the "oad_firmware_update_EXP432P4111_tirtos_ccs" example does not use the 'imagetool' but also does not store this metadata somewhere in flash! So our guess is that the "SimpleLink SDK Explorer" android app looks if its a "txt" or "hex" extension and than provides this FL_OAD_IMG_TYPE_XXX. It does receive it from mq_receive(hOadRec, (void*) &oadWriteEvt,..) and then saves it! So, something else provided it! Our guess for this example is the 'SimpleLink SDK Explorer"(Android app) provides it! Can we switch then to using the 'imagetool'?


    Laurent