BELK/BXELK Quick Start Guide
< BELK
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
 For BELK 3.0.2 or older, please refer to the BELK Quick Start Guide in PDF format. |
Contents
BELK/BXELK Quick start guide[edit | edit source]
This page describes how to quickly start working with the BELK/BXELK kit. The following paragraphs will guide you through the setup and installation procedures.
Kit registration[edit | edit source]
|
Customers are strongly recommended to register their kits. Registration grants access to reserved material such as source code and additional documentation. To register the kit, please send an email to helpdesk@dave.eu, providing the kit P/N and S/N. If you also wish to access git repositories containing source code, please follow the procedure described here. |
Target setup and first boot[edit | edit source]
This section describes how to quickly start Bora/BoraEVB and BoraX/BoraXEVB systems included in the BELK/BXELK:
- on target side, connect a null-modem cable on J17 DB9 connector, denoted also as UART1
- on host side, connect the other end of the null-modem cable to a COM port and start your favorite terminal software that will be used to interact with the target's serial console; communication parameters are 115200-8-N-1
- optionally connect the BoraEVB/BoraXEVB board to an Ethernet LAN by plugging cable into connector J8, also denoted as ETH0 on BoraEVB and BORAX ETHERNET on BoraXEVB
- connect 12V power supply to JP2 or J7 connector, also denoted as PSU 12V
- insert the microSD card in the slot J21, also denoted as MICROSD.
Once power has been applied to the target, FSBL or U-boot SPL and U-Boot bootloaders will be fetched from the SPI NOR flash that equips Bora/BoraX/BORA Lite SOM and executed. Boot messages will be printed out to the serial console. Redundant U-Boot environment is stored in the NOR flash as well, as depicted in the following image.
By default, U-Boot is configured to retrieve Linux kernel image stored in the microSD card [1]. In turn, Linux kernel shall mount root file system from the mmcblk0p2 partition of the microSD card itself [2], [3]. At the end of boot process, Linux shell shall be available on the serial console. Default boot process does not download any bitstream to the Programmable Logic.
The following dump shows the typical messages printed out to the console during bootstrap process. This log refers to Belk-4.0.0 running on BORA SOM. For BORAX SOM similar messages are printed out to the console.
U-Boot SPL 2017.01-belk-4.0.0 (Jul 11 2017 - 15:58:04)
qspi boot
Trying to boot from SPI
U-Boot 2017.01-belk-4.0.0 (Jul 11 2017 - 15:58:04 +0200), Build: jenkins-BELK_u-boot-10
Model: Bora
Board: Xilinx Zynq
I2C: ready
DRAM: ECC disabled 1 GiB
Relocating to 3ff2e000, new gd at 3eaedee8, sp at 3eaedec0
NAND: 1024 MiB
MMC: sdhci@e0100000: 0 (SD)
SF: Detected s25fl256s_64k with page size 256 Bytes, erase size 64 KiB, total 64 MiB
*** Warning - bad CRC, using default environment
In: serial@e0001000
Out: serial@e0001000
Err: serial@e0001000
Model: Bora
Board: Xilinx Zynq
SF: Detected s25fl256s_64k with page size 256 Bytes, erase size 64 KiB, total 64 MiB
SF: Detected s25fl256s_64k with page size 256 Bytes, erase size 64 KiB, total 64 MiB
SOM ConfigID#: 00000001
SOM UniqueID#: 01234567:89abcdef
ds2431_readmem(): error in chip reset
ds2431_readmem(): error in reading buffer
ds2431_readmem(): error in chip reset
ds2431_readmem(): error in reading buffer
CB ConfigID CRC mismatch for 0x00000000 (was 0x00000000, expected 0x2144df1c) at block 3 (offset 96): using default
CB ConfigID#: ffffffff
CB UniqueID#: 00000000:00000000
Net: ZYNQ GEM: e000b000, phyaddr 7, interface rgmii-id
eth0: ethernet@e000b000
Hit ENTER within 3 seconds to stop autoboot
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
USB device 0: unknown device
** Bad device usb 0 **
switch to partitions #0, OK
mmc0 is current device
reading boot.scr
472 bytes read in 12 ms (38.1 KiB/s)
Running bootscript from mmc ...
## Executing script at 02080000
bootscript generated with command "mkimage -A ARM -T script -C none -n BELK -d bootscript.txt boot.scr"
reading uImage
3770880 bytes read in 642 ms (5.6 MiB/s)
reading bora.dtb
10647 bytes read in 19 ms (546.9 KiB/s)
Booting Bora/BoraX via mmc
## Error: "configid_fixup" not defined
## Booting kernel from Legacy Image at 02080000 ...
Image Name: Linux-4.9.0-belk-4.0.0-xilinx
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3770816 Bytes = 3.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
Loading Kernel Image ... OK
Loading Device Tree to 1effa000, end 1efff996 ... OK
Switching to NAND storage before starting Linux
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.0-belk-4.0.0-xilinx (jenkins@linuxserver2) (gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) ) #1 SMP PREEMPT Sun Jul 9 23:10:22 CEST 2017
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt:Machine model: Bora
[ 0.000000] bootconsole [earlycon0] enabled
[ 0.000000] cma: Reserved 16 MiB at 0x3f000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 262144
[ 0.000000] free_area_init_node: node 0, pgdat c0a2d840, node_mem_map ef7f7000
[ 0.000000] Normal zone: 1536 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 196608 pages, LIFO batch:31
[ 0.000000] HighMem zone: 65536 pages, LIFO batch:15
[ 0.000000] percpu: Embedded 14 pages/cpu @ef7d1000 s26124 r8192 d23028 u57344
[ 0.000000] pcpu-alloc: s26124 r8192 d23028 u57344 alloc=14*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: root=/dev/mmcblk0p2 rootwait rw console=ttyPS0,115200n8 debug earlyprintk
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 1013220K/1048576K available (6144K kernel code, 232K rwdata, 1512K rodata, 1024K init, 323K bss, 18972K reserved, 16384K cma-reserved, 245760K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0700000 (7136 kB)
[ 0.000000] .init : 0xc0900000 - 0xc0a00000 (1024 kB)
[ 0.000000] .data : 0xc0a00000 - 0xc0a3a1a0 ( 233 kB)
[ 0.000000] .bss : 0xc0a3a1a0 - 0xc0a8afb4 ( 324 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 32.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] efuse mapped to f0802000
[ 0.000000] slcr mapped to f0804000
[ 0.000000] L2C: platform modifies aux control register: 0x02060000 -> 0x02460000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x02460000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x46460001
[ 0.000000] zynq_clock_init: clkc starts at f0804100
[ 0.000000] Zynq clock init
[ 0.000000] ps_clk frequency not specified, using 33 MHz.
[ 0.000012] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
[ 0.007870] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
[ 0.018886] Switching to timer-based delay loop, resolution 3ns
[ 0.024887] clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[ 0.033937] timer #0 at f080c000, irq=17
[ 0.038252] Console: colour dummy device 80x30
[ 0.042581] Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
[ 0.053061] pid_max: default: 32768 minimum: 301
[ 0.057843] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.064345] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.071973] CPU: Testing write buffer coherency: ok
[ 0.076890] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.082484] Setting up static identity map for 0x100000 - 0x100058
[ 0.258340] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.258442] Brought up 2 CPUs
[ 0.266979] SMP: Total of 2 processors activated (1333.33 BogoMIPS).
[ 0.273360] CPU: All CPU(s) started in SVC mode.
[ 0.278941] devtmpfs: initialized
[ 0.285288] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.293052] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.303669] pinctrl core: initialized pinctrl subsystem
[ 0.310015] NET: Registered protocol family 16
[ 0.316110] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.358364] cpuidle: using governor ladder
[ 0.398352] cpuidle: using governor menu
[ 0.414905] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.422775] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.428739] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0880000
[ 0.435584] zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
[ 0.455610] vgaarb: loaded
[ 0.458851] SCSI subsystem initialized
[ 0.462817] usbcore: registered new interface driver usbfs
[ 0.468276] usbcore: registered new interface driver hub
[ 0.473587] usbcore: registered new device driver usb
[ 0.479680] pps_core: LinuxPPS API ver. 1 registered
[ 0.484514] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.493700] PTP clock support registered
[ 0.499357] clocksource: Switched to clocksource arm_global_timer
[ 0.520290] NET: Registered protocol family 2
[ 0.525350] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.532409] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.538840] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.545202] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.551082] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.557542] NET: Registered protocol family 1
[ 0.562207] RPC: Registered named UNIX socket transport module.
[ 0.567985] RPC: Registered udp transport module.
[ 0.572752] RPC: Registered tcp transport module.
[ 0.577445] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.583922] PCI: CLS 0 bytes, default 64
[ 0.588414] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.598056] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.604966] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[ 0.612013] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 0.619910] bounce: pool size: 64 pages
[ 0.623630] io scheduler noop registered
[ 0.627583] io scheduler deadline registered
[ 0.631928] io scheduler cfq registered (default)
[ 0.639167] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.645763] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.654861] e0000000.serial: ttyPS1 at MMIO 0xe0000000 (irq = 145, base_baud = 3125000) is a xuartps
[ 0.664307] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 146, base_baud = 3125000) is a xuartps
à[ 0.673432] console [ttyPS0] enabled
[ 0.673432] console [ttyPS0] enabled
[ 0.680527] bootconsole [earlycon0] disabled
[ 0.680527] bootconsole [earlycon0] disabled
[ 0.689751] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to f086f000
[ 0.696648] [drm] Initialized
[ 0.712609] brd: module loaded
[ 0.723100] loop: module loaded
[ 0.728406] libphy: Fixed MDIO Bus: probed
[ 0.735460] CAN device driver interface
[ 0.741807] libphy: MACB_mii_bus: probed
[ 0.840108] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 148 (00:50:c2:1e:af:e0)
[ 0.849977] Micrel KSZ9031 Gigabit PHY e000b000.etherne:07: attached PHY driver [Micrel KSZ9031 Gigabit PHY] (mii_bus:phy_addr=e000b000.etherne:07, irq=-1)
[ 0.864140] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 0.869913] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 0.876782] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.883279] ehci-pci: EHCI PCI platform driver
[ 0.887820] usbcore: registered new interface driver usb-storage
[ 0.894012] e0002000.usb supply vbus not found, using dummy regulator
[ 0.900703] ULPI transceiver vendor/product ID 0x0424/0x0006
[ 0.906275] Found SMSC USB331x ULPI transceiver.
[ 0.910910] ULPI integrity check: passed.
[ 0.916630] mousedev: PS/2 mouse device common for all mice
[ 0.922521] i2c /dev entries driver
[ 0.926190] cdns-i2c e0004000.i2c: 100 kHz mmio e0004000 irq 142
[ 0.933517] rtc-ds3232 0-0068: oscillator discontinuity flagged, time unreliable
[ 0.943182] rtc-ds3232 0-0068: rtc core: registered ds3232 as rtc0
[ 0.950800] ina2xx 0-0041: power monitor ina226 (Rshunt = 10000 uOhm)
[ 0.959126] Xilinx Zynq CpuIdle Driver started
[ 0.964011] sdhci: Secure Digital Host Controller Interface driver
[ 0.970180] sdhci: Copyright(c) Pierre Ossman
[ 0.974447] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.039420] mmc0: SDHCI controller on e0100000.sdhci [e0100000.sdhci] using DMA
[ 1.047063] usbcore: registered new interface driver usbhid
[ 1.053610] usbhid: USB HID core driver
[ 1.060557] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xd3
[ 1.066828] nand: AMD/Spansion S34ML08G1
[ 1.070797] nand: 1024 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.079104] Bad block table found at page 524224, version 0x01
[ 1.086183] Bad block table found at page 524160, version 0x01
[ 1.092800] 8 ofpart partitions found on MTD device pl35x-nand
[ 1.098568] Creating 8 MTD partitions on "pl35x-nand":
[ 1.103708] 0x000000000000-0x000000040000 : "nand-SPL"
[ 1.120695] 0x000000040000-0x000000100000 : "nand-uboot"
[ 1.137009] 0x000000100000-0x000000140000 : "nand-uboot-env1"
[ 1.153846] 0x000000140000-0x000000180000 : "nand-uboot-env2"
[ 1.160646] mmc0: new SDHC card at address 0001
[ 1.165619] mmcblk0: mmc0:0001 SD16G 14.6 GiB
[ 1.170685] 0x000000180000-0x000000780000 : "nand-bitstream"
[ 1.177693] 0x000000780000-0x000000800000 : "nand-device-tree"
[ 1.183599] mmcblk0: p1 p2
[ 1.194709] 0x000000800000-0x000001000000 : "nand-linux"
[ 1.211164] 0x000001000000-0x000020000000 : "nand-rootfs"
[ 1.232466] NET: Registered protocol family 17
[ 1.236842] can: controller area network core (rev 20120528 abi 9)
[ 1.243084] NET: Registered protocol family 29
[ 1.247450] can: raw protocol (rev 20120528)
[ 1.251720] can: broadcast manager protocol (rev 20161123 t)
[ 1.257345] can: netlink gateway (rev 20130117) max_hops=1
[ 1.263160] Registering SWP/SWPB emulation handler
[ 1.274219] rtc-ds3232 0-0068: hctosys: unable to read the hardware clock
[ 1.283162] EXT4-fs (mmcblk0p2): mounting ext3 file system using the ext4 subsystem
[ 1.592447] random: fast init done
[ 1.748727] EXT4-fs (mmcblk0p2): recovery complete
[ 1.756780] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 1.764840] VFS: Mounted root (ext3 filesystem) on device 179:2.
[ 1.775504] devtmpfs: mounted
[ 1.781627] Freeing unused kernel memory: 1024K (c0900000 - c0a00000)
INIT: version 2.88 booting
Starting udev
[ 2.706500] udevd[702]: starting version 3.2
[ 2.771034] udevd[703]: starting eudev-3.2
[ 2.915949] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Mon Jul 3 00:01:52 UTC 2017
INIT: Entering runlevel: 5
Configuring network interfaces... udhcpc (v1.24.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
done.
Starting system message bus: dbus.
Starting Dropbear SSH server: dropbear.
Starting rpcbind daemon...done.
starting statd: done
exportfs: can't open /etc/exports for reading
NFS daemon support not enabled in kernel
Starting syslogd/klogd: done
Starting internet superserver: xinetd.
* Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
...done.
Starting tcf-agent: OK
Poky (Yocto Project Reference Distro) 2.2.1 bora /dev/ttyPS0
bora login:
[1] bootscript is used to do this task.
[2] This root file system has been generated by Yocto build system.
[3] The microSD card is bootable itself, as explained here.
Host setup and target software development[edit | edit source]
Please refer to this page.
Target configuration for the development stage (net_nfs)[edit | edit source]
|
The default BELK/BXELK Virtual Machine network configuration is using NAT: this allows to accessing external network (i.e. Internet) using the host computer's networking connection.
For software development using |
During the development stage, the target is usually connected via Ethernet LAN to the host machine and is configured to:
- retrieve binary images (i.e. Linux kernel) via TFTP protocol
- mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted here. An example of Bridge mode configuration can be found here
In DAVE Embedded Systems development kits, this configuration is generally denoted as net_nfs. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up.
For more information about how to set up and use TFTP and NFS servers, please refer to the following link Booting the system via nfs.
Target configuration for standalone boot[edit | edit source]
Please refer to this page.
Recovery procedure[edit | edit source]
In case the target is not able to boot from NOR or NAND flash for any reason, this recovery procedure can be use to boot from microSD card.
