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.
Part Number: TPS2546
Have you seen any functional issues from the device being in divider 2? If the device is still outputting the correct current, the phone may be able to recognize divider 2 but still output the desired current.
If you need to be in divider 1, you can use CTL1, CTL2, CTL3, and ILIM_SEL to force the device into DCP divider 1 as shown in the table below.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Emma Hoying:
The functional issue with the behavior is that the MFI certification lab flags the 2 second reset and mode switch as a failure with their automated test system (ATS).
Configuring the device for exclusive divider1 mode precludes the use of DCP_Shorted for non-Apple devices.
I am curious why 750mA was selected as a threshold for trying divider2 mode when the load is already less than the 1A current advertised by divider1 mode.
In reply to Alan R Olson:
The designer for this part is currently out of office until early November so I will not be able to get back to you on the reasoning behind 750 mA until then.
Also, the TPS2546 can support charging schemes tested during MFI compliance. However, the TPS2546 has not been tested or certified for MFI compliance so if you are seeing a failure during MFI compliance testing, it may be valid. The device can still properly support these charging schemes, though.
Thank you for following up with the chip designer. I hope to read their comments the first week in November.
The TPS2546 will first attempt to do Divider 1 which is the first generation of the proprietary charging. When current goes above the 750mA the TPS2546 will attempt to try Divider2 so see if the device connected support the higher current. If it is determined that the device supports divider2 it will remain in that state, if not it will go back to divider1.
This allows a device that supports divider2 to charge at the highest current possible and still allow devices supporting the first generation divider1 to charge at the rated current.
The reason VBUS is discharged is to adhere to the USB Spec and BC1.2 spec, where a device determines the attach through the presence of VBUS. VBUS is discharged to simulate the disconnect and restart the timing for each of the detection. In a BC1.2 only, Divider1, or Divider2 only charger, the VBUS will never toggle in a normal working condition since the advertisement does not change.
When you use the DCP auto feature it will have to cycle through all the modes but will have to remove/apply VBUS as it switches.
When running compliance for a specific mode you should set the control bits according to the test you want to run to not have the DCP conflict.
In reply to Jacob Ontiveros:
Thank you for this reply.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.