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.

CC2640: Core Erratum 10734 Pairing Updates

Part Number: CC2640

We starting up BT qualification using WiPro as BQC.  We are using the CC2640 BLE chip (not a module).  From what I read the QDID is 82185 and I verified that we are using the latest BLE stack according to this link 

This question comes from WiPro to our company:

"If TI has a QDID including the PICS corresponding to Core Erratum 10734, then you no does not need to validate the tests."

So basically, if the test been performed by TI and we can prove it we don't need pay for an extra test.  

  • Got another reply form our BQC:

    As per Bluetooth SIG webpage, the Qualification Assessment Date date for QDID 82185 is 2016-06-22. How do we confirm that the fixes are assessed as this errata was published couple of months before only.

    Please find the response from Bluetooth SIG: “Either the chipset vender can perform a reassessment to bring the component the latest qualification requirements (TCRL 2018-1/2) or their customers qualifying new End Products will need to each provide test evidence for the corresponding test cases. We recommend reaching out to the vendor to reassess the component.”

    Is there a plan to do a reassessment of the QUID to include this erratum? 

    Thanks

    -Anders

  • Hi Anders,

    Please see the last post in this thread: e2e.ti.com/.../744159

    Following the guidelines provided by JXS should resolve the consistency check failures in BLS.

    Regards Fredrik
  • Fredrick,

    Thanks, I saw that and had that link in my original post.   In other words, TI does not have an updated report for this QDID.  

    Wipro is asking:

    please check with TI and share the test report corresponding to QDID 82185.

    Thanks

  • Hi Anders,

    We do not have an updated QDID, no. We have implemented the erratum in the listed SDKs though, and following the outlined procedure in the other E2E thread will allow you to complete your end product listing in Bluetooth Launch Studio without consistency check failures.

    Regards,
    Fredrik