Skip to content

Define more errors in the Memory Configuration Standard? #169

@bobjacobsen

Description

@bobjacobsen

On Nov 30, 2024, at 10:47 PM, Jim Kueneman jimkueneman@yahoo.com wrote:

What is the correct action if a read/write command has a value larger than 64?

Clip the value to 64?
Return an Error? If so what Error? If so that should be added to the list of error return in the Memory Config spec.

That should pro probably be defined as a type of permanent error:

Section 4.3 of the Memory Configuration Standard mentions a few other ones, so it could be added there as e.g. the 0x0004 case.

C.f section 3.5.5 of the Message Standard, which defines the upper bits as 0x1080.

Are there other errors that could be defined?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions