This section describes how to connect to your image after you have it running on the S32V board.
Because the default image starts an application immediately, you can connect to it using a console connection via the debug port on the board. You may require the Virtual COM Port (VCP) Driver installed on your system, which allows you to connect to Console on board and see the boot sequence for the board. For more information, Future Technology Devices International Ltd. (FTDI) website at http://www.ftdichip.com/FTDrivers.htm.
Connect to your board using a terminal (Linux or macOS) or console program such as Tera Term or puTTy (Windows). For more information, see the “Set up the hardware” section in the Installation Notes chapter of the NXP S32V234 EVB (TreeRunner) BSP User's Guide.
After you turn press the power button, here's what you should see in your console.
U-Boot 2016.01 (Mar 25 2016 - 16:44:24 +0200), Build: jenkins-u-boot_archive-board=s32v234evb-17
CPU: Freescale Treerunner S32V234 at 1000 MHz
Reset cause: Software Functional reset
Board: s32v234evb
I2C: ready
DRAM: 256 MiB
All (4) cores are up.
MMC: FSL_SDHC: 0
In: serial
Out: serial
Err: serial
Net: FEC
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
reading s32v234-evb.dtb
11359 bytes read in 15 ms (739.3 KiB/s)
reading ifs-s32v-evb.ui
11860516 bytes read in 1059 ms (10.7 MiB/s)
## Booting kernel from Legacy Image at c307ffc0 ...
Image Name:
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 11860452 Bytes = 11.3 MiB
Load Address: c3080000
Entry Point: c3080000
Verifying Checksum ... OK
## Flattened Device Tree blob at c2000000
Booting using the fdt blob at 0xc2000000
XIP Kernel Image ... OK
reserving fdt memory region: addr=c0000000 size=10000
Loading Device Tree to 00000000cfd6c000, end 00000000cfd71c5e ... OK
Starting kernel ...
MMU: 16-bit ASID 40-bit PA TCR_EL1=85180519
GICv2: 224 interrupts
GICv2: routing SPIs to gic cpu 0
cpu0: MPIDR=80000000
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 256K linesz=64 set/way=256/16
cpu0: GICv2 cpu interface 0
Loading IFS...done
System page at phys:0000000080010000 user:ffffff8040202000 kern:ffffff8040201000
Starting next program at vffffff8060057d40
MFLAGS=1
Welcome to QNX Neutrino 7.0 on the s32v EVB Board!!
Starting I2C 1/2/3 driver (/dev/i2c0,2,3)...
Starting SD Card as system disk /dev/sysdisk0...
[00] SIM="SDMMC" HBA="s32v"
[00,0,0] type=00 ver=05 resp=00 SDMMC:
Starting dumper
Waiting for disk before starting screen...
IFS2_ENABLED not set to true, secondary IFS disabled
Starting screen.
sourcing env.sh
Starting SLM...
About to start serial driver
If you want to connect using ssh, in your console connection run ifconfig to determine the IP address. For example:
# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33136
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
rt0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
enabled=0
address: f4:4d:30:68:40:ee
media: Ethernet autoselect (1000baseT full-duplex)
status: active
inet 10.101.10.100 netmask 0xfffffe00 broadcast 10.101.10.255
inet6 fe80::f64d:30ff:fe68:40ee%rt0 prefixlen 64 scopeid 0x11
pflog0: flags=0 mtu 33136
If this IP address is preserved after a reboot, you can use it to connect to the S32V board using ssh. This may be dependent on the policies you have in place in your network. In some cases, it may be easier to assign a static IP address to your S32V board.
Using a terminal (Linux or macOS) or terminal program (Windows), such as puTTY or Tera Term, you can use ssh to connect to the IP address previously determined. You can log in using the user ID and password of root. For example:
# ssh 10.101.10.100
login as: root
root@10.101.10.100's password: