Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 171
» Latest member: Finley167
» Forum threads: 65
» Forum posts: 289

Full Statistics

Online Users
There are currently 9 online users.
» 0 Member(s) | 9 Guest(s)

Latest Threads
Possible to run older ver...
Forum: Getting Started
Last Post: Robert.VanVossen
Yesterday, 02:48 PM
» Replies: 1
» Views: 41
Which qemu-system-aarch64...
Forum: Getting Started
Last Post: brettstahlman
08-15-2017, 01:55 PM
» Replies: 2
» Views: 45
XZD Yocto Layer
Forum: Knowledge Base
Last Post: ariefgrand
08-14-2017, 05:20 PM
» Replies: 6
» Views: 471
DomU I/O and Communicatio...
Forum: Public Support
Last Post: Nathan.Studer
08-14-2017, 01:21 PM
» Replies: 3
» Views: 281
SD card does not boot pas...
Forum: Public Support
Last Post: jarvis_roach
08-04-2017, 01:58 PM
» Replies: 5
» Views: 357
SD card booting hangs sta...
Forum: Public Support
Last Post: ReubenLewis
07-21-2017, 12:54 PM
» Replies: 1
» Views: 263
booting from SD card
Forum: Public Support
Last Post: jarvis_roach
07-18-2017, 03:07 PM
» Replies: 5
» Views: 447
kpartx won't mount root p...
Forum: Public Support
Last Post: jarvis_roach
07-12-2017, 12:11 AM
» Replies: 1
» Views: 203
XZD_20160930 Release
Forum: Knowledge Base
Last Post: jarvis_roach
07-11-2017, 12:23 PM
» Replies: 5
» Views: 1,662
Yocto image as domU
Forum: Public Support
Last Post: jarvis_roach
07-11-2017, 12:17 PM
» Replies: 12
» Views: 850

 
  Possible to run older versions of xilinx linux kernel on zynqmp ultrascale+?
Posted by: brettstahlman - 08-18-2017, 06:51 PM - Forum: Getting Started - Replies (1)

I would like to run a 3.x linux kernel on my zynqmp ultrascale+ (ZCU102), rather than the 4.x kernel that corresponds to the latest xlnx-linux release. Accordingly, I checked out the version of xlnx-linux tagged as 2013.4 (which used v3.12 kernel), and I was able to build it after making some minor tweaks (e.g., adding zcu102-specific DTS files). But it hangs near the beginning of boot. I'll probably try to enable some additional debug information, but I'd like to know before I get too far down the debugging path whether what I'm trying to do is even feasible. What is the earliest kernel version on which the xilinx linux kernel has been tested on the ZCU102?

Thanks,
Brett S.

Print this item

  Which qemu-system-aarch64 should be in path?
Posted by: brettstahlman - 08-14-2017, 09:56 PM - Forum: Getting Started - Replies (2)

Hello,
I've installed both XZD (2016.12.31) and the Xilinx SDK (2016.3), and am uncertain as to which of the following qemu-system-aarch64 binaries I should be using:

  • Debian system (v2.5.0)
  • Xilinx SDK (v2.2.50)
  • XZD tools/hsm/bin (v2.2.50)
  • XZD tools/linux-i386/petalinux/bin (v2.2.50)
Sourcing settings64.sh in the Xilinx SDK puts the Xilinx SDK version in my PATH, but text in the XZD user manual makes it sound as though I should be using the one that ships with XZD. The version numbers of the XZD/Xilinx binaries are actually indentical, but perhaps they're different builds? Any information would be greatly appreciated...
Thanks,
Brett S.

Print this item

  SD card booting hangs stage 4, ES1
Posted by: jrheisey - 07-20-2017, 08:22 PM - Forum: Public Support - Replies (1)

 
Using the prebuilt binary files from XZD_20161231.gz.
There are no errors. It just stops during Stage 4 as demonstrated in thread
http://xzdforums.dornerworks.com/showthr...In+Stage+4
Here is the console output.
 
 
Xilinx Zynq MP First Stage Boot Loader
Release 2016.3   Jan  5 2017  -  11:58:09
Platform: Silicon (1.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
Board Configuration successful
Processor Initialization Done
================= In Stage 2 ============
SD1 Boot Mode
SD: rc= 0
File name is BOOT.BIN
Multiboot Reg : 0x0
Image Header Table Offset 0x8C0
*****Image Header Table Details********
Boot Gen Ver: 0x1020000
No of Partitions: 0x4
Partition Header Address: 0x440
Partition Present Device: 0x0
Initialization Success
======= In Stage 3, Partition No:1 =======
UnEncrypted data Length: 0x1800
Data word offset: 0x1800
Total Data word length: 0x1800
Destination Load Address: 0xFFFEA000
Execution Address: 0xFFFEA000
Data word offset: 0x8A20
Partition Attributes: 0x116
Partition 1 Load Success
======= In Stage 3, Partition No:2 =======
UnEncrypted data Length: 0x8
Data word offset: 0x8
Total Data word length: 0x8
Destination Load Address: 0xFFFF0000
Execution Address: 0x0
Data word offset: 0xA220
Partition Attributes: 0x116
Partition 2 Load Success
======= In Stage 3, Partition No:3 =======
UnEncrypted data Length: 0x22B80
Data word offset: 0x22B80
Total Data word length: 0x22B80
Destination Load Address: 0x8000000
Execution Address: 0x8000000
Data word offset: 0xA230
Partition Attributes: 0x116
Partition 3 Load Success
All Partitions Loaded
================= In Stage 4 ============
Protection configuration applied
  ATF running on XCZU9EG/silicon v1/RTL5.1 at 0xfffea000
NOTICE:  BL31: Secure code at 0x0
NOTICE:  BL31: Non secure code at 0x0
NOTICE:  BL31: v1.2(release):2c2b23f
NOTICE:  BL31: Built : 11:58:24, Jan  5 2017
 
Note that my boot output says
 
ATF running on XCZU9EG/silicon v1/RTL5.1 at 0xfffea000
 
Where the boot in the below referenced forum thread is
 
ATF running on XCZU9EG/silicon v3/RTL5.1 at 0xfffea000
 
Is this relevant?

I am going down the path of rebuilding u-boot.

_____________________________________________________
The Xen-Zynq-Distribution-XZD-Users-Manual.pdf says …
 
If the U-Boot boot command was not modified, you will need to interrupt the startup sequence and enter the boot commands manually:
U-Boot-PetaLinux> fatload mmc 0:1 $fdt_addr xen.dtb
U-Boot-PetaLinux> fdt addr $fdt_addr
U-Boot-PetaLinux> fdt resize
U-Boot-PetaLinux> fatload mmc 0:1 0x80000 Image
U-Boot-PetaLinux> fdt set /chosen/dom0 reg <0 0x80000 0x$filesize>
U-Boot-PetaLinux> fatload mmc 0:1 6000000 xen.ub
U-Boot-PetaLinux> bootm 6000000 - $fdt_addr
 
The document does not say how to interrupt the startup sequence.
Pressing CTL->C after the last output has no effect.



Regards,
J.R. Heisey
 

Print this item

  SD card does not boot past stage 2
Posted by: jrheisey - 07-13-2017, 12:01 AM - Forum: Public Support - Replies (5)

Greetings,


Code:
Xilinx Zynq MP First Stage Boot Loader
Release 2016.3   Jan  5 2017  -  11:58:09
Platform: Silicon (3.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
Board Configuration successful
Processor Initialization Done
================= In Stage 2 ============
SD1 with level shifter Boot Mode
SD: rc= 0
File name is BOOT.BIN
SD: Unable to open file BOOT.BIN: 3
                                   XFSBL_ERROR_SD_F_OPEN
Boot Device Initialization failed 0x29
================= In Stage Err ============
Fsbl Error Status: 0x0
  • I am using the binaries from XZD_20161231.gz
  • I followed most of instructions in Xen-Zynq-Distribution-XZD-Users-Manual.pdf
  • I deviated only by putting the files directly on the SD card rather than an image file due to technical issues
  • I am using CentOS as a guest in VirtualBox on Windows 7 host
  • I created the xen-zcu102_sd.dtb using the patch in the user's manual (above) and PetaLinux v2015.4 and vivado 2017.2
  • I have HW-Z1-ZCU102 revision 1.0
Questions:
  • Could this be an issue with using fdisk, mounting the SD card and coping files?
  • Could this be a compatibility issue between the hardware and the pre-built binary files?
  • I do not have a reason to build my own binaries at this time
  • My goal is to run some user mode software under the hypervisor for testing purposes
  • If the SD card configuration is most likely to be the problem then I am considering getting a physical computer with Ubuntu 14.04 as what is recommended in the DornerWorks' user's manual.
J.R. Heisey

Print this item

  kpartx won't mount root partition
Posted by: jrheisey - 07-11-2017, 09:10 PM - Forum: Public Support - Replies (1)

Here are the steps from the document from DornerWorks Xen-Zynq-Distribution-XZD-Users-Manual.pdf

Quote:1. Create a new clean two partition image.
   $ dd if=/dev/zero of=$RELEASE_DIR/dist/images/sdcard.img bs=1G count=7
   $ echo -e "n\np\n1\n\n+256M\nt\nc\nn\np\n2\n\n\nt\n2\n83\nw\n" | fdisk
   $RELEASE_DIR/dist/images/sdcard.img
2. Install kpartx if it is not already.
   $ sudo apt-get install kpartx
3. Mount both partitions of the image using kpartx.
   sudo kpartx -av $RELEASE_DIR/dist/images/sdcard.img
   sudo mkfs.vfat /dev/mapper/loop1p1
   sudo mkfs.ext4 /dev/mapper/loop1p2

I am using CentOS as a guest of VirtualBox with Windows 7 as the host OS.
I have a couple of issues with the document.
  • For dd I changed the count=7 to count=15 for my larger SD card.
  • The string piped to fdisk did not work out-of-the-box. I needed to manually run fdisk to create the two partitions.
  • The string shows the first partition set to the system ID of 'c' which is 'W95 FAT32 (LBA)'.
          I tried leaving it at the default of '83' for 'Linux' but it did not change the behavior of kpartx.
  • Result of kpartx
         $ sudo kpartx -av $RELEASE_DIR/dist/images/sdcard.img
         [sudo] password for username:
         add map loop0p2 (253:2): 0 14680001 linear /dev/loop0 63
  • mkfs.*: loop1 part of loop1p1 reference is not appropriate for my system because it is mounting as loop0. Easy to compensate.
  • In the two mkfs.vfat command loop0p1 is not mounted at all just loop0p2.
My specific question is why kpartx won't mount the root partition of sdcard.img?


Results from fdisk -l
Code:
Disk /media/sf_projects/RDP3/XZD_20161231/dist/images/sdcard.img: 16.1 GB, 16106127360 bytes, 31457280 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x322d1bed
                                                      Device Boot      Start         End      Blocks   Id  System
/media/sf_projects/RDP3/XZD_20161231/dist/images/sdcard.img1            2048     2099199     1048576   83  Linux
/media/sf_projects/RDP3/XZD_20161231/dist/images/sdcard.img2         2099200    31457279    14679040   83  Linux

Print this item

  booting from SD card
Posted by: albanbourge - 06-30-2017, 09:55 AM - Forum: Public Support - Replies (5)

Hello everyone,

My question is probably related with http://xzdforums.dornerworks.com/showthread.php?tid=651, but unfortunately, I was not able to make it work with the solution presented there.
When following the tutorial for booting from SD card, I'm stuck a the booting process.
Here is the log.

Code:
Xilinx Zynq MP First Stage Boot Loader
Release 2016.3   Jan  5 2017  -  11:58:09
Platform: Silicon (3.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
Board Configuration successful
Processor Initialization Done
================= In Stage 2 ============
SD1 with level shifter Boot Mode
SD: rc= 0
File name is BOOT.BIN
SD: Unable to open file BOOT.BIN: 3
                                  XFSBL_ERROR_SD_F_OPEN
Boot Device Initialization failed 0x29
================= In Stage Err ============
Fsbl Error Status: 0x0
I thought about a tool version problem and incompatibility between the boot.bin given and the board I have (ZCU102 rev 1.0 ES2) which is not the same from the tutorial I think because the SW6 configuration shown is not the same (must be 0xE, see UG1182). Hence I tried regenerating the boot.bin with newer SDK version. So I did as the tutorial said for generating a new boot.bin with SDK 2017.2 and get exactly the same error.
Next, I tried to use an FSBL generated with SDK 2017.2. So I started a blank project targeting the board and generated an newer fsbl. I next generated the boot.bin with the same procedure and got :
Code:
Xilinx Zynq MP First Stage Boot Loader
Release 2017.2   Jun 30 2017  -  10:53:29
Reset Mode      :       System Reset
Platform: Silicon (3.0), Cluster ID 0x80000000
Running on A53-0 (64-bit) Processor, Device Name: XCZU9EG
Board Configuration successful
Processor Initialization Done
================= In Stage 2 ============
SD1 with level shifter Boot Mode
SD: rc= 0
File name is BOOT.BIN
Multiboot Reg : 0x0
Image Header Table Offset 0x8C0
*****Image Header Table Details********
Boot Gen Ver: 0x1020000
No of Partitions: 0x4
Partition Header Address: 0x440
Partition Present Device: 0x0
Initialization Success
======= In Stage 3, Partition No:1 =======
UnEncrypted data Length: 0x1800
Data word offset: 0x1800
Total Data word length: 0x1800
Destination Load Address: 0xFFFEA000
Execution Address: 0xFFFEA000
Data word offset: 0x76E0
Partition Attributes: 0x116
Partition 1 Load Success
======= In Stage 3, Partition No:2 =======
UnEncrypted data Length: 0x8
Data word offset: 0x8
Total Data word length: 0x8
Destination Load Address: 0xFFFF0000
Execution Address: 0x0
Data word offset: 0x8EE0
Partition Attributes: 0x116
Partition 2 Load Success
======= In Stage 3, Partition No:3 =======
UnEncrypted data Length: 0x22B80
Data word offset: 0x22B80
Total Data word length: 0x22B80
Destination Load Address: 0x8000000
Execution Address: 0x8000000
Data word offset: 0x8EF0
Partition Attributes: 0x116
Partition 3 Load Success
All Partitions Loaded
================= In Stage 4 ============
Protection configuration applied
 ATF running on XCZU9EG/silicon v3/RTL5.1 at 0xfffea000
NOTICE:  BL31: Secure code at 0x0
NOTICE:  BL31: Non secure code at 0x0
NOTICE:  BL31: v1.2(release):2c2b23f
NOTICE:  BL31: Built : 11:58:24, Jan  5 2017


And the console is stuck there. U-boot doesn't show up.

Any idea what I should do ?
Thanks in advance !

Print this item

  XZD Power Management
Posted by: jwolff - 06-27-2017, 06:20 PM - Forum: Public Support - Replies (1)

Hi, I have a few questions about XZD power management.  My goal is to have a configuration in which the full APU-hosted Xen MPSoC system can be suspended to RAM, as described in this Xilinx Wiki page for a Linux-only configuration:
http://www.wiki.xilinx.com/Zynq+UltraSca...nux+Kernel
 
When the APU-hosted Xen system is needed, it would come online much more quickly if it were suspended to RAM than if it needed to boot from scratch.  So, here are my questions:
 
1) Does the Xen kernel provide a "suspend to RAM" option for itself? 
 
2) If this is not supported, then is it possible to suspend dom0 in addition to the domU VMs?  Since the Xen kernel boots up very quickly, then suspending all domains might be a good option.
 
3) Finally, if suspending dom0 and the domUs is possible, can you suspend them to disk (i.e. to non-volatile memory)?  This would allow the APU to be powered off when it is not needed and then boot Xen / restore the VMs more quickly than a normal cold boot.
 
Thanks very much for your help with these questions!

Print this item

  DomU I/O and Communication
Posted by: pello.heriz - 06-19-2017, 07:07 AM - Forum: Public Support - Replies (3)

Hi,

I'm very interested in knowing how to assign specific HW to each one of the running OS-s if I'm working with Xen hypervisor. Is it possible? Where do I need to specify this?

On the other hand, I also would like to know, how would the different OS-s running under Xen hypervisor communicate between them. I.e.: an application running over Linux (i.e.: Docker) and FreeRTOS.

Finally, it would be interesting for me too, to know how to debug the behavior of an OS running under Xen (i.e.: FreeRTOS) in the real MPSoC board.

Any answer would be helpful,

Thanks,
Pello

Print this item

  XZD Yocto Layer
Posted by: Nathan.Studer - 04-12-2017, 03:23 PM - Forum: Knowledge Base - Replies (6)

In preparation for the 2017.1 XZD release, the XZD Yocto Layer has been made publicly available.  This Yocto Layer can currently be used to generate XZD kernel images and root filesystems with the 2016.4 version of XSDK.

The layer and instructions for using it can be found in github at https://github.com/dornerworks/meta-xzd .  A repo manifest which simplifies the process can also be found in github at https://github.com/dornerworks/xzd-yocto-manifests .

     Nate

Print this item

  Yocto image as domU
Posted by: pello.heriz - 04-07-2017, 09:28 AM - Forum: Public Support - Replies (12)

Is it possible to add an image created myself with Yocto as a dom1 or dom2 guest? If the answer is yes, which are the steps I need to follow to add this image as a guest?

Best regards,
Pello

Print this item