We use cookies to provide our visitors with an optimal site experience. View our privacy notice and cookie notice to learn more about how we use cookies and how to manage your settings. By proceeding on our website you consent to the use of cookies.
I have read through the various documentation I could find for the USB2514B, and from what I can determine, the chip can be configured in any of the following ways:
Use internal default configuration in combination with external strap options, which are physical pin configurations dictated by the board layout using pull-up and/or pull-down resistors.
Load configuration at start-up via I2C from external EEPROM device.
Load configuration at start-up via SMBus, typically from an external MCU.
This implies that, other than the default internal configuration option, the configuration values must be programmed into one of the external devices mentioned rather than into the USB2514B itself. Therefore, there could not be a “programming device” for the chip, as it does not have any internal non-volatile programmable memory to program. Configuration is loaded into RAM (volatile memory) at start-up via one of the methods mentioned above.
So, in your particular instance, if there is not external EEPROM or other SMBus device which configures the USB2514B at start-up, it would be using the default configuration that comes in the chip. If there is an external EEPROM or SMBus device on board, then that device would contain the configuration info.
Ok, Thanks David! That is a lot of great information. So what you are saying is that if it is not functioning properly now, that I should go through the circuitry and find the EEProm or other device.
Possibly. Keep in mind that just because the chip isn’t “destroyed”, visually, it doesn’t mean that it doesn’t have some internal damage. That’s always a possibility, and probably the best-case scenario, since a new replacement chip would have the same default configuration as the one on your board.
On the other hand, if it used an external EEPROM or some other device connecting via SMBus and that chip is damaged, then there’s likely no way to retrieve the configuration info from that device. This would make it very difficult to get your device working again.
David, I have already replaced the chip, but it did not respond as expected. That is what put me on the path of programming. I there is another USB controller IC near it and an eeprom for sure as well. I will check that out as well.