transport_dbg and TLM_IGNORE_COMMAND

Jerome, All,

Let's see if we can deal with the easier issues.

Your original 4th point was about the value returned from transport_dbg for TLM_IGNORE_COMMAND. My answer was that an application is already free to return whatever value it likes without breaking the base protocol, although I would agree that is a matter of interpretation, and the LRM wording could be made more explicit.

In other words, TLM_IGNORE_COMMAND says that the target does not perform a BP read or write, but is free to do something else. The value returned from transport_dbg is tightly defined for read or write, but if the application is executing an extended command, the target is free to choose the return value.

Does that meet your requirement? Is everyone else okay with that?

Thanks,

John A

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.