cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mischlo
Observer
Observer
1,717 Views
Registered: ‎11-12-2020

CU timeout! DPU aborts while running demo

Hi,

we want to run yolov3 from the vitis-ai-library on the ZCU104 with a custom software platform with XRT 2020.2 and Vitis AI v1.3.

The XSA is based on the zcu104 base platform 2020.2

When we run the demo we get the following error:

 

 

 

 

 

./test_jpeg_yolov3 tf_yolov3_voc testpic.jpg 
WARNING: Logging before InitGoogleLogging() is written to STDERR
W0204 07:16:37.697132   267 xrt_cu.cpp:195] cu timeout! device_core_idx 0  handle=0x5596661b80 ENV_PARAM(XLNX_DPU_TIMEOUT) 10000 state 1 ERT_CMD_STATE_COMPLETED 4 ms 10010  bo=1 is_done 0 
I0204 07:16:37.697329   267 xrt_cu.cpp:105] Total: 10010421us   ToDriver: 65us  ToCU: 18446742567853857us       Complete: 0us   Done: 1515866050us
F0204 07:16:37.697402   267 dpu_control_xrt_edge.cpp:177] dpu timeout! core_idx = 0
 LSTART 0  LEND 0  CSTART 0  CEND 0  SSTART 0  SEND 0  MSTART 0  MEND 0  CYCLE_L 0  CYCLE_H 0 
*** Check failure stack trace: ***
Aborted

 

 

 

 

 

 

The output of dmesg:

 

 

 

 

 

[  297.850193] [drm] Pid 231 opened device
[  297.850721] [drm] Pid 231 closed device
[  297.852017] [drm] Pid 231 opened device
[  297.852513] [drm] Pid 231 closed device
[  299.773060] [drm] Pid 231 opened device
[  299.773573] [drm] Pid 231 closed device
[  299.774275] [drm] Pid 231 opened device
[  299.774767] [drm] Pid 231 closed device
[  299.775814] [drm] Pid 231 opened device
[  299.776531] [drm] Pid 231 closed device
[  299.880687] [drm] Pid 231 opened device
[  299.881213] [drm] Pid 231 closed device
[  299.881730] [drm] Pid 231 opened device
[  299.885310] [drm] get section DEBUG_IP_LAYOUT err: -22 
[  299.885318] [drm] get section AIE_METADATA err: -22 
[  299.886007] [drm] zocl_xclbin_read_axlf 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 ret: 0
[  299.890760] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 locked, ref=1
[  299.891796] [drm] No ERT scheduler on MPSoC, using KDS
[  299.893452] [drm] scheduler config ert(0)
[  299.893454] [drm]   cus(2)
[  299.893961] [drm]   slots(16)
[  299.894304] [drm]   num_cu_masks(1)
[  299.894680] [drm]   cu_shift(16)
[  299.895122] [drm]   cu_base(0x80000000)
[  299.895531] [drm]   polling(0)
[  299.896057] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 unlocked, ref=0
[  299.896804] [drm] Pid 231 opened device
[  299.898265] [drm] Pid 231 closed device
[  299.898878] [drm] Pid 231 opened device
[  299.899866] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 locked, ref=1
[  299.899901] [drm] Pid 231 opened device
[  299.901321] [drm] Pid 231 closed device
[  299.901828] [drm] Pid 231 opened device
[  299.902451] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 locked, ref=2
[  299.902799] [drm] Pid 231 opened device
[  299.904201] [drm] Pid 231 closed device
[  299.904707] [drm] Pid 231 opened device
[  299.905311] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 locked, ref=3
[  299.906219] [drm] Pid 231 opened device
[  299.907622] [drm] Pid 231 closed device
[  299.908127] [drm] Pid 231 opened device
[  299.908657] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 locked, ref=4
[  310.721321] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 unlocked, ref=0
[  310.722242] [drm] Pid 231 closed device
[  310.723666] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  311.228864] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  311.740907] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  312.252906] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  312.764906] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  313.276906] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  313.788923] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  314.300906] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  314.812906] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  315.324906] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  315.836935] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  316.348907] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  316.860869] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  317.372905] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  317.884863] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  318.396906] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  318.908867] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  319.420906] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  319.932907] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  320.444906] [drm] pid(231) waiting for outstanding 1 cmds to finish
[  320.956922] [drm:zocl_client_release [zocl]] *ERROR* Please investigate stale cmds
[  320.958667] [drm] addr 0x80010000, status 0x0
[  320.958669] [drm] addr 0x80000000, status 0x0
[  320.959223] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 unlocked, ref=0
[  320.959775] [drm] Pid 231 closed device
[  320.961209] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 unlocked, ref=0
[  320.961212] [drm] Pid 231 closed device
[  320.973714] [drm] bitstream 71bef9c3-5ae7-4a3b-9018-1b2934b800c6 unlocked, ref=0
[  320.973719] [drm] Pid 231 closed device
[  320.975290] [drm] Pid 231 closed device

 

 

 

 

 

xbutil query:

INFO: Found total 1 card(s), 1 are usable
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
System Configuration
OS name:        Linux
Release:        5.4.0
Version:        #1 SMP Wed Feb 3 14:11:09 CET 2021
Machine:        aarch64
Glibc:          2.31
Distribution:   Buildroot 2020.11.1
Now:            Thu Feb  4 07:20:31 2021 GMT
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XRT Information
Version:        2.8.0
Git Hash:       c2864bc70b33416d8315cd697f1d22814a13c5aa
Git Branch:     add-xrt
Build Date:     2021-02-03 14:14:29
ZOCL:           2.8.0,c2864bc70b33416d8315cd697f1d22814a13c5aa
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Shell                           FPGA                            IDCode
xilinx_zcu104_base_202020_1     N/A                             N/A
Vendor          Device          SubDevice       SubVendor       
0x10ee          N/A             N/A             N/A             
DDR size        DDR count       Clock0          Clock1          Clock2          
4 GB            1               100             0               0               
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Memory Status
     Tag         Type        Temp(C)  Size    Mem Usage       BO count
[ 0] HPC0        MEM_DRAM             2 GB    12288 Byte      3       
[ 1] HP3         MEM_DRAM             2 GB    0 Byte          0       
[ 2] HPC1        **UNUSED**           0 Byte  0 Byte          0       
[ 3] HP0         MEM_DRAM             2 GB    0 Byte          0       
[ 4] HP1         MEM_DRAM             2 GB    0 Byte          0       
[ 5] HP2         MEM_DRAM             2 GB    0 Byte          0       
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Streams
     Tag         Flow ID  Route ID Status   Total (B/#)     Pending (B/#)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Xclbin UUID
71bef9c3-5ae7-4a3b-9018-1b2934b800c6
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Compute Unit Status
CU[ 1]: DPUCZDX8G:DPUCZDX8G_1           @0x80000000        (--)
CU[ 0]: DPUCZDX8G:DPUCZDX8G_2           @0x80010000        (--)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
INFO: xbutil query succeeded.

We integrated the DPU with DPU-TRD Vitis flow and recompiled the model.

The vivado block design and dpu.xclbin are attached in case they are helpful.

We are looking forward for a solution for this error.

 

Regards

Michael

 

 

 

Tags (1)
0 Kudos
11 Replies
dvukadin
Participant
Participant
436 Views
Registered: ‎07-19-2018

Hi,

I also have a similar problem when I try to run demo resnet50 model on custom ZCU104 platform with Vitis 1.3. The custom platform was built using command line flow "make KERNEL=DPU DEVICE=ZCU104". We tested with RAM_USAGE_LOW and RAM_USAGE_HIGH, but nothing helped.

prj_config:

[clock]

# freqHz=225000000:DPUCZDX8G_1.aclk
# freqHz=450000000:DPUCZDX8G_1.ap_clk_2

id=1:DPUCZDX8G_1.aclk
id=2:DPUCZDX8G_1.ap_clk_2

[connectivity]

sp=DPUCZDX8G_1.M_AXI_GP0:HPC0
sp=DPUCZDX8G_1.M_AXI_HP0:HP0
sp=DPUCZDX8G_1.M_AXI_HP2:HP1

 

When I run: "$ ./demo_classification /usr/share/vitis_ai_library/models/resnet50/resnet50.xmodel resnet_50_0 image_example.jpg", I get the error:

"W0408 10:53:21.426137 1170 xrt_cu.cpp:195] cu timeout! device_core_idx 0 handle=0x
aaaaefa87270 ENV_PARAM(XLNX_DPU_TIMEOUT) 10000 state 1 ERT_CMD_STATE_COMPLETED 4 ms
10010 bo=1 is_done 0
I0408 10:53:21.426287 1170 xrt_cu.cpp:105] Total: 10010213us ToDriver: 74us ToCU
: 18446738372378995us Complete: 0us Done: 5711340695us
F0408 10:53:21.426327 1170 dpu_control_xrt_edge.cpp:177] dpu timeout! core_idx = 0
LSTART 0 LEND 0 CSTART 0 CEND 0 SSTART 0 SEND 0 MSTART 0 MEND 0 CYCLE_L 0
CYCLE_H 0"

 

Please find attached full output.

Thanks!

Regards,

dvukadin

 

Tags (3)
0 Kudos
afantina
Contributor
Contributor
409 Views
Registered: ‎04-04-2019

Any update? We have the same issue!

Br,

afantina

0 Kudos
jheaton
Xilinx Employee
Xilinx Employee
383 Views
Registered: ‎03-21-2008

@dvukadin,

A general comment here on RAM_USAGE_LOW vs HIGH.
Xmodels generated for the ZCU104 from the VIA-1.3 Examples are for compiled for RAM_USAGE_LOW.
If you are using RAM_USAGE_HIGH, then you will need to recompile the xmodel in the VAI compiler using the arch.json file from your Vitis project.
When building the DPU_TRD you will probably want to change the dpu_conf.vh file to use RAM_USAGE_LOW, this way you can use the VAI-1.3 ZCU104 xmodels  as is.

0 Kudos
dvukadin
Participant
Participant
356 Views
Registered: ‎07-19-2018

@jheaton 

thanks for the clarification. We tried VAI-1.3 ZCU104 xmodels as is with RAM_USAGE_LOW, but the same error appeared.

$ xbutil dump returns this:

[  147.839192] [drm] Pid 898 opened device
[  147.843189] [drm] Pid 898 closed device
[  147.847282] [drm] Pid 898 opened device
{
    "version": "1.1.0",
    "system": {
        "sysname": "Linu[  147.852061] [drm] Pid 898 closed device
x",
        "release": "5.4.0-xilinx-v2020.2",
        "version": "#1 SMP Wed Apr 7 09:31:10 UTC 2021",
        "machine": "aarch64",
        "glibc": "2.30",
        "now": "Fri Apr  9 09:24:45 2021 GMT"
    },
    "runtime": {
        "build": {
            "version": "2.8.0",
            "hash": "f19a872233fbfe2eb933f25fa3d9a780ced774e5",
            "date": "2020-11-15 11:07:38",
            "branch": "2020.2",
            "zocl": "2.8.0,f19a872233fbfe2eb933f25fa3d9a780ced774e5"
        }
    },
    "board": {
        "info": {
            "dsa_name": "edge",
            "vendor": "4334",
            "device": "65535",
            "subdevice": "65535",
            "subvendor": "65535",
            "xmcversion": "0",
            "ddr_size": "4294967296",
            "ddr_count": "1",
            "clock0": "100",
            "clock1": "0",
            "clock2": "0"
        },
        "xclbin": {
            "uuid": "(null)"
        }
    }
}

Is everything okay? Maybe "clock1" and "clock2" must have some values?

Regards,

dvukadin

0 Kudos
jheaton
Xilinx Employee
Xilinx Employee
340 Views
Registered: ‎03-21-2008

 The clocks look okay. The xbutil dump  matches what I see for the DPU_TRD.

I built the DPU_TRD using the zcu104 base platform and the ZynqMP common image from: https://www.xilinx.com/support/download/index.html/content/xilinx/en/downloadNav/embedded-platforms.html.

After you install Vart, and run show_dpu, do you see the following:

Capture.PNG

 

0 Kudos
jheaton
Xilinx Employee
Xilinx Employee
324 Views
Registered: ‎03-21-2008

0 Kudos
dvukadin
Participant
Participant
242 Views
Registered: ‎07-19-2018

Thank you for help.

I also managed to run that DPU_TRD using ZCU104 base_platform and the ZynqMP common image.

But when I try to implement 1xDPU in our custom platform and run "$ show_dpu", I get:

[  220.870565] [drm] Pid 835 opened device
[  220.874444] [drm] Pid 835 closed device
[  220.878395] [drm] Pid 835 opened device
[  220.882262] [drm] Pid 835 closed device
[  220.886198] [drm] Pid 835 opened device
[  220.890060] [drm] Pid 835 closed device
[  220.894042] [drm] Pid 835 opened device
[  220.897907] [drm] Pid 835 closed device
[  220.901924] [drm] Pid 835 opened device
[  220.905856] [drm] Pid 835 closed device
[  220.910643] [drm] Pid 835 opened device
[  220.914509] [drm] Pid 835 closed device
[  220.918379] [drm] Pid 835 opened device
[  220.924692] [drm] zocl_xclbin_read_axlf The XCLBIN already loaded
[  220.924701] [drm] zocl_xclbin_read_axlf 2e9ef218-bf0d-4c72-8647-12588cbfb250 ret: 0
[  220.941932] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 locked, ref=1
[  220.949189] [drm] Reconfiguration not supported
[  220.953749] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 unlocked, ref=0
[  220.961315] [drm] Pid 835 opened device
[  220.965181] [drm] Pid 835 closed device
[  220.969105] [drm] Pid 835 opened device
[  220.973130] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 locked, ref=1
[  220.980385] [drm] Pid 835 opened device
[  220.984238] [drm] Pid 835 closed device
[  220.988098] [drm] Pid 835 opened device
[  220.992032] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 locked, ref=2
[  220.999902] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 unlocked, ref=1

device_core_id=0 device= 0 core = 0 fingerprint = 0x0 batch = 1 full_cu_name=DPUCZDX8G:DPUCZDX8G_1

[  221.012796] [drm] Pid 835 closed device
[  221.021415] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 unlocked, ref=0
[  221.021417] [drm] Pid 835 closed device
[  221.032668] [drm] Pid 835 closed device

 

I see "fingerprint = 0x0" and many "drm" lines. Is this okay?

Regards,

dvukadin

0 Kudos
mischlo
Observer
Observer
219 Views
Registered: ‎11-12-2020

Hi together,

the problem was in our case, that we tried to load the DPU by U-Boot. After some checks we found out, that the DPU was already loaded by FSBL. Therefore we corrupted something due to this issue.

Although I don't think that somebody else has this specific problem, I wanted to share our solution.

If you build a custom Image try to understand exactly how the example platform provided by Xilinx is structured.

0 Kudos
jheaton
Xilinx Employee
Xilinx Employee
191 Views
Registered: ‎03-21-2008

@dvukadin,

Its okay to see more lines, you will those lines if  you run from a serial terminal instead of using an ssh terminal.

The fingerprint should not be 0, something is going wrong here.

After a reboot, here is what I see for a 1 DPU device built using the DPU_TRD using the prj_config_1dpu config script.


[ 157.895928] [drm] Pid 1302 opened device
[ 157.899887] [drm] Pid 1302 closed device
[ 157.903918] [drm] Pid 1302 opened device
[ 157.907856] [drm] Pid 1302 closed device
[ 157.911855] [drm] Pid 1302 opened device
[ 157.915788] [drm] Pid 1302 closed device
[ 157.919715] [drm] Pid 1302 opened device
[ 157.923652] [drm] Pid 1302 closed device
[ 157.946396] [drm] Pid 1302 opened device
[ 157.950447] [drm] Pid 1302 closed device
[ 158.433636] [drm] Pid 1302 opened device
[ 158.437592] [drm] Pid 1302 closed device
[ 158.441539] [drm] Pid 1302 opened device
[ 158.469752] [drm] get section DEBUG_IP_LAYOUT err: -22
[ 158.469767] [drm] get section AIE_METADATA err: -22
[ 158.475015] [drm] zocl_xclbin_read_axlf 42aa01f1-f855-46ba-b0e1-d76396e41fd5 ret: 0
[ 158.483441] [drm] bitstream 42aa01f1-f855-46ba-b0e1-d76396e41fd5 locked, ref=1
[ 158.491114] [drm] No ERT scheduler on MPSoC, using KDS
[ 158.503516] [drm] scheduler config ert(0)
[ 158.503517] [drm] cus(1)
[ 158.507521] [drm] slots(16)
[ 158.510211] [drm] num_cu_masks(1)
[ 158.513168] [drm] cu_shift(16)
[ 158.516648] [drm] cu_base(0x80000000)
[ 158.519869] [drm] polling(0)
[ 158.523722] [drm] bitstream 42aa01f1-f855-46ba-b0e1-d76396e41fd5 unlocked, ref=0
[ 158.526918] [drm] Pid 1302 opened device
[ 158.538228] [drm] Pid 1302 closed device
[ 158.542234] [drm] Pid 1302 opened device
[ 158.546361] [drm] bitstream 42aa01f1-f855-46ba-b0e1-d76396e41fd5 locked, ref=1
[ 158.546389] [drm] Pid 1302 opened device
[ 158.557521] [drm] Pid 1302 closed device
[ 158.561459] [drm] Pid 1302 opened device
device_core_id=0 device= 0 core = 0 fingerprint = 0x1000020f60144[ 158.565448] [drm] bitstream 42aa01f1-f855-46ba-b0e1-d76396e41fd5 locked, ref=2
07 batch = 1 full_cu_name=DPUCZDX8G:DPUCZDX8G_1

What do you see for the cu information when you run after a reboot?

 

0 Kudos
dvukadin
Participant
Participant
163 Views
Registered: ‎07-19-2018

@jheaton 

Here is the cu information after reboot:

 

[   63.564517] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.568527] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.572558] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.576484] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.580608] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.584526] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.588472] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.592398] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.602791] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.606839] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.627098] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.631027] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.634993] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.648270] [drm] get section DEBUG_IP_LAYOUT err: -22                                                                                                                                                  
[   63.648276] [drm] get section AIE_METADATA err: -22                                                                                                                                                     
[   63.653578] [drm] zocl_xclbin_read_axlf 2e9ef218-bf0d-4c72-8647-12588cbfb250 ret: 0                                                                                                                     
[   63.669731] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 locked, ref=1                                                                                                                          
[   63.676995] [drm] No ERT scheduler on MPSoC, using KDS                                                                                                                                                  
[   63.682202] [drm] scheduler config ert(0)                                                                                                                                                               
[   63.682203] [drm]   cus(1)                                                                                                                                                                              
[   63.686212] [drm]   slots(16)                                                                                                                                                                           
[   63.688910] [drm]   num_cu_masks(1)                                                                                                                                                                     
[   63.691869] [drm]   cu_shift(16)                                                                                                                                                                        
[   63.695349] [drm]   cu_base(0x80010000)                                                                                                                                                                 
[   63.698563] [drm]   polling(0)                                                                                                                                                                          
[   63.705480] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 unlocked, ref=0                                                                                                                        
[   63.713067] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.716931] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.720858] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.724925] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 locked, ref=1                                                                                                                          
[   63.732176] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.736032] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.739892] [drm] Pid 833 opened device                                                                                                                                                                 
[   63.743833] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 locked, ref=2                                                                                                                          
device_core_id=0 device= 0 core = 0 fingerprint = 0x0 batch = 1 f[   63.751708] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 unlocked, ref=1                                                       
ull_cu_name=DPUCZDX8G:DPUCZDX8G_1                                                                                                                                                                          
                                                                                                                                                                                                           
[   63.764611] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.778965] [drm] bitstream 2e9ef218-bf0d-4c72-8647-12588cbfb250 unlocked, ref=0                                                                                                                        
[   63.778967] [drm] Pid 833 closed device                                                                                                                                                                 
[   63.790197] [drm] Pid 833 closed device

 

 

Please also find attached linux booting output.

 

Regards,

dvukadin

 

 

0 Kudos
jheaton
Xilinx Employee
Xilinx Employee
141 Views
Registered: ‎03-21-2008

@dvukadin ,

The fact that  the finger print is 0, means something is broken.

What's different between the platform you used and and the vitis base zcu104 platform?

When you built the hw for the 1 DPU design, did you use the prj_config_1dpu config script, what other changes did you make.

Are you using the Linux common image, or did you build the linux kernel. If you built your own kernel maybe start with the common image to see if you can get that to work with 1 dpu.

Did Vivado meet timing when you build the hw in Vitis link?

Are you running the script zynqmp_dpu_optimize.sh before running models (see issue 5.5.3 onhttps://github.com/Xilinx/Vitis-AI/blob/master/dsa/DPU-TRD/prj/Vitis/README.md#fine-tune). 

0 Kudos