UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Contributor
Contributor
2,281 Views
Registered: ‎03-23-2018

ZCU102 System Controller firmware update to 2017.4 failed

Jump to solution

Hi,

 

- I have Vivado 2017.4, ZCU102 board, system controller firmware version May 17 2017 12:51:57 

 

- I tried to update System Controller on my zcu102 board to 2017.4, and got error message as below

 

- There is J164 on my board, so I just use 2 jumper to connect it, not use long jumper as instructed.

 

- From log file, look like bit file is loaded and running. However, it failed when try reading from COM port. (I closed all Tera Term before launching fimrware update, so it should not be conflict problem)

 

- Before running, I can use Tera Term to check both COM interface 0 and 3, so they are really there.\

 

- Instruction how to upate fimrware from XTP433 2017.4  is really bad, just one slide for how to run BIT.EXE, so I have no idea which option I should select before running, so I just click on SYS_CTRL_v1.50 RESTORE button,

 

Board: ZCU102
Serial Number: 0000-0000
Mac Address: 01:02:03:04:05:06


Info: SYS_CTLR v1.50 RESTORE test started...

Info: The test will take 0 hours, 01 minutes, and 21 seconds. 0:01:21

Info: This step started at: 2018-04-05 10:38:13

Info: This step started at: 2018-04-05 10:38:13

User has confirmed: "Turn ZCU102 Board Power Off.
Set mode switch SW6 to "0" (Up,Up,Up,Up)
Connect two long jumpers:
From J87 (PMOD1), Pin 1 to J92, Pin 11
From J87 (PMOD1), Pin 3 to J92, Pin 8
Turn ZCU102 Power On"

step finished

Info: This step started at: 2018-04-05 10:38:14
after 2000

catch { disconnect }
1
after 2000

connect -url tcp:127.0.0.1:3121
attempting to launch hw_server

****** Xilinx hw_server v2017.4.1
**** Build date : Jan 30 2018-15:49:02
** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

INFO: hw_server application started
INFO: Use Ctrl-C to exit hw_server application

 

****** Xilinx hw_server v2017.4.1

**** Build date : Jan 30 2018-15:49:02

** Copyright 1986-2017 Xilinx, Inc. All Rights Reserved.

 

INFO: hw_server application started

INFO: Use Ctrl-C to exit hw_server application

 


INFO: To connect to this hw_server instance use url: TCP:127.0.0.1:3121

 

tcfchan#0
targets -set -filter {name =~"*APU*"}

rst -srst

after 3000

targets -set -filter {name =~"*APU*"}

fpga -no-revision-check -file C:/x/zcu102_scui/flash_restore/tests/ZCU102/bitstream/boot_strap_loader.bit

initializing
0% 0MB 0.0MB/s ??:?? ETA
4% 1MB 2.1MB/s ??:?? ETA
7% 1MB 1.7MB/s ??:?? ETA
11% 2MB 1.8MB/s ??:?? ETA
15% 3MB 1.8MB/s ??:?? ETA
18% 4MB 1.7MB/s ??:?? ETA
22% 5MB 1.7MB/s 00:11 ETA
26% 6MB 1.7MB/s 00:10 ETA
29% 7MB 1.7MB/s 00:10 ETA
32% 8MB 1.7MB/s 00:09 ETA
36% 9MB 1.7MB/s 00:09 ETA
39% 10MB 1.7MB/s 00:08 ETA
43% 11MB 1.7MB/s 00:08 ETA
47% 12MB 1.7MB/s 00:07 ETA
51% 13MB 1.7MB/s 00:07 ETA
54% 13MB 1.7MB/s 00:06 ETA
58% 14MB 1.7MB/s 00:06 ETA
61% 15MB 1.7MB/s 00:05 ETA
65% 16MB 1.7MB/s 00:05 ETA
68% 17MB 1.7MB/s 00:04 ETA
72% 18MB 1.7MB/s 00:04 ETA
76% 19MB 1.7MB/s 00:03 ETA
79% 20MB 1.7MB/s 00:03 ETA
83% 21MB 1.7MB/s 00:02 ETA
86% 21MB 1.7MB/s 00:02 ETA
89% 22MB 1.7MB/s 00:01 ETA
93% 23MB 1.7MB/s 00:01 ETA
96% 24MB 1.7MB/s 00:00 ETA
99% 25MB 1.7MB/s 00:00 ETA
100% 25MB 1.7MB/s 00:15

targets -set -filter {name =~"*APU*"}

source C:/x/zcu102_scui/flash_restore/tests/ZCU102/tcl/bsl_psu_init.tcl

psu_init

after 1000

psu_ps_pl_isolation_removal

after 1000

psu_ps_pl_reset_config

targets -set -filter {name =~"*A53*0"}

rst -processor

dow C:/x/zcu102_scui/flash_restore/tests/ZCU102/elf/boot_strap_loader.elf

Downloading Program -- C:/x/zcu102_scui/flash_restore/tests/ZCU102/elf/boot_strap_loader.elf
section, .text: 0x00000000 - 0x0001442f
section, .init: 0x00014440 - 0x00014473
section, .fini: 0x00014480 - 0x000144b3
section, .note.gnu.build-id: 0x000144b4 - 0x000144d7
section, .rodata: 0x000144d8 - 0x00014dcf
section, .rodata1: 0x00014dd0 - 0x00014dff
section, .sdata2: 0x00014e00 - 0x00014dff
section, .sbss2: 0x00014e00 - 0x00014dff
section, .data: 0x00014e00 - 0x00015fe7
section, .data1: 0x00015fe8 - 0x00015fff
section, .ctors: 0x00016000 - 0x00015fff
section, .dtors: 0x00016000 - 0x00015fff
section, .eh_frame: 0x00016000 - 0x00016003
section, .mmu_tbl0: 0x00017000 - 0x0001700f
section, .mmu_tbl1: 0x00018000 - 0x00019fff
section, .mmu_tbl2: 0x0001a000 - 0x0001dfff
section, .preinit_array: 0x0001e000 - 0x0001dfff
section, .init_array: 0x0001e000 - 0x0001e007
section, .fini_array: 0x0001e008 - 0x0001e047
section, .sdata: 0x0001e048 - 0x0001e07f
section, .sbss: 0x0001e080 - 0x0001e07f
section, .tdata: 0x0001e080 - 0x0001e07f
section, .tbss: 0x0001e080 - 0x0001e07f
section, .bss: 0x0001e080 - 0x0011e2bf
section, .heap: 0x0011e2c0 - 0x001262bf
section, .stack: 0x001262c0 - 0x0012f2bf

0% 0MB 0.0MB/s ??:?? ETA
79% 0MB 0.2MB/s ??:?? ETA
100% 0MB 0.2MB/s 00:00

Setting PC to Program Start Address 0x00000000
Successfully downloaded C:/x/zcu102_scui/flash_restore/tests/ZCU102/elf/boot_strap_loader.elf

con

step finished

Info: This step started at: 2018-04-05 10:38:43
Error: Invalid input for COM port

Error: Found regular expression in step 3 of test 0 - "(.*)Error(.*)"

Error: Could not find regular expression in step 3 of test 0 - "(.*)File\s+sent\s+successfully"

Info: This step started at: 2018-04-05 10:38:43

Error: Stopped because step 3 failed in test 0

step finished

Error: Could not find regular expression in step 0 of test 0 - "(.*)MSP v1.50 I2C Bridge v1.50(.*)"

Info: Result for step 0: Fail
Info: Result for step 1: Pass
Info: Result for step 2: Pass
Info: Result for step 3: Fail
Info: The test took 0 hours, 00 minutes, and 30 seconds. 0:00:30

 

Thanks,

Andrew

0 Kudos
1 Solution

Accepted Solutions
Contributor
Contributor
2,529 Views
Registered: ‎03-23-2018

Re: ZCU102 System Controller firmware update to 2017.4 failed

Jump to solution
Hi all,

- I found the problem: there is mismatch between COM Port name between windows device manager and flash restore program.

- In my case, windows device manager report as Silicon Labs Quad CP2108 USB to UART Bridge: Interface 0", while firmware_flash_gui_070517.bat use the name Silicon Labs Quad CP2108x USB to UART Bridge: Interface 0"

- Fix?: just open that bat file and change x into 8 or any newer device id that your device manager report.

Cheers
Andrew.




7 Replies
Contributor
Contributor
2,530 Views
Registered: ‎03-23-2018

Re: ZCU102 System Controller firmware update to 2017.4 failed

Jump to solution
Hi all,

- I found the problem: there is mismatch between COM Port name between windows device manager and flash restore program.

- In my case, windows device manager report as Silicon Labs Quad CP2108 USB to UART Bridge: Interface 0", while firmware_flash_gui_070517.bat use the name Silicon Labs Quad CP2108x USB to UART Bridge: Interface 0"

- Fix?: just open that bat file and change x into 8 or any newer device id that your device manager report.

Cheers
Andrew.




Highlighted
Newbie ielecer
Newbie
1,808 Views
Registered: ‎09-07-2018

Re: ZCU102 System Controller firmware update to 2017.4 failed

Jump to solution
Good job! Andrew.
0 Kudos
Adventurer
Adventurer
1,744 Views
Registered: ‎03-29-2008

Re: ZCU102 System Controller firmware update to 2017.4 failed

Jump to solution

Why is it that the slides that give the instructions do not mention it?  The BAT files does, but that is NOT the first place I looked, rather I read the instructions.  Silly me I thought they would tell me how to make it go.  

 

There is a comment as to the quality of the instructions at the beginning of the thread.  I agree.

 

Nick

 

0 Kudos
Observer gclark
Observer
1,532 Views
Registered: ‎07-11-2018

Re: ZCU102 System Controller firmware update to 2017.4 failed

Jump to solution

Scratching my head on this one ... thank you Andrew!

0 Kudos
Observer thomasmurphyge
Observer
1,207 Views
Registered: ‎09-20-2018

Re: ZCU102 System Controller firmware update to 2017.4 failed

Jump to solution

This is probably related to AR 69640, where compatibility with the SiLabs driver is limited to 6.7.0. However, the 6.7.0 driver is not compatible with Windows 10, having been replaced by a version 10.x.x driver. The device name search change still works under Windows 10 and with Vivado 2018.2 with version 9.0/June 18, 2018 version of XTP433.

For improved clarity, the BAT file to modify is located in <unzip dir>\zcu102_scui\flash_restore\tests\ZCU102\bat. The string passed to the -c flag of MSP_BSL_Flasher.exe needs to match the base COM port name from Device Manager. The change is still with regard to the chip name having the "x" placeholder versus a full number.

0 Kudos
Moderator
Moderator
1,170 Views
Registered: ‎08-10-2007

Re: ZCU102 System Controller firmware update to 2017.4 failed

Jump to solution

@andrewngo Thank you for including the solution that worked for you.  I believe you are correct, and this is to do with the CP210x driver showing up as anything other than CP210x (CP2105 or CP2108 for example).  For future reference, this is outlined in (Xilinx Answer 68521): https://www.xilinx.com/support/answers/68521.html

 

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Contributor
Contributor
782 Views
Registered: ‎07-23-2015

Re: ZCU102 System Controller firmware update to 2017.4 failed

Jump to solution

Thank you for sharing this. Your solution worked for me as well.

0 Kudos