Read VI Frame Count register

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

system crash when we read the VI Frame Count register with command : sudo devmem2 0x0x15f11070.
According to https://docs.nvidia.com/drive/drive-os-5.2.3.0L/drive-os/index.html#page/DRIVE_OS_Linux_SDK_Development_Guide/NvMedia/nvmedia_debugging_csi_errors.html#wwpID0E0QB0HA , we can read it.

error log :

tegra-ubuntu login: [ 36.973772] bash[1220]: Switch did not repospond to MAC address 02-00-de-af-00-01
[ 36.974164] bash[1220]: Get firmware version will be attempted using 02-00-00-00-00-11
[ 47.097593] bash[1220]: Unable to get the current switch firmware version
[ 47.097971] bash[1220]: Please also check the ethernet interface provided.
[ 47.098934] bash[1220]: Current ethernet interface used is : eth0.200
[ 47.099279] bash[1220]: Try running with sudo if not already
[ 47.099709] bash[1220]: Could not get the current firware version.
[ 47.100179] bash[1220]: Updation failed
[ 47.100485] bash[1220]: ----------------------- Error log start ------------------------
[ 47.100956] bash[1220]: /lib/firmware/marvell_ethernet//tools/linux/prebuilt/MarvFlashImage -fv -iieth0.200 -da02-00-de-af-00-01 -dn17 -th10000
[ 47.101379] bash[1220]: Marvell 88Q5050 Image Download Tool v0.00.0014 (local build)
[ 47.102183] bash[1220]: Result = 0
[ 47.102593] bash[1220]: Start: 5616, current: 10006617, diff: 10001001, diff2: 10001
[ 47.102950] bash[1220]: Timeout 10000 elapsed, RX tries: 4854938
[ 47.103360] bash[1220]: TIMEOUT!
[ 47.103857] bash[1220]: Failed to Get the response for firmware version get command :9807: ReceiveGetFwResponse()returned error 9.
[ 47.104663] bash[1220]: GetFwVersion failed with error:9
[ 47.105017] bash[1220]: Image Download Tool exiting with result 2.
[ 47.105394] bash[1220]: /lib/firmware/marvell_ethernet//tools/linux/prebuilt/MarvFlashImage -fv -iieth0.200 -da02-00-00-00-00-11 -dn17 -th10000
[ 47.105775] bash[1220]: Marvell 88Q5050 Image Download Tool v0.00.0014 (local build)
[ 47.106187] bash[1220]: Result = 0
[ 47.106532] bash[1220]: Start: 4827, current: 10005828, diff: 10001001, diff2: 10001
[ 47.106877] bash[1220]: Timeout 10000 elapsed, RX tries: 5423365
[ 47.107272] bash[1220]: TIMEOUT!
[ 47.107634] bash[1220]: Failed to Get the response for firmware version get command :9807: ReceiveGetFwResponse()returned error 9.
[ 47.108085] bash[1220]: GetFwVersion failed with error:9
[ 47.108841] bash[1220]: Image Download Tool exiting with result 2.
[ 47.109200] bash[1220]: ----------------------- Error log end ------------------------
[ 47.110124] bash[1220]: Failed to update the Marvell switch firmware… Script exited with 1
???130624863|HV/c0: ???**************************************
???130626065|HV/c0: ???CPU:0, Error:CBBNOCAXI
???130626929|HV/c0: ??? Error Logger : 0
???130627667|HV/c0: ??? ErrLog0 : 0x80070400
???130628474|HV/c0: ??? Transaction Type : RD - Read, Incrementing
???130629640|HV/c0: ??? Error Code : SEC
???130630660|HV/c0: ??? Error Source : Initiator NIU or Firewall
???130637275|HV/c0: ??? Error Description : Security violation. Firewall error
???130645037|HV/c0: ??? Packet header Lock : 0
???130649976|HV/c0: ??? Packet header Len1 : 7
???130654916|HV/c0: ??? NOC protocol version : version >= 2.7
???130661178|HV/c0: ??? ErrLog1 : 0x352822
???130665765|HV/c0: ??? ErrLog2 : 0x0
???130669912|HV/c0: ??? RouteId : 0x352822
???130674586|HV/c0: ??? InitFlow : ccroc_p2ps/I/ccroc_p2ps
???130680672|HV/c0: ??? Targflow : host1x_p2pm/T/host1x_p2pm
???130686934|HV/c0: ??? TargSubRange : 20
???130691521|HV/c0: ??? SeqId : 0
???130695490|HV/c0: ??? ErrLog3 : 0x311470
???130700077|HV/c0: ??? ErrLog4 : 0x0
???130704225|HV/c0: ??? Address : 0x15f11470
???130709162|HV/c0: ??? ErrLog5 : 0x889f850
???130713837|HV/c0: ??? Non-Modify : 0x1
???130718337|HV/c0: ??? AXI ID : 0x11
???130722570|HV/c0: ??? Master ID : CCPLEX
???130727244|HV/c0: ??? Security Group(GRPSEC): 0x7e
???130732713|HV/c0: ??? Cache : 0x0 – Non-cacheable/Non-Bufferable)
???130739770|HV/c0: ??? Protection : 0x2 – Unprivileged, Non-Secure, Data Access
???130747884|HV/c0: ??? FALCONSEC : 0x0
???130752295|HV/c0: ??? Virtual Queuing Channel(VQC): 0x0
???130758205|HV/c0: ???**************************************
???130764300|HV/c0: ???CBB-ERR: Stopping guest 0 that owns the peripheral belonging to the address 0x15f11470.
???[ 129.763] Start VM0(Guest VM 0) to VM_STATE_SHUTDOWN
[ 129.884] End VM0(Guest VM 0) to VM_STATE_SHUTDOWN
???SMMU instance: 0x0
StreamID: 0x1b
Input Fault Address: 0x7ffffc6f80
Access Type: Read
Fault type: S2 CB
CB Index: 0x0
S2 CB belongs to VM: 0x0
Stage-2 CB fault. Killing VM: 0x0
???130942765|HV/c0: ???vpr base=8:70000000, size=80, ctrl=1, override:(a01a8340, fcee10c1, 1, 0)
???130944358|HV/c0: ???(255) csw_xusb_hostw: EMEM VPR violation
???130946589|HV/c0: ??? status = 0x0ff7404b; addr = 0xffffffff00
???130953028|HV/c0: ??? secure: yes, access-type: write
???SMMU instance: 0x1
StreamID: 0x1b
Input Fault Address: 0x7ffffa7080
Access Type: Read
Fault type: S2 CB
CB Index: 0x0
S2 CB belongs to VM: 0x0
Stage-2 CB fault. Killing VM: 0x0
??

[*] DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
[*] Linux
QNX
other

Hardware Platform
[*] NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.7.1.8928
[*] other

Host Machine Version
[*] native Ubuntu 18.04
other

2

Dear @zaiqdong,
Could you please confirm the DRIVE OS version as you have pointed to DRIVE OS 5.2.3 documentation. Besides that, Do you see any errors related to switch while tegra is booting. Could you share boot log?

4

My DRIVE OS version is 5.2.6, and according to https://docs.nvidia.com/drive/drive-os-5.2.6.0L/drive-os/index.html#page/DRIVE_OS_Linux_SDK_NGC_Development_Guide/NvMedia/nvmedia_debugging_csi_errors.html#wwpID0E0PB0HA.

boot log and error log upload as attach.
minicom.cap (186.1 KB)

5

Dear @zaiqdong,
It looks like the Switch errors are not related to the used command. Is it possible check re-flashing to see if switch related issue gets fixed?

6

Switch errors have nothing to do with read VI fream count. This error occurs every time the system starts. We get same error after re-flash . Any other suggestions？ thanks & brs.

7

Dear @zaiqdong,

Switch errors have nothing to do with read VI fream count

Thank you for clarification. Does the error occur in booting even in earlier release(DRIVE OS 5.2.0) (or) only after you updated to DRIVE OS 5.2.6 (or) or only since couple of days on DRIVE OS 5.2.6?

system crash when we read the VI Frame Count register

That means, it went into hang state and not accessible via minicom or it throws some error log?

8

I only used 5.2.6 and it always exists。

9

Guest OS linux be shoutdown.
log as :
End VM0(Guest VM 0) to VM_STATE_SHUTDOWN
???SMMU instance: 0x0
StreamID: 0x1b
Input Fault Address: 0x7ffffc6f80
Access Type: Read
Fault type: S2 CB
CB Index: 0x0
S2 CB belongs to VM: 0x0
Stage-2 CB fault. Killing VM: 0x0

10

We change the mac address of 88Q5050 and Switch errors disappear，So this problem has nothing to do with switch error.

The real reason is as follows and the vm0(linux) was shut down by hypervisior：

???78634836|HV/c0: ???**************************************
???78636001|HV/c0: ???CPU:0, Error:CBBNOCAXI
???78636798|HV/c0: ??? Error Logger : 0
???78637521|HV/c0: ??? ErrLog0 : 0x80070400
???78638312|HV/c0: ??? Transaction Type : RD - Read, Incrementing
???78639463|HV/c0: ??? Error Code : SEC
???78640209|HV/c0: ??? Error Source : Initiator NIU or Firewall
???78646631|HV/c0: ??? Error Description : Security violation. Firewall error
???78654304|HV/c0: ??? Packet header Lock : 0
???78659156|HV/c0: ??? Packet header Len1 : 7
???78664008|HV/c0: ??? NOC protocol version : version >= 2.7
???78670182|HV/c0: ??? ErrLog1 : 0x352822
???78674680|HV/c0: ??? ErrLog2 : 0x0
???78678737|HV/c0: ??? RouteId : 0x352822
???78683325|HV/c0: ??? InitFlow : ccroc_p2ps/I/ccroc_p2ps
???78689322|HV/c0: ??? Targflow : host1x_p2pm/T/host1x_p2pm
???78695497|HV/c0: ??? TargSubRange : 20
???78699995|HV/c0: ??? SeqId : 0
???78703877|HV/c0: ??? ErrLog3 : 0x311470
???78708375|HV/c0: ??? ErrLog4 : 0x0
???78712433|HV/c0: ??? Address : 0x15f11470
???78717283|HV/c0: ??? ErrLog5 : 0x889f850
???78721870|HV/c0: ??? Non-Modify : 0x1
???78726280|HV/c0: ??? AXI ID : 0x11
???78730426|HV/c0: ??? Master ID : CCPLEX
???78735013|HV/c0: ??? Security Group(GRPSEC): 0x7e
???78740393|HV/c0: ??? Cache : 0x0 – Non-cacheable/Non-Bufferable)
???78747362|HV/c0: ??? Protection : 0x2 – Unprivileged, Non-Secure, Data Access
???78755388|HV/c0: ??? FALCONSEC : 0x0
???78759710|HV/c0: ??? Virtual Queuing Channel(VQC): 0x0
???78765532|HV/c0: ???**************************************
???78771539|HV/c0: ???CBB-ERR: Stopping guest 0 that owns the peripheral belonging to the address 0x15f11470.
???[ 78.185] Start VM0(Guest VM 0) to VM_STATE_SHUTDOWN
[ 78.299] End VM0(Guest VM 0) to VM_STATE_SHUTDOWN
???SMMU instance: 0x0
StreamID: 0x1b
Input Fault Address: 0x7ffffc6700
Access Type: Read
Fault type: S2 CB
CB Index: 0x0
S2 CB belongs to VM: 0x0
Stage-2 CB fault. Killing VM: 0x0
???78942199|HV/c0: ???vpr base=8:70000000, size=80, ctrl=1, override:(a01a8340, fcee10c1, 1, 0)
???78943775|HV/c0: ???(255) csw_xusb_hostw: EMEM VPR violation
???78945868|HV/c0: ??? status = 0x0ff7404b; addr = 0xffffffff00
???78952218|HV/c0: ??? secure: yes, access-type: write
???SMMU instance: 0x1
StreamID: 0x1b
Input Fault Address: 0x7ffffc4000
Access Type: Read
Fault type: S2 CB
CB Index: 0x0
S2 CB belongs to VM: 0x0
Stage-2 CB fault. Killing VM: 0x0
??

11

Dear @zaiqdong,
The real reason is as follows and the vm0(linux) was shut down by hypervisior

Does that mean, after running the command it was shutdown or while booting?

12

shutdown when run sudo devmem2 0x15f11070

13

Dear @zaiqdong,
I could reproduce the issue. I am checking internally on this. May I know if it is blocking your development?

14

I want to debug camera by read VI Frame Count, but now I can not read it.

15

I have the same issue. Any tips for solution.

.

16

Dear @zaiqdong, @rockdee733
Just to clarifiy It is not possible to access VI registers on DRIVE OS 5.2.6.

@rockdee733, could you please use your business email before posting to get better support

18

Please refer to Nvmimg_cc CSI debugging.

19

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.