When attempting a self boot, there is only one short burst of I2C activity. SigmaStudio version is 3.3. EEPROM can be written and read back.
Are there any other known issues that would keep self boot from working?
Are you attempting self-boot on one of our eval boards or your own prototype board?
My preliminary assessment is that the SigmaDSP is attempting to access the EEPROM - this would account for the short burst of activity - but is maybe not receiving an acknowledge from the EEPROM. If the EEPROM access request fails, then the selfboot operation will cease.
-Board is our own board.
-If I attach pdf of relevant page is it visible to public?
I see the self boot process is attempting 400KHz I2C transactions. Is there a way to change this default?
The default 400 kHz is "Fast Mode" in the I2C spec, which should work with almost any EEPROM you can find that is compatible with SigmaDSP. Is there any reason why you'd like to change it?
The clock is derived internally from the MCLK but I'm not sure if speeding up or slowing down MCLK would cause the I2C master clock to scale proportionally. In any case, that could cause issues with PLL locking, so I wouldn't recommend it. Is there any reason why you'd like to do this?
I will send you a private message regarding the schematic. If you post here, it will be visible, so if you'd like to avoid that you can email it to me directly.
I've got the DSP self-booting after changing the I2C bus pullup resistor values from 2.7K to 4.7K. Still don't know why either the EEPROM or the DSP at 2mA default drive would not be able to handle.
That's good to hear. Depending on the PCB trace length/width and the integrity of the connection between the programmer and the board, I guess the pull-ups might be too strong for the drivers to handle at some point.
Retrieving data ...