Skip to content
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

BCT can't open Eagle Stream's bsf #99

Closed
memristor2 opened this issue Jan 10, 2024 · 8 comments
Closed

BCT can't open Eagle Stream's bsf #99

memristor2 opened this issue Jan 10, 2024 · 8 comments

Comments

@memristor2
Copy link

Hello
I am trying to use the bct tool to patch the fsp.fd file. Unfortunately BCT isn't able to open the associated BSF file.
image.

@swong23
Copy link
Contributor

swong23 commented Jan 10, 2024

@memristor2
Copy link
Author

@swong23 Thank you.
I don't know if you have checked this yourself or not. But unfortunately the config Editor Tool doesn't load the parameters of Eagle Streams BSF file either

@meyfa
Copy link

meyfa commented Jan 12, 2024

It looks to me like the published file is incomplete / broken. It's many fewer lines than other published .bsf files (only 144 lines compared to many thousands). Also, it starts with a StructDef but no associated EndStruct.

@LeanSheng
Copy link

usually, you can directly configure the UPD parameters directly from BIOS like coreboot or Slim bootloader, so BCT tool or config editor tool comes secondary. it is because the tool only changes the 'default' settings of FSP, if BIOS reference code like coreboot overwrites the UPD settings, then the default setting will be ignored.

@memristor2
Copy link
Author

Fixed in #100

@paulmenzel
Copy link

The merge/pull request is still open, and I think it’s common practice to leave the corresponding issue open until the merge/pull request is accepted and merged/submitted. If you add a line

Resolves: #99

to the commit message of the commit fixing the issue, then GitHub is going to close the issue automatically, when the merge/pull request is merged/submitted.

@memristor2
Copy link
Author

@paulmenzel I simply did this to close it since it was not an issue for me anymore. But you're right Ill reopen it and let the contributers close it

@nate-desimone
Copy link
Contributor

Fixed in e07f875

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

No branches or pull requests

6 participants