Tool/software:
I am working on a developing an in production programming device to dump setting onto a custom PCB with the BQ4050.
I am having a lot issues with getting the BQ4050 to respond as I expect, and have currently gotten to a point with my two prototypes. Where the boards are now not responding to even the address call.
A couple of things I currently have the test packs and the host module scoped up and I am watching the communication lines on my oscilloscope. All the hardware and signaling seems to be intact from a signal integrity stand point. I currently have the clock running at 10Khz and the data looks clean and it is making it to the chip.
I feel fairly confident that my problems are coming from either not sending packets in the right order or missing some sort of end packet. or some how sending a byte that locks the device. So basically something in my host firmware that is not interfacing with the bq4050 correctly.
For this application, I think the solution should go down the path of automatically setting the chip to the correct mode by default in my procedure so that setting can always be dumped. This way it simplifies the manufacturing process where my lower level guys do not have to try and worry about the status of chip before they try program the production settings.
Do you have a procedure for which registers in which order to write to make sure that the chip is accessible. Are there certain commands that need a check sum? or and exit command?
