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.

LMX9838 ... BDaddr for multiple devices appears to be the same .. ??

We are having a problem with the NSC LMX9838 module, where it is using the same BDaddr of 10:00:e8:00:00:00 across multiple modules. The top line of the NSC module shows a lot code of 2VT136AC . I do not believe the problem is the 2VT136AC lot code because we have that lot code from a different order that work correctly (so unique BDaddr). Also, we have no mechanism in our firmware to reprogram or erase the BDaddr. Some thoughts/questions:

1. Could the parts we received  be restock? Maybe another customer reprogrammed the BD address?

2. Could the parts not have been through all the programming steps at the factory?

3. AN-1699 section 7.3.2 error code 0x10 mentions that the module will change the BDaddr to the NSC address. We don’t see error code 0x10 but I am curious, what is the NSC address?

4. Is there some other method to get the module to ‘boot’ with the 10:00:e8:00:00:00 address?

We have about 500 boards built with 50+ of those boards assembled into units.  Those 50+ units all have the 10:00:e8:00:00:00 address.  We should have firmware that will let us rewrite the address done today.   Please send to us and allocate unique NSC/TI addresses.  It looks pretty definitive that we need at least 550 address to cover the first PO, I don’t know if the second PO has the same problem, if they do we will need 1100 addresses total.  Expedite as quickly as possible, we need the unique addresses for our QC starting today (it uses the BT radio), so that we can ship product on Friday.

  • Hi Rick,

    My name is Ryan Lin. I have been the applications engineer for the LMX9838 since 2013. It seems like we did not follow up on this topic and we deeply apologize for letting this fall through the crack.

    This is an known issue and we have delivered a PIA (product information advisory) to the distributors to resolve this BDAdress issue. Have you received such information from your distributor? Please let us know what your channel is and we can assist in correcting this.

    Please feel free to contact me at ryanlin@ti.com

    Ryan Lin

     

     

  • Hi Ryan, we seem to be encountering a similar problem with duplicate Bluetooth device addresses, but the PIA does not apply (the LSBs are not zeroed).  We have confirmation that a product sold to one of our customers back in September has the same address as one of the chips we currently have in-house.  Is this a known issue?

  • Hi!

    We may have observed this in the past. I just want to let you know both the 0's and duplicates problems are resolved before and all the current ones should be clean and good!

    As for the in-house pieces you have, please contact me directly at ryanlin@ti.com, and I can assist to get you into the process to obtain unique BDaddresses.

    Ryan Lin