Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vitis Platform Creation Tutorial for ZCU104: Emulation Does Not Work in u-boot #99

Closed
Hamptonjc opened this issue Aug 31, 2021 · 7 comments
Assignees
Labels
PFM Platform related issues

Comments

@Hamptonjc
Copy link

Following: https://github.com/Xilinx/Vitis-Tutorials/tree/2020.2/Vitis_Platform_Creation/Introduction/02-Edge-AI-ZCU104#step-by-step-tutorial

During step 4, test 2 "Run Vector Addition Application", when running HW-emulation I get the following in the emulation console of the Vitis IDE:


Starting QEMU
 - Press <Ctrl-a h> for help 
Waiting for QEMU to start. qemu_port 8064
Qemu_pids 4450 4451
qemu-system-aarch64: -chardev socket,path=./qemu-rport-_pmu@0,server,id=pmu-apu-rp: info: QEMU waiting for connection on: disconnected:unix:./qemu-rport-_pmu@0,server

QEMU started. qemu_pid=4450.
Waiting for PMU to start. Qemu_pids 4454 4455
qemu-system-aarch64: -chardev socket,id=pl-rp,host=127.0.0.1,port=7724,server: info: QEMU waiting for connection on: disconnected:tcp:127.0.0.1:7724,server

PMC started. pmc_pid=4454
Starting PL simulation.Generating PLLauncher commandline
running PLL Launcher
qemu-system-aarch64: warning: hub 0 is not connected to host network

PMU Firmware 2020.2	Aug 31 2021   17:24:15
PMU_ROM Version: xpbr-v8.1.0-0
NOTICE:  ATF running on XCZUUNKN/QEMU v4/RTL0.0 at 0xfffea000
NOTICE:  BL31: v2.2(release):xlnx_rebase_v2.2_2020.3
NOTICE:  BL31: Built : 17:22:19, Aug 31 2021


U-Boot 2020.01 (Aug 31 2021 - 17:23:30 +0000)

Model: ZynqMP ZCU104 RevC
Board: Xilinx ZynqMP
DRAM:  2 GiB
PMUFW:	v1.1
EL Level:	EL2
Chip ID:	unknown
NAND:  0 MiB
MMC:   mmc@ff170000: 0
In:    serial@ff000000
Out:   serial@ff000000
Err:   serial@ff000000
Bootmode: JTAG_MODE
Reset reason:	
Net:   
ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 12, interface rgmii-id

Warning: ethernet@ff0e0000 using MAC address from DT
eth0: ethernet@ff0e0000
Hit any key to stop autoboot:  2 ��� 1 ��� 0 
JTAG: Trying to boot script at 0x20000000
## Executing script at 20000000
Wrong image format for "source" command
JTAG: SCRIPT FAILED: continuing...
starting USB...
Bus dwc3@fe200000: this is not a DesignWare USB3 DRD Core
failed to initialize core
Port not available.
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (1 ms)
*** Warning: no boot file name; using '0A00020F.img'
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename '0A00020F.img'.
Load address: 0x8000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-00-0a-35-00-22-01
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/01-00-0a-35-00-22-01'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A00020F
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00020F'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A00020
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00020'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A0002
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A0002'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A000
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A000'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A00
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A0
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A0'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-zynqmp-zynqmp
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm-zynqmp-zynqmp'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-zynqmp
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm-zynqmp'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...

Note: I am using branch 2020.2, matching my Xilinx tool versions.

Any ideas?

@Premduth
Copy link

@imrickysu can you take a look?

@imrickysu
Copy link
Contributor

@Hamptonjc This error behavior looks very like the u-boot can't find boot.scr.
Please make sure you put boot.scr into image directory when Preparing Files for Platform Packaging (step 6).

@imrickysu imrickysu changed the title Vitis Platform Creation Tutorial for ZCU104: Emulation Does Not Work Vitis Platform Creation Tutorial for ZCU104: Emulation Does Not Work in u-boot Sep 1, 2021
@Hamptonjc
Copy link
Author

@imrickysu I can confirm boot.scr is in the image directory:

image

@Hamptonjc
Copy link
Author

The full read out from the emulation console:

Required emulation files like qemu_args exists


Starting QEMU
 - Press <Ctrl-a h> for help 
Waiting for QEMU to start. qemu_port 8118
Qemu_pids 20769 20770
qemu-system-aarch64: -chardev socket,path=./qemu-rport-_pmu@0,server,id=pmu-apu-rp: info: QEMU waiting for connection on: disconnected:unix:./qemu-rport-_pmu@0,server

QEMU started. qemu_pid=20769.
Waiting for PMU to start. Qemu_pids 20773 20774
PMC started. pmc_pid=20773
qemu-system-aarch64: -chardev socket,id=pl-rp,host=127.0.0.1,port=8876,server: info: QEMU waiting for connection on: disconnected:tcp:127.0.0.1:8876,server

Simulation Started. pl_pid=20779
qemu-system-aarch64: warning: hub 0 is not connected to host network

PMU Firmware 2020.2	Aug 31 2021   17:24:15
PMU_ROM Version: xpbr-v8.1.0-0
NOTICE:  ATF running on XCZUUNKN/QEMU v4/RTL0.0 at 0xfffea000
NOTICE:  BL31: v2.2(release):xlnx_rebase_v2.2_2020.3
NOTICE:  BL31: Built : 17:22:19, Aug 31 2021


U-Boot 2020.01 (Aug 31 2021 - 17:23:30 +0000)

Model: ZynqMP ZCU104 RevC
Board: Xilinx ZynqMP
DRAM:  2 GiB
PMUFW:	v1.1
EL Level:	EL2
Chip ID:	unknown
NAND:  0 MiB
MMC:   mmc@ff170000: 0
In:    serial@ff000000
Out:   serial@ff000000
Err:   serial@ff000000
Bootmode: JTAG_MODE
Reset reason:	
Net:   
ZYNQ GEM: ff0e0000, mdio bus ff0e0000, phyaddr 12, interface rgmii-id

Warning: ethernet@ff0e0000 using MAC address from DT
eth0: ethernet@ff0e0000
Hit any key to stop autoboot:  2 ��� 1 ��� 0 
JTAG: Trying to boot script at 0x20000000
## Executing script at 20000000
Wrong image format for "source" command
JTAG: SCRIPT FAILED: continuing...
starting USB...
Bus dwc3@fe200000: this is not a DesignWare USB3 DRD Core
failed to initialize core
Port not available.
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (4 ms)
*** Warning: no boot file name; using '0A00020F.img'
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename '0A00020F.img'.
Load address: 0x8000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-00-0a-35-00-22-01
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/01-00-0a-35-00-22-01'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A00020F
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00020F'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A00020
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00020'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A0002
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A0002'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A000
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A000'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A00
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A0
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A0'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0A
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-zynqmp-zynqmp
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm-zynqmp-zynqmp'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-zynqmp
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm-zynqmp'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Config file not found
starting USB...
Bus dwc3@fe200000: this is not a DesignWare USB3 DRD Core
failed to initialize core
Port not available.
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (0 ms)
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'boot.scr.uimg'.
Load address: 0x20000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (1 ms)
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'boot.scr.uimg'.
Load address: 0x18000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
JTAG: Trying to boot script at 0x20000000
## Executing script at 20000000
Wrong image format for "source" command
JTAG: SCRIPT FAILED: continuing...
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2007 bytes read in 20 ms (97.7 KiB/s)
## Executing script at 20000000
Bad Linux ARM64 Image magic!
SCRIPT FAILED: continuing...
MMC Device 1 not found
no mmc device at slot 1
SF: Detected n25q512a with page size 256 Bytes, erase size 64 KiB, total 64 MiB
device 0 offset 0x3e80000, size 0x80000
SF: 524288 bytes @ 0x3e80000 Read: OK
QSPI: Trying to boot script at 0x20000000
## Executing script at 20000000
Wrong image format for "source" command
QSPI: SCRIPT FAILED: continuing...


no devices available
NAND: SCRIPT FAILED: continuing...
starting USB...
Bus dwc3@fe200000: this is not a DesignWare USB3 DRD Core
failed to initialize core
Port not available.
USB is stopped. Please issue 'usb start' first.
starting USB...
Bus dwc3@fe200000: this is not a DesignWare USB3 DRD Core
failed to initialize core
Port not available.
USB is stopped. Please issue 'usb start' first.
scanning bus for devices...
SATA link 0 timeout.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 1.5 Gbps 0x3 impl SATA mode
flags: 64bit ncq only 

Device 0: unknown device
starting USB...
Bus dwc3@fe200000: this is not a DesignWare USB3 DRD Core
failed to initialize core
Port not available.
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (0 ms)
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'boot.scr.uimg'.
Load address: 0x18000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-00-0a-35-00-22-01
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/01-00-0a-35-00-22-01'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/0A00020F
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00020F'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/0A00020
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00020'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/0A0002
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A0002'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/0A000
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A000'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/0A00
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A00'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/0A0
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A0'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/0A
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0A'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/0
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/0'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/default-arm-zynqmp-zynqmp
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm-zynqmp-zynqmp'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/default-arm-zynqmp
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm-zynqmp'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/default-arm
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default-arm'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Retrieving file: pxelinux.cfg/default
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'pxelinux.cfg/default'.
Load address: 0x10000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
Config file not found
starting USB...
Bus dwc3@fe200000: this is not a DesignWare USB3 DRD Core
failed to initialize core
Port not available.
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (0 ms)
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'boot.scr.uimg'.
Load address: 0x20000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
BOOTP broadcast 1
DHCP client bound to address 10.0.2.15 (0 ms)
Using ethernet@ff0e0000 device
TFTP from server 10.0.2.2; our IP address is 10.0.2.15
Filename 'boot.scr.uimg'.
Load address: 0x18000000
Loading: *�
TFTP error: 'Access violation' (2)
Not retrying...
ZynqMP> 

imrickysu pushed a commit that referenced this issue Nov 20, 2021
vmayoral pushed a commit to vmayoral/Vitis-Tutorials that referenced this issue Jan 20, 2022
Update AIE feature tutorials 02,03,04 for 2021.1_next
@imrickysu
Copy link
Contributor

Hi @sven2314 Please check this issue and provide suggestions.

@imrickysu imrickysu removed their assignment Aug 1, 2022
@imrickysu imrickysu added the PFM Platform related issues label Aug 1, 2022
@sven2314
Copy link
Collaborator

Hi, @Hamptonjc
From my experience this error is caused by lacking of boot.scr. Most importantly the boot.scr should be prepared in image directory and give it to Vitis before generating the platform. If you already generate a platform you should copy the boot.scr to image directory and regenerate the platform again to make the mew file work.

imrickysu pushed a commit that referenced this issue Nov 3, 2022
CRTejaswi pushed a commit to CRTejaswi/amd-vitis that referenced this issue Oct 3, 2023
37cba5b Clean WebpEnc
05b7e30 fixed index.html
d3e13e2 modified 2021.1 to 2021.2
5d21faf Merge pull request Xilinx#107 from yunleiz/fnext
2f4abaa [gui] add description
0183ab5 Merge pull request Xilinx#106 from yunleiz/fnext
672b1db [clean]fixed CR https://jira.xilinx.com/browse/CR-1109840
010b477 fixed CR https://jira.xilinx.com/browse/CR-1109840
a64fbce Merge pull request Xilinx#103 from yuxiangz/move
480ec86 rm L2include
8d4685b Merge pull request Xilinx#102 from siyangw/next
383fda2 fix some problem for https://jira.xilinx.com/browse/CR-1107161
de542c3 Merge pull request Xilinx#101 from yuxiangz/rmwebp
0b648f2 rm webp
5ff5869 Merge pull request Xilinx#100 from liyuanz/next
4fa8680 replace XILINX_VIVADO with XILINX_HLS
ffcb650 Merge pull request Xilinx#98 from yuxiangz/image_error
e95ae01 fixed image error
891a16e Merge pull request Xilinx#97 from yuxiangz/readme
b0c676e fixed benchmark
c04bc74 update release
1b28512 fixed kernel doc
c853e54 update benchmark wepb
573f3db revise code struct
451450e add wepb api
7d4d309 Merge pull request Xilinx#95 from yuxiangz/readme
b2e9ddd fixed error for readme
9f32eb2 Merge pull request Xilinx#94 from yuxiangz/readme
8974955 fixed error for readme
ca242c9 Merge pull request Xilinx#91 from yunleiz/fnext
53b7203 [doc] fixed pik profm in next
b53c54c [doc] fixed pik profm in net
4152274 Merge pull request Xilinx#90 from yunleiz/fnext
f4a9082 [doc] fixed readme on next
a1b4baa Merge pull request Xilinx#88 from siyangw/fix_sw_emu
4bbba7f change 2021.1_stable_latest to 2021.2_stable_latest
REVERT: 48cc941 Merge pull request Xilinx#99 from yuxiangz/cr-640
REVERT: c373206 fixed image error for master
REVERT: 4d5db06 Merge pull request Xilinx#92 from yunleiz/fmaster
REVERT: 19e4a69 [doc] fixed pik profm in master
REVERT: 74e5c6a Merge pull request Xilinx#89 from yunleiz/fmaster
REVERT: 2f9cc50 [doc] fixed readme on master
REVERT: 587473b Merge pull request Xilinx#87 from siyangw/fix_sw_emu
REVERT: 41a249c create master branch from next branch

git-subtree-dir: codec
git-subtree-split: 37cba5bec8072c63d0d75433cebe2467cd74f401

Co-authored-by: sdausr <[email protected]>
CRTejaswi pushed a commit to CRTejaswi/amd-vitis that referenced this issue Oct 3, 2023
f7d1abc Merge pull request Xilinx#122 from tuol/disable_2_case
ae62691 disable 2 case due to U250 platform change
3af143e Merge pull request Xilinx#118 from tuol/fix_cr_1122542
3e7f919 temporally disable L3/tests/mlp, due to U250 platform change
1728d13 update opts.cfg
98d3f3f Merge pull request Xilinx#117 from yuanqian/next
8639708 remove email from Jenkinsfile:https://jira.xilinx.com/browse/CR-1124831
18a7458 Merge pull request Xilinx#116 from changg/wa_u280_201920
86e28ef WA for xilinx_u280_xdma_201920_3
07abe54 Merge pull request Xilinx#114 from liyuanz/replace_cflags
7cb157c replace cflags with clflags
0196ded Merge pull request Xilinx#113 from changg/cov_fix
fc100b4 cov fix
b201f43 cov fix
14067e6 Merge pull request Xilinx#110 from liyuanz/next
bbe42e9 fix bug
257677d Merge pull request Xilinx#109 from changg/pr_108
79db50c fix makefiles
984a71c update Makefile and utils
daf9820 Merge pull request Xilinx#106 from liyuanz/replace_blacklist
28fe2ed replace whiltelist/blacklist to allowlist/blocklist
981b5a2 Merge pull request Xilinx#105 from changg/pr_104
2f45a63 add time for hw_build
a21b8db add time
7256e35 add time
5f2c36a Merge pull request Xilinx#102 from changg/add_extraflags
acce305 fix utils.mk
74536af fix utils.mk
3c0647e Merge pull request Xilinx#101 from liyuanz/next
fc26744 increase mem
7a1b220 Merge pull request Xilinx#99 from changg/fix_mks
055c521 fix typ
44ff7b9 fix utils.mk
4050d17 Merge pull request Xilinx#98 from liyuanz/replace_targets
b0157d6 update targes
e41fc60 Merge pull request Xilinx#96 from changg/metadata
f6d1e26 draft metadata
0bbb982 change 2021.2_stable_latest to 2022.1_stable_latest

Co-authored-by: sdausr <[email protected]>
CRTejaswi pushed a commit to CRTejaswi/amd-vitis that referenced this issue Oct 3, 2023
00c1121 Merge pull request Xilinx#101 from changg/wa_u280
6353429 fix
15dddbb Merge pull request Xilinx#100 from changg/wa_u280
bb26130 wa for u280
f33813e Merge pull request Xilinx#99 from changg/fix_meta
78bfba6 fix meta

Co-authored-by: sdausr <[email protected]>
@AnusheelXilinx
Copy link
Collaborator

Closing the thread as there are no open concerns.

Thanks
Anusheel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PFM Platform related issues
Projects
None yet
Development

No branches or pull requests

5 participants