Boot board
Preparing the microSD to boot the boardsection in this chapter for more information.
Note:
To enable booting the system from the microSD card, you
need create a DOS FAT32 partition (type 12) on the card.
For information about preparing a bootable microSD card,
see the Prepare a bootable microSD
in this chapter.
- Connect a USB cable from your Xilinx KR260 target board to your host system.
- On your host machine, start your favorite terminal program with these settings:
- Baud rate: 115200
- Data: 8 bit
- Parity: none
- Stop: 1 bit
- Flow control: none
- Connect the Xilinx KR260 board to the power supply. To reset the board, press the reset button SW2.
- After the power is turned on, output from FSBL appears terminal console. FSBL will load U-Boot, and U-Boot will load QNX IFS from the microSD.
# Zynq MP First Stage Boot Loader starting USB... Bus usb@fe200000: Register 2000440 NbrPorts 2 Starting the controller USB XHCI 1.00 Bus usb@fe300000: Register 2000440 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus usb@fe200000 for devices... 5 USB Device(s) found scanning bus usb@fe300000 for devices... 4 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Hit any key to stop autoboot: 0 SMK-K26-XCL2G: No match model=SMK-K26-XCL2G Device 0: Vendor: Generic Rev: 1.98 Prod: Ultra HS-COMBO Type: Removable Hard Disk Capacity: 15193.5 MB = 14.8 GB (31116288 x 512) ... is now current device Scanning usb 0:1... Found U-Boot script /boot.scr 1447 bytes read in 6 ms (235.4 KiB/s) ## Executing script at 20000000 12990920 bytes read in 865 ms (14.3 MiB/s) 45038 bytes read in 8 ms (5.4 MiB/s) ## Booting kernel from Legacy Image at 00100000 ... Image Name: Created: 2024-08-23 5:40:32 UTC Image Type: AArch64 Linux Kernel Image (uncompressed) Data Size: 12990856 Bytes = 12.4 MiB Load Address: 00100000 Entry Point: 00100000 Verifying Checksum ... OK ## Flattened Device Tree blob at 40000000 Booting using the fdt blob at 0x40000000 Working FDT set to 40000000 Loading Kernel Image Loading Device Tree to 000000000fff2000, end 000000000fffffed ... OK Working FDT set to fff2000 Starting kernel ... Xilinx KR260 starter kit board startup Hypervisor support disabled MMU: 16-bit ASID 40-bit PA TCR_EL1=00000012b5183519 GICv2: 192 interrupts GICv2: routing SPIs to gic cpu 0 cpu0: MPIDR=0000000080000000 cpu0: MIDR=410fd034 Cortex-A53 r0p4 cpu0: CWG=4 ERG=4 Dminline=4 Iminline=4 VIPT cpu0: CLIDR=a200023 LoUU=1 LoC=2 LoUIS=1 cpu0: L1 Icache 32K linesz=64 set/way=256/2 cpu0: L1 Dcache 32K linesz=64 set/way=128/4 cpu0: L2 Unified 1024K linesz=64 set/way=1024/16 cpu0: GICv2 cpu interface 0 Loading IFS...decompressing...done cpu1: MPIDR=0000000080000001 cpu1: MIDR=410fd034 Cortex-A53 r0p4 cpu1: CWG=4 ERG=4 Dminline=4 Iminline=4 VIPT cpu1: CLIDR=a200023 LoUU=1 LoC=2 LoUIS=1 cpu1: L1 Icache 32K linesz=64 set/way=256/2 cpu1: L1 Dcache 32K linesz=64 set/way=128/4 cpu1: L2 Unified 1024K linesz=64 set/way=1024/16 cpu1: GICv2 cpu interface 1 cpu2: MPIDR=0000000080000002 cpu2: MIDR=410fd034 Cortex-A53 r0p4 cpu2: CWG=4 ERG=4 Dminline=4 Iminline=4 VIPT cpu2: CLIDR=a200023 LoUU=1 LoC=2 LoUIS=1 cpu2: L1 Icache 32K linesz=64 set/way=256/2 cpu2: L1 Dcache 32K linesz=64 set/way=128/4 cpu2: L2 Unified 1024K linesz=64 set/way=1024/16 cpu2: GICv2 cpu interface 2 cpu3: MPIDR=0000000080000003 cpu3: MIDR=410fd034 Cortex-A53 r0p4 cpu3: CWG=4 ERG=4 Dminline=4 Iminline=4 VIPT cpu3: CLIDR=a200023 LoUU=1 LoC=2 LoUIS=1 cpu3: L1 Icache 32K linesz=64 set/way=256/2 cpu3: L1 Dcache 32K linesz=64 set/way=128/4 cpu3: L2 Unified 1024K linesz=64 set/way=1024/16 cpu3: GICv2 cpu interface 3 System page at phys:0000000000015000 user:ffffff8040208000 kern:ffffff8040204000 Starting next program at vffffff8060077740 syspage::hypinfo::flags=0x00000000 Welcome to QNX 8.0.0 on Xilinx_MPSoC_KR260_starter_board ! Starting clock manager... Starting I2C driver ... Setting OS clock from RTC ... Starting serial driver (/dev/ser1) Starting RAM block driver ... Starting QSPI NOR flash driver... Starting USB host driver ... Path=0 - target=0 lun=0 Direct-Access(0) - ram Rev: Starting devb-umass ... Starting devf-ram filesystem ... Starting networking ... Starting DHCP client ... Starting SSH daemon ... Starting devc-pty manager ... Starting qconn daemon ... Starting shell ... #
You should now be able to test the OS by executing any shell command, or any command residing within the QNX IFS image. For example: ls or uname -a.
Page updated: