Boot board

The followings steps describe how to boot board from your microSD. Before you can complete these steps, you must prepare the microSD. For more information, see the Preparing the microSD to boot the board section 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.

  1. Connect a USB cable from your Xilinx KD240 target board to your host system.
  2. 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
  3. Connect the Xilinx KD240 board to the power supply. To reset the board, press the reset button SW2.
  4. 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
    Release 2023.2   Oct 12 2023  -  15:51:06
    MultiBootOffset: 0x1F0
    Reset Mode      :       System Reset
    Platform: Silicon (4.0), Running on A53-0 (64-bit) Processor, Device Name: XCZUUNKNEG
    QSPI 32 bit Boot Mode
    FlashID=0x20 0xBB 0x20
    â–’NOTICE:  BL31: Non secure code at 0x8000000
    NOTICE:  BL31: v2.8(release):xlnx_rebase_v2.8_2023.2_ksb_aug
    NOTICE:  BL31: Built : 12:21:43, Aug 31 2023
    
    
    U-Boot 2023.01 (Sep 21 2023 - 11:02:37 +0000)
    
    CPU:   ZynqMP
    Silicon: v3
    Chip:  xck24
    Detected name: zynqmp-smk-k24-xcl2g-revB-sck-kd-g-revB
    Model: ZynqMP KD240 revA/B/1
    Board: Xilinx ZynqMP
    DRAM:  2 GiB
    PMUFW:  v1.1
    Xilinx I2C FRU format at nvmem0:
     Manufacturer Name: XILINX
     Product Name: SMK-K24-XCL2G
     Serial No: XFL1EDU4SDU1
     Part Number: 05128-01
     File ID: 0x0
     Revision Number: B
    Xilinx I2C FRU format at nvmem1:
     Manufacturer Name: XILINX
     Product Name: SCK-KD-G
     Serial No: XFL1G2KXULVN
     Part Number: 5130-01
     File ID: 0x0
     Revision Number: B
    EL Level:       EL2
    Secure Boot:    not authenticated, not encrypted
    Core:  132 devices, 33 uclasses, devicetree: board
    NAND:  0 MiB
    MMC:
    Loading Environment from nowhere... OK
    In:    serial
    Out:   serial
    Err:   serial
    Bootmode: QSPI_MODE
    Reset reason:   SOFT
    Net:   ADIN1300 PHY detected at addr 8
    
    ZYNQ GEM: ff0c0000, mdio bus ff0c0000, phyaddr 8, interface rgmii-id
    
    Warning: ethernet@ff0c0000 MAC addresses don't match:
    Address in ROM is               ff:ff:ff:ff:ff:ff
    Address in environment is       00:0a:35:15:93:73
    eth0: ethernet@ff0c0000
    starting USB...
    Bus usb@fe200000: Register 2000440 NbrPorts 2
    Starting the controller
    USB XHCI 1.00
    scanning bus usb@fe200000 for devices... 5 USB Device(s) found
           scanning usb for storage devices... 1 Storage Device(s) found
    Enable permission for node ID 33
    Enable permission for node ID 47
    Hit any key to stop autoboot:  0
    model=SMK-K24-XCL2G
    
    Device 0: Vendor: Generic  Rev: 1.98 Prod: Ultra HS-COMBO
                Type: Removable Hard Disk
                Capacity: 30436.5 MB = 29.7 GB (62333952 x 512)
    ... is now current device
    Scanning usb 0:1...
    Found U-Boot script /boot.scr
    1104 bytes read in 6 ms (179.7 KiB/s)
    ## Executing script at 20000000
    13071160 bytes read in 867 ms (14.4 MiB/s)
    ## Booting kernel from Legacy Image at 00100000 ...
       Image Name:
       Created:      2024-08-30   9:20:14 UTC
       Image Type:   AArch64 Linux Kernel Image (uncompressed)
       Data Size:    13071096 Bytes = 12.5 MiB
       Load Address: 00100000
       Entry Point:  00100000
       Verifying Checksum ... OK
    ## Flattened Device Tree blob at 7b8143f0
       Booting using the fdt blob at 0x7b8143f0
    Working FDT set to 7b8143f0
       Loading Kernel Image
       Loading Device Tree to 000000000fff2000, end 000000000ffff960 ... OK
    Working FDT set to fff2000
    
    Starting kernel ...
    
    Xilinx KD240 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_KD240_board !
    
    Starting clock manager...
    Starting I2C driver ...
    Setting OS clock from RTC ...
    Starting CAN driver...
    Starting serial driver (/dev/ser2)
    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: