Dears,
We used WCT1013 in our wireless charging TX board, and now there are some problems.
1. When we power up the NXP evaluation board without the RX, there is a shiny green light indicating normal state. However, when we power up our TX board under the same conditions (using same TX coil), there is a constant red light which indicates there is TX_PRE_FOD_ERROR or TX_QFOD_ERROR according to the manual (refer to the attachment FOD.png).
2. We modified the software configuration to shield above errors, then our TX board can power on normally (a shiny green light). However, when we tried to connect RX board, only when the RX coil is very clear to the TX coils (about 1~2mm), the connection can be established. For NXP evaluation board, the spacing to establish connection is about 6mm (with same RX board and coils)
3. For our TX board, once the connection is established at 1~2mm coils spacing, even if the coils spacing is increased to about 5~6mm later, the connection can still maintain.
4. We have tried to implement calibration process according to the Run-Time Debugging User's Guide, but the board can't enter debug mode, as shown in the attachment Calibration.png.
Based on above problems, we need some technical support:
1. What's the possible causes of the FOD errors and large connection spacing? Hardware or software configuration?
2. How to solve the problem of calibration process? The board can not enter debug mode now.
3. Our hardware schematic design is the same as NXP evaluation board, but we guess the software in our board (offered by NXP) is different from the NXP evaluation board according to the test phenomenon. So could you please offer the software of NXP evaluation board? We want to eliminate the influence of hardware design. The hardware version of NXP evaluation board is shown in attachment EVB.jpg.
This problem appeared a few weeks ago, but we are unable to get timely and effective support from NXP FAE. We also have few technical references now. So, could you please provide some emergency technical support? Such as email or other timely communication. Our project development has been delayed, and we must at least make sure there is no hardware problem, so that we can start the design for our next version sample.
Thanks!
