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

LPC fixups #19

Open
wants to merge 11 commits into
base: master
Choose a base branch
from
Open

Conversation

madscientist159
Copy link

Fix potential HBBL hang
Add optional printf() support over serial
Fix FTBFS in various trace statements

madscientist159 and others added 11 commits April 6, 2020 17:09
Allow 16-bit LPC addresses in both read and write routines
…f to HBBL

HBBL tests for LPC attached firmware by executing a single read then checking
the OPB LPC error status register.  If any LPC operation failed during SBE
execution, even if the failure was harmless (e.g. write to nonexistent status
display device) HBBL will assume the error status applies to the initial
firmware test read.

Make sure the error status register is clear before handing off to HBBL.
SBE trace messages are not automatically enabled in this case due to PIBMEM size constraints
@@ -7,6 +7,7 @@
/* */
/* Contributors Listed Below - COPYRIGHT 2015,2018 */
/* [+] International Business Machines Corp. */
/* COPYRIGHT 2020 Raptor Engineering, LLC */
Copy link

Choose a reason for hiding this comment

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

Is this form of the copyright header right?

@@ -7,6 +7,7 @@
/* */
/* Contributors Listed Below - COPYRIGHT 2015,2018 */
/* [+] International Business Machines Corp. */
/* COPYRIGHT 2020 Raptor Engineering, LLC */
Copy link

Choose a reason for hiding this comment

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

Is this form of the copyright header right?

Copy link
Author

Choose a reason for hiding this comment

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

Probably not, actually. The whole header seems odd, it looks auto-generated but we don't have access to the tooling to regenerate it. If there's a preferred format I'll update.

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.

2 participants