Based on user guide documentation of ‘Demonstration of Error Reporting Functionality’- DemoAppSwErr is used for demonstrating error reporting from Ccplex. I was able to report error using DemoAppSwErr.
Now, at FSI, Is there mechanism to receive the demonstrated error info and send to MCU via SPI for testing purpose. Can you please let us know how to demonstrate the error report end to end via SPI Is similar sample DemoApp available for FSI to MCU also? OR if you can suggest other possible way for verification it would be helpful.
root@7.0.3.0-0010-linux-nsr:/home/nvidia# cat FSI.txt
Time taken from Error Reporting to SEH: 3771264 microseconds
DemoApp: ErrCode-0x1234 ReptrId-0x8001 ErrAttr-0xabcd
EPS TimeStamp: 0xe0c83e46
With the tcu_muxer command,Error propagation is demonstrated,but I got following error. Can you please share the reference from guide for tcu_muxer utility? Invalid client name: CCPLE6,G=7
Invalid client config
On execution of error reporting demo I am setting error code as 0x22112222 at CCPLEX but, at FSI and MCU it was 0x2000000d. snippets attached.
Is there issue in communicating error info to FSI by CCPLEX and then sent to MCU? How to verify?Or, Is the mismatch of sent and received error due to invalid client at tcu_muxer?
Also, I understand the SPI configuration at MCU side is as per MCU_FOH Integration Steps — NVIDIA DriveOS 7.0.3 Linux SDK Developer Guide
How to verify/modify at FSI side, where to be checked at FSI?
I was able to get FSI console log with mentioned command.
But the observation remains the same. Whatever different error reporter ID, error codes I set from CCPLEX, at FSI and MCU it was always the same log: ErrorCode-0x2000000d ReporterId-0x8120 Error_Attribute-0x0 Timestamp-0x0. Where can I get the description for reporterId-0x8120 and corresponding ErrorCode?
Looks like error report is not reaching FSI. Is there any additional steps required for CCPLEX to be able to propagate the error to FSI by DemoAppSwErr?
I notice, if we use Error Reported ID above 0x8000, Issue is not noticed and I can see messages on FSI console as well.
The FSI files mentioned are not part of devzone release. Please contact your NVIDIA representative to sign necessary agreements, access and support on this.
Thank you @SivaRamaKrishnaNV for support!
I was able to see the same error at FSI and MCU as reported at CCPLEX.
Is this condition (error reporter>0x8000) only applicable with demonstrating error reporting by DemoAppSwErr or we need to consider when implementing any errors in general?
Can you share the reference in document for any such conditions to be considered during implementation?
Dear @divya.bilimoria ,
The SW Reported error ID are above 0x8000 . I could not find info on Reported Error ID values in devzone documentation. Let me check internally and update you on this.
With DemoAppSwErr, we simulate Error reporting functionality from SOC to MCU. Similarly, how can we verify error reporting from MCU to SOC? Is there a way to induce the error via MCU console or DemoApp if any?
Also, can we propagate only the fixed Error codes from MCU as listed in snippet below, OR, We can communicate any other Error codes from MCU ?
