Zynqberry demo1

[Gloria]

After the win_setup_cmd, I open the project by vivado and write TE::pr_programming_flash swapp u-boot according to the instructions.
However,
TE::pr_program_flash -swapp u-boot
Start Flash Programming
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
INFO: [Labtools 27-2222] Launching hw_server...
INFO: [Labtools 27-2221] Launch Output:

****** Xilinx hw_server v2020.1
  **** Build date : May 27 2020 at 20:24:38
    ** Copyright 1986-2020 Xilinx, Inc. All Rights Reserved.


INFO: [Labtools 27-3415] Connecting to cs_server url TCP:localhost:3042
INFO: [Labtools 27-3417] Launching cs_server...
INFO: [Labtools 27-2221] Launch Output:


****** Xilinx cs_server v2020.1.0
  **** Build date : May 14 2020-09:10:29
    ** Copyright 2017-2020 Xilinx, Inc. All Rights Reserved.



connect_hw_server: Time (s): cpu = 00:00:03 ; elapsed = 00:00:08 . Memory (MB): peak = 1150.301 ; gain = 0.012
WARNING: [Labtoolstcl 44-128] No matching hw_devices were found.
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/251633005930A
open_hw_target: Time (s): cpu = 00:00:05 ; elapsed = 00:00:07 . Memory (MB): peak = 2439.836 ; gain = 1289.535
INFO: [Labtools 27-1434] Device xc7z010 (JTAG device index = 1) is programmed with a design that has no supported debug core(s) in it.
WARNING: [Xicom 50-100] The current boot mode is QSPI.
If flash programming fails, configure device for JTAG boot mode and try again.
Problem in running uboot
Flash programming initialization failed.
ERROR: [Labtools 27-3161] Flash Programming Unsuccessful
ERROR: [TE_PR-108] Script (TE::VLAB::hw_program_flash) failed: ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.
.
ERROR: (TE_PR-108) Script (TE::VLAB::hw_program_flash) failed: ERROR: [Common 17-39] 'program_hw_cfgmem' failed due to earlier errors.
.

[JH]

Hi,
scripts was not created for 2020.1 Vivado.

For Flash Programmings see:
https://wiki.trenz-electronic.de/pages/viewpage.action?pageId=105689937
and (Xilinx Dokumentation and which described how you program it without scripts):
https://wiki.trenz-electronic.de/display/PD/Xilinx+Development+Tools#XilinxDevelopmentTools-XilinxSoftwareProgrammingandDebugging

br
John

[Gloria]

Hi， I have wacthed the solutions about"add register mode =JTAG"
However, I found that this has been added into the demo1 of 2019.2 in fsbl_flash.elf. So i think the flash will be successful using the fsbl_flash.elf in demo1 of 2019.2, right?
1. I completed TE::pr_program_flash -swapp u-boot
2.copy image.ub and  init.sh into SD card
3. insert SD card
but the monitor is the color of yellow
What's the problem?
Besides, the COM5 in windows should be set as 1152000， right? I have set this.

[JH]

Hi,
since 2019.2 it depends on the content of the QSPI Flash which FSBL you need:
https://wiki.trenz-electronic.de/pages/viewpage.action?pageId=105689937#AR00002QSPIProgrammingissues-Vivado2019.xornewer(lasttestedversion2020.1)

fsbl_flash.elf in case it'S empty, default one in case it's not empty.

On older Vivado versions it was easier to use

br
John

[Gloria]

I understand ...
Now, I have another computer that has vivado 2017.1
And I download the demo1 of 2017.1
I open the project with "win_setup_cmd"，however, when I try to flash the memory with /prebuilt/boot_images/<short dir>/u-boot and /prebuilt/software/<short dir>/zynq_fsbl.elf
The flash program also unseccessful,and the erase and programming are successful but verify failed.
What's the problem?

[Gloria]

Hi, it works now.
However, I found that every time after implementing rst, the monitor is80% black and 20% grainy on the bottom of the screen.
And after about 1 minutes, the video display rightly.
Why?
Besides, whether it is related with JTAG scan rate? Every time I change the scan rate from mannualy to 30 s， I do not know what reasons.
Thank you !

[JH]

Hi,
it's a demo only. in in case you use RPI camera 2.1, it's no complete stable at the moment:
https://wiki.trenz-electronic.de/display/PD/TE0726+Zynqberry+Demo1#TE0726ZynqberryDemo1-Hardware

problem is that the camera must be configuration over I2C  and the specification of the camera is not free  available and this demo was created with information which can be found on the web from RPI user.
Our source code is included you can modify and improve the design if you want.


br
John