element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
ZUBoard VxWorks Image not working on U Boot
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 1 reply
  • Subscribers 347 subscribers
  • Views 1307 views
  • Users 0 members are here
  • jtag
  • ZUBoard
Related

VxWorks Image not working on U Boot

ABHIRAO12
ABHIRAO12 over 2 years ago

I am trying to boot VxWorks Image on U Boot for ZUB 1CG Board.
The Uboot is working fine with the board but unable to get the image correctly on the terminal.
I am using Vitis to flash .bin on board and using in QSPI Mode.
I have made changes dts as per my requirements and kept only Uart driver in dts.
I have tried most of the solutions provided on net but unable to get image.
Any proper resource or tutorial will help. Thanks

Xilinx Zynq MP First Stage Boot Loader
Release 2022.1 Sep 13 2023 - 18:20:39
Hello v1
MultiBootOffset: 0x0
Reset Mode : System Reset
Platform: Silicon (4.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZUUNKNCG
Proc: A53-0 Freq: 1200000000 Hz Arch: 64
Processor Initialization Done
================= In Stage 2 ============
QSPI 32 bit Boot Mode
QSPI is in single flash connection
QSPI is using 4 bit bus
FlashID=0x9D 0x70 0x19
ISSI 256M Bits
Qspi, Freq: 300000000 Hz
Multiboot Reg : 0x0
QSPI Reading Src 0x0, Dest FFFF0040, Length EC0
.QSPI Read Src 0x0, Dest FFFF0040, Length EC0
Image Header Table Offset 0x8C0
QSPI Reading Src 0x8C0, Dest FFFDA050, Length 40
.QSPI Read Src 0x8C0, Dest FFFDA050, Length 40
*****Image Header Table Details********
Boot Gen Ver: 0x1020000
No of Partitions: 0x3
Partition Header Address: 0x440
Partition Present Device: 0x0
QSPI Reading Src 0x1100, Dest FFFDA090, Length 40
.QSPI Read Src 0x1100, Dest FFFDA090, Length 40
QSPI Reading Src 0x1140, Dest FFFDA0D0, Length 40
.QSPI Read Src 0x1140, Dest FFFDA0D0, Length 40
QSPI Reading Src 0x1180, Dest FFFDA110, Length 40
.QSPI Read Src 0x1180, Dest FFFDA110, Length 40
Initialization Success
80.550970 ms. : Boot Dev. Init. Time
======= In Stage 3, Partition No:1 =======
UnEncrypted data Length: 0x537B0
Data word offset: 0x537B0
Total Data word length: 0x537B0
Destination Load Address: 0x8000000
Execution Address: 0x8000000
Data word offset: 0xF550
Partition Attributes: 0x116
QSPI Reading Src 0x3D540, Dest 8000000, Length 14DEC0
.QSPI Read Src 0x3D540, Dest 8000000, Length 14DEC0
82.523430 ms.: P1 Copy time, Size: 1367744
Partition 1 Load Success
======= In Stage 3, Partition No:2 =======
UnEncrypted data Length: 0xB54FF
Data word offset: 0xB54FF
Total Data word length: 0xB54FF
Destination Load Address: 0xFFFFFFFF
Execution Address: 0x0
Data word offset: 0x62D00
Partition Attributes: 0x26
QSPI Reading Src 0x18B400, Dest 100000, Length 2D53FC
.QSPI Read Src 0x18B400, Dest 100000, Length 2D53FC
168.241220 ms.: P2 Copy time, Size: 2970620
Destination Device is PL, changing LoadAddress
Non authenticated Bitstream download to start now
DMA transfer done
4.429030 ms.: P2 (nsec. bitstream) dwnld Time
PL Configuration done successfully
Partition 2 Load Success
All Partitions Loaded
528.189330 ms.: Total Time
Note: Total execution time includes print times
================= In Stage 4 ============
PM Init Success
Protection configuration applied
Running Cpu Handoff address: 0x8000000, Exec State: 0
Exit from FSBL


U-Boot 2023.01 (Sep 11 2023 - 11:40:37 +0530)

CPU: ZynqMP
Silicon: v3
Chip: zu1eg
Board: Xilinx ZynqMP
DRAM: 1023 MiB
PMUFW: v1.1
PMUFW: No permission to change config object
EL Level: EL3
Secure Boot: not authenticated, not encrypted
Multiboot: 0
Core: 46 devices, 23 uclasses, devicetree: board
NAND: 0 MiB
MMC: mmc@ff170000: 0
Loading Environment from SPIFlash... SF: Detected is25wp256 with page size 256 Bytes, erase size 64 KiB, total 32 MiB
OK
In: serial
Out: serial
Err: serial
Net:
ZYNQ GEM: ff0d0000, mdio bus ff0d0000, phyaddr 7, interface rgmii-id

Warning: ethernet@ff0d0000 MAC addresses don't match:
Address in ROM is ff:ff:ff:ff:ff:ff
Address in environment is fc:c2:3d:42:e0:b9
eth0: ethernet@ff0d0000
scanning bus for devices...
Hit any key to stop autoboot: 0
ZynqMP>
ZynqMP>
ZynqMP>
ZynqMP>
ZynqMP>
ZynqMP> setenv ipaddr 165.100.10.40 && setenv serverip 165.100.10.35 && setenv netmask 255.255.255.0 && setenv bootargs 'gem(0,0)host:vxworks h=165.100.10.40 e=165.100.10.35:ffffff00 u=target pw=vxTarget f=0x0' && setenv eth0addr fc:c2:3d:42:e0:b9
ZynqMP> tftpb 0x5000000 165.100.10.35:uVxWorks && tftpb 0x4000000 165.100.10.35:xlnx-zcu102-rev-1.1.dtb
ethernet@ff0d0000 Waiting for PHY auto negotiation to complete................ done
Using ethernet@ff0d0000 device
TFTP from server 165.100.10.35; our IP address is 165.100.10.40
Filename 'uVxWorks'.
Load address: 0x5000000
Loading: T T #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#############################################################
339.8 KiB/s
done
Bytes transferred = 5968040 (5b10a8 hex)
Using ethernet@ff0d0000 device
TFTP from server 165.100.10.35; our IP address is 165.100.10.40
Filename 'xlnx-zcu102-rev-1.1.dtb'.
Load address: 0x4000000
Loading: ###
931.6 KiB/s
done
Bytes transferred = 11453 (2cbd hex)
ZynqMP> bootm 0x5000000 - 0x4000000
## Booting kernel from Legacy Image at 05000000 ...
Image Name: vxworks
Created: 2023-09-19 12:35:56 UTC
Image Type: AArch64 VxWorks Kernel Image (uncompressed)
Data Size: 5967976 Bytes = 5.7 MiB
Load Address: 00100000
Entry Point: 00100000
Verifying Checksum ... OK
## Flattened Device Tree blob at 04000000
Booting using the fdt blob at 0x4000000
Working FDT set to 4000000
Loading Kernel Image
!!! WARNING !!! Using legacy DTB
Loading Device Tree to 000000003fefa000, end 000000003feffcbc ... OK
Working FDT set to 3fefa000
## Starting vxWorks at 0x00100000, device tree at 0x3fefa000 ...
Ûp
òÜ ?
làÛnâ#
?b?ÜÈÄ9
rr|òn<cr?ßÈnn?`¶àr?ßÈnnßÄGânÄb?nâFb?n|ÜÆb;Ibbû
À
?

rÜÀ?rnßÄ?b?rßÇb

?bÜ?b?bÜ?bÜp

lÇÇ
r~r?rßÇÄG??ÄF?n|ÜÆb rÛHØH?

àÇÀ


?Øl`?b

?âÜ?â?âÜ?âÜð
â

b?ònäÛr?bÄ9

?âÜ?â?âÜ?âÜð
â

?ònäÛr?bû
ØÜÇrnÀ?àâÜ?âÜ?â?âÜ?
â

;r?
;?l8
n?߯?l8|?
;r?
8?ÄÇ?ßÀ?âb#`àâÜ?â?âÜ?â?
â

?ònäÛr?bû
Ø rÄÈÜÇrnÀnà;O??ÄÈÜÆnìãnàÃOâÃN?r?ßÇ?l;ÄÈb?òÜ?ÜÆ?aân6àr?ßÈnnßÄÈnàÃOln|?ì<bòܾ?ÄÈ
b#

  • Sign in to reply
  • Cancel
  • narrucmot
    0 narrucmot over 2 years ago

    I see at the start of VxWorks execution at the handoff from u-boot that the serial terminal output changes to unreadable characters.  This is an indication that the UART baud rate has changed.  The ZynqMP FSBL and u-boot will have had the ZynqMP UART baud set to 115,200.  I suspect your VxWorks OS image changes the baud rate to something different. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube