- What
about read-modify-write fields where writeable bits are in an unknown state
and should not be modified? (bad design practice)
-
What about a component
that has multiple bus interfaces that have different access/visibility into
the register set? Also, SUPERVISOR code could have different visibility
over USER code.
-
What about when
Marketing (phantom ware) or Applications (feature not supported) concerns
override the Design?
Best regards,
Alan
Attached are the
access definitions I used in the pilot and the presentational expectations for
each access type.
Here are a few
comments:
- When possible, if
something is read-only, I used a 4-character definition that explains the
write behavior. The same is true for write-only.
- No zero ("0")
characters are used, so they are not confused for "O"
- RU is used for
registers that are reserved for an unknown reason, where the read/write
behavior is not known/explained.
- I prefer "RORZ",
but there was some "ROZ" instances that our processing supports, but it will
be fixed and deprecated.
-seth
--------------------------------------------
seth park
information architect
Freescale Semiconductor,
Inc.
512.895.2463
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]