-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
changelog v1.1 #69
Comments
@filipswit did you consult moving the EEPROMs to separate I2C interface with software guys? |
no, but default EEPROM, IC5 is not moved. |
I believe there was some discussion on version naming convention and patch number (according to ..) was to be reserved only for compatible component replacements. Here I can see some issue fixes. If such discussion was not written (honestly, don't remember) maybe we should write down rules on that. |
yes, since it requires software changes, there must be new revision |
@gkasprow How does it require software changes? IO expander has different address / registry map? |
I2C EEPROM is connected in a different way |
Before EEPROM was connected to shared bus, now it has a dedicated FPGA pins. |
old-style regulators may not like 10uF at the output. I'd replace C376 with a 100nF capacitor and decouple it from LDOs 1uF caps with a few tens Ohm resistor. With a low ESR multi-uF load, it may oscillate. |
@filipswit there is yet another issue that needs correction |
just add a single 22Ohm (or similar already in the BOM) at the LDO output after the 100nF cap. |
yep, my bad |
OK, so you found better DS than me :) |
No need for series resistor then. |
@gkasprow could you please look at the changes one more time? |
@gkasprow @filipswit Can we assume v1.1 is reviewed? |
@gkasprow Do you think sinara-hw/Kasli#99 should be implemneted here? |
SOT-23 version of EEPROM is still not available |
please add note close to the I2C expanders that ASSY variant need to be updated. |
Ah, I see, IC5 is connected instead... |
yeep, it should be added. I've made issue to not forget about it in next revision #72. |
edit
The text was updated successfully, but these errors were encountered: