I am testing this eval kit with the EVAL-CN0581-EBZ (where sink parameters - voltage, current) are selected via a series of dip switches. https://wiki.analog.com/resources/eval/user-guides/circuits-from-the-lab/cn0581 . Actual load needs to be applied separately. Under the design constraints, I can only require a fraction of the power (15W) which your kit is capable of: 5V @ 3A, 9V @ 1.7A, 12V @ 1.3A, and 15V @ 1A.
Here are some questions regarding this and the procedure in general:
-
So what I am noticing is that if the sink device advertises it needs more current than the source device can support, the source device sources no current and defaults to 5V. Is this expected behavior?
-
If the sink device advertises a particular voltage and current, and if something goes wrong with the sink device (e.g., a short?) so that more current is consumed, there are no safeties built in and I can sink more current than the source device agrees to. In other words, the source device has no built in protections if the sink current is greater than the source should provide. Is that correct?
-
Using Virtual Bench Pro 4.0. I am noticing one set of registers which are generally accessible: Global, BuckBoost, PDO, VBATT, OTW and Power Share but these don’t appear to be all the registers. (for example, I see no register referencing current sense resistor value. ) However, if I hit the Export Button, a new set of registers comes up which includes, among others, the register in the example I just cited. What is the purpose of having these register setting in different places, rather than having them all accessible on the main page?
-
When I import ATE files from the the set that I just exported, the I2C address gets set to 0x00, even though the I2C address register clearly states 0x61, making the file unusable. Why and how do you get around this?
-
What is the difference between simply saving the file and exporting and then importing? It seems like you see more register settings on the latter, but the main PDOs are retained when you simply do a save and then open, and again, in #4 above, there seems to be an issue with importing previously exported file.
-
In terms of programming voltage, it appeared to me once that the unit was unable to program - volatile memory - at 12V but that was probably just a fluke, because now I can see the unit programming at 10.8V (which is our systems minimum). Please verify that this is OK and will not have any issues. Again, I would rather have these chips be pre-flashed, but in case they can’t be, I want to know if any accommodations need to be made in the circuitry. Is there a difference in voltage requirement writing to volatile vs non-volatile memory?
-
While I would prefer to have these ICs pre-programmed, in the case I need to program ram every time the unit powers up, is there a link to a document available which describes this process and the protocol for programming registers on your IC?
-
And lastly, if MPS were to flash these chips for us, would they be provided with the exported file or simply with the saved register file (.spec). If it is the former, the issue that was previously discussed needs to be addressed.
Thanks and sorry for all the questions.