Skip to content

Conversation

@kiram9
Copy link
Member

@kiram9 kiram9 commented Dec 16, 2025

for fresh expansion bay modules that are unprogrammed, we need to turn on the power to program them if they are not preprogrammed with dummy values.

@kiram9 kiram9 requested a review from JohnAZoidberg December 16, 2025 11:45
@kiram9 kiram9 force-pushed the pr-fw16-enable-power-when-writing-eeprom branch from 0956338 to 71823ec Compare December 16, 2025 11:52
@JohnAZoidberg JohnAZoidberg force-pushed the pr-fw16-enable-power-when-writing-eeprom branch from 71823ec to 89d8129 Compare January 9, 2026 14:08
@JohnAZoidberg
Copy link
Member

Rebased on top of main

JohnAZoidberg and others added 2 commits January 9, 2026 22:23
Allow setting individual GPIOs.
You need to be careful because the definitions can change between each
platform and controlling some GPIOs can cause mainboard damaged if
controlled in correctly.

Co-Authored-by: Kieran Levin <[email protected]>
Signed-off-by: Daniel Schaefer <[email protected]>
For fresh expansion bay modules that are unprogrammed, we need to turn
on the power to program them if they are not preprogrammed with dummy
values.

Signed-off-by: Kieran Levin <[email protected]>
@JohnAZoidberg JohnAZoidberg force-pushed the pr-fw16-enable-power-when-writing-eeprom branch from 89d8129 to 541e279 Compare January 9, 2026 14:24
os_specific::sleep(100_000);
if let Err(err) = res {
println!(" Failed to write chunk: {:?}", err);
return Err(err);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make this not return but break the loop, and we return the error at the end.
Then the cleanup routine at the end to disable force power still runs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants