how to build defect-detection app from source and list the revision of the source? #2
Comments
|
hi Tony, I didnt see a .bit file. Also please note, xmutil expects a .bit.bin file, not a .bit file (please see step 3 here to convert: https://xilinx.github.io/kria-apps-docs/creating_applications/1.0/build/html/docs/creating_applications_vitis_accel_flow.html#step-3 ) There's also a different way to move files onto target: in my comment here i am referring to pages under https://xilinx.github.io/kria-apps-docs/creating_applications/1.0/build/html/index.html - it would be good to understand what your goal is so I can understand which flow you are sort of going through. Then I maybe able to help further. |
Thanks |
|
I think my title need to change to "how to build defect-detection app from source and list the revision of the source?" I got error in dmesg. I list the sequence of how I do it in below petalinux-createapp files generated after petalinux-createpetalinux-buildapp files generated after petalinux-builduse SFTP to put below files to target systemI put the file in below location in target systemsudo xmutil loapappdmesg error after loadapp - tony-0303fw-release-2020.2.2-k26 |
TonyHo722
changed the title
in https://github.com/Xilinx/kv260-firmware/blob/release-2021.1/defect-detect/kv260-defect-detect.dtsi
but I found in /home/tonyho/petalinux/2021.1/tools/xsct/release-2020.2.2_k26/pl.dtsi => this file generated by DTG.
in the https://github.com/Xilinx/linux-xlnx/blob/master/drivers/media/platform/xilinx/xilinx-csi2rxss.c I also found this link https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/128024605/DTG+limitation+for+multimedia+IPs
My question is - Can I use the DTG to generate the dtsi file from defect-detection PL design (.xsa file)? or I need to manual modify the dtsi file generated from DTG? in /home/tonyho/petalinux/2021.1/tools/xsct/release-2020.2.2_k26/pl.dtsi
|
|
@TonyHo722 thanks for the detailed write up. first - you will need to align tool version to the bsp version. you should be using 21.1 tools with 21.1 bsp, it will not work otherwise. you are currently using 2020.2 this command below, can you tell me what it should do? just want to make sure the basics is good before we go into more details into the other questions |
1. base on your comment, I think I need provide my detail flow for you to check what I miss.
My flow to build petalinux image and app as below.
Step 1. create petalinux project and put in /home/tonyho/petalinux/2021.1/tony_0215Step 2. add BOARD_VARIANTStep 3. petalinux-config -c rootfs
Step 4. build petalinux imageStep 5. Add New FPGA Firmware(app) for defect-detection.
Step 6. build petalinux image again to generate New FPGA FirmwareStep 7. New FPGA Firmware(app) files generated after petalinux-build2. I am confusing in your comment.
|
|
for align tool version, I had done as below but it is no help I check the pl. dtsi file still with below comment,
I used below comment to generate .dtsi file pl.dtsi file in this folder. pl.dtsi content as below demsg error I think this issue is how to generate .dtsi file for the app. |
|
hi @TonyHo722 please note there's also this way of placing firmware on target to run (instead of doing it through petalinux): |
|
I got it. I will try to manual tuning it. |
|
Could you comment what revision of kv260-vitis can generate exact the same binary of below files in kv260-firmware? https://github.com/Xilinx/kv260-firmware/blob/release-2021.1/defect-detect/kv260-defect-detect.xclbin does it as below? If you can provide it then I can just use the .dtsi in below without modify and study the source. Thanks |
|
I can run the defect-detection from the binary I built from sourece now. I used below revision to generate .xclbin and .bit file the .xclbin and .bit file is generated from vivado 2021.1 and https://github.com/Xilinx/kv260-vitis branch = release_2021.1 command as below to generate the app file
Note: the .dtsi file is come from https://github.com/Xilinx/kv260-firmware/blob/release-2021.1/defect-detect/kv260-defect-detect.dtsi the dmesg error after "sudo xmutil loadapp tony-0309fw-rel-v2021.1"
run python code in jupyter notebook and result is ok
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had try to create app in below command and the firmware files are come from https://github.com/Xilinx/kv260-firmware/tree/release-2021.1/defect-detect.
The result is ok to run defect-detect.ipynb in Jupyter notebook in target system.
Note: I used 4 files from https://github.com/Xilinx/kv260-firmware/tree/release-2021.1/defect-detect to create the app
But I have issue when I replace .bin & .xclbin files as my build kv260-defect-detect-my-build.bit and kv260-defect-detect-my-build.xclbin in below command.
I named the app to my-0215fw2, it with issue when run defect-detect.ipynb in Jupyter notebook. the picture with noise as below picture.
Note: the kv260-defect-detect-my-build.bit and kv260-defect-detect-my-build.xclbin is built from https://github.com/Xilinx/kv260-vitis.
and I had follow this link Xilinx/kria-vitis-platforms#11 to built the .bin & .xclbin file.
I am not sure does it correct to just replace the .bin & .xclbin file?
I found the dmesg with error as below in my-0215fw2
or I should create my own .dtsi file?
I don't know how to create .dtsi file, any comment about how to create it?
I had follow "Generate .dtsi from .xsa using DTG" from https://xilinx.github.io/kria-apps-docs/creating_applications/1.0/build/html/docs/creating_applications_dtsi_dtbo_generation.html but it still fail.
I found in .dtsi file I generated from .xsa file as below.
should I update the firmware-name in the .dtsi file?
I also found in https://github.com/Xilinx/kv260-firmware/blob/release-2021.1/defect-detect/kv260-defect-detect.dtsi with zocl:
it is not found from my .dtsi file which generated from .xsa file.
should I add below in my .dtsi file?
Note: my KV260 target system without AR0144 mipi camera module, I used camera, I used playback=5 in defect-detect.ipynb in Jupyter notebook to test it.
The text was updated successfully, but these errors were encountered: