TECHNICAL NOTE

JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

Introduction
This document describes how to get the CM startup serial log via BIM.

We found there were several cases in which the not defective core modules (CM) were replaced in the
past based on our inspection at our lab. Getting and investigating the CM startup serial log could
investigate the CM status in detail when it was stopped, and it can be avoided to replace the not
broken CM replaced.

Remote Access

Management

MGMT

BDE Inmarsat
Support
BIM (acu) GX Web Router
http://acu:9443

ON/OFF Port 9001

Power Ethernet Serial

INSD

CM (modem) CM Web INSD Desktop

https://modem
172.29.30.1

Service Port

Service
Engineer
PC
172.29.30.2
Tight VNC

Fi.1 Work conceptual diagram

Notes
・For Fleet Edge, the IP address is different from INSD. The execution folder
of the batch file is also different, so please refer to page 3 for details.

Page 1/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

Preparation
Required tools
PC (only visit vessel)
Not required when requesting remote work to
Inmarsat Support due to accessible INSD directly

TightVNC (only visit vessel for Cab-B, Cab-C)

Batch file for automatic getting CM log

provide file： GetCMlog.zip （4MB）

including PuTYY of terminal software

Processing details of batch

The batch file automatically performs the following processing.
① Start PuTTY software
② Connect to CM serial port 9001 via BIM
③ Start log record
④ Turn on the power of the CM again and wait for the CM to start.
⑤ End log saving at the same time as PuTTY close.

Notes
• Do not use this batch file for anything other than failure analysis work.

• Delete all files and folder after work

• Do not provide this batch file to a third person.

Page 2/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

Procedure
1. Connect to PC
1-1. prepare
1）For Service Engineer (For Cab-B or Cab-C )
Connect own PC to the Service Port of FX rack and connect using TightVNC software.
For more information, see Appendix-A “Accessing INSD desktop”.

2) For Service Engineer (For Fleet Edge)

Connect own PC to the Service Port of FX rack and open the Fleet Edge
WebUI(192.168.168.170) by the browser.

3) For Inmarsat Support

No required TightVNC software.

1-2. Get the Lookback IP address (For Fleet Edge)

Open the menu “Service -> System INFO “ on Fleet edge Web UI.
Record the lookback IP address.

2. Get CM log:
2-1. Click windows explorer and copy the compressed file (GetCMlog.zip).
No specific path is specified but use a temporary folder easy to delete after work.
For FleetEdge remote access, it should be copied to the FleetServer folder.

2-2. The following files will be displayed when the zip file is unziped.

Page 3/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

Notes
• Use “getcmlog_from_INSD.bat” when working from the INSD desktop.
• “getcmlog_from_PC.bat” is provided for users that directly connect the BDE's MGMT
port, but be sure to restore the wiring if unplugged a LAN cable.

2-3. modify the batch file ( For Fleet Edge)

Open the file “getcmlog_from_Fleetedge.bat” by Notepad.
Rewrite the “0.0.0.0” part in the first line to the IP address recorded in 1-2.

2-4. execute the batch file

Double-click the batch file to execute the program.

(For Cab-B or Cab-C) getcmlog_from_INSD.bat

(For Fleet Edge) getcmlog_from_FleetEdge.bat

PuTTY will start automatically and the following screen will appear.

2-5. The CM will be powered off again and a boot message will appear.
“coremodule.log” file will appear where the message has stopped.
However, the file has not been saved yet at this time.

Page 4/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

2-6. Click the “x button” on the upper right to close PuTTY.

Click the “OK button” in the exit confirmation message to save the log file.

Page 5/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

2-7. Extract the log file.

Please rename the file to be submitted with the vessel name and date.

File name example: Vesselname_YYMMDD_coremodule.log

2-8. Delete all working folders after completing the work.

3. Ethernet Connection Check:

Launch a command prompt with a windows accessory and check the ping response.

1) For Cab-B or Cab-C

ping modem

2) For Fleet Edge

nothing

3) When connecting directly to BDE

ping 192.168.1.1

4. Other Check:
Other confirmation work will be instructed separately depending on the analysis status.

Page 6/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

Checking the log

The checking points of the CM startup log are described.
Basically, JRC will check the log and give instructions, but the main points are listed for reference.

Cases that can be judged from the log

No. Booting step Failure status Instruction Check
mark
1 Board Tests ・No serial log is output Replacing board
・Overall Board Tests: FAIL
2 U-Boot ・Stop in mid-flow TBD
(Linux-OS) ・Watchdog Reset Detected
・Error 4098 FSL_ESDHC_COM_ERR
・Error 4099 FSL_ESDHC_CTOE_ERR
3 Falcon TBD
(Modem-App)

Cases that comprehensive judgment is required including subsequent operations

No. Failure status Instruction Check
mark
1 No connect to ethernet Factory Reset
（no response by ping） ↓
Replacing board
2 OTC fails Check the cable
Re-trial OTC (telnet 0 log)

3 OTC is not start Delete OTC file → Re-trial OTC

Refer to「JUE-60GX_SY07_How_to_FactoryReset_
iDirect_CM.pdf」
4 Not being “IN_NETWORK” Check registration (TPK) with Inmarsat
status when first equipped Change configuration file
Factory reset → Reload configuration files
5 Repeat status Re-trial OTC
”IN_NETWORK” Change configuration file
and “OUT_NETWORK” Factory reset → Reload configuration files

Page 7/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

Appendix
A Accessing INSD desktop
Accessing the INSD
1. Connect your computer to the RJ45 extension (Dell port 2) and use the following IP settings on your
laptop:

INSD
Service PC
Port

IP: 172.29.30.2/3
Mask: 255.255.255.252
GW: 172.29.30.1

2. By using VNC you can now access the INSD.

TightVNC can be downloaded here: http://www.tightvnc.com/

Remote Host: 172.29.30.1::5900

Password: 5ev5@t

Page 8/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

3. INSD Desktop is displayed.

4. Click the windows tab button on tightvnc window.

Page 9/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

B Startup message example

It shows how to monitor CM startup message with PuTTY.

Fig.B-1
PuTTY Configuration

Fig.B-2
iDirectCM login
User name: root
Password: P@55w0rd!

Page 10/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

Fig.B-3
Boot is paused

Fig.B-4
Board Test PASS

Fig.B-5
Boot Complete

Page 11/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

Startup log example: The message will differ depending on board revision.

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2022.03.11 In: serial

14:05:55 =~=~=~=~=~=~=~=~=~=~=~= Out: serial
・・煇 Err: serial
Net:
Bootloader version: master-24
Initiating Power On Self Test (POST) Level 0 Match phy_info Id 4a2 phy_info_shift 4a2
PASS: Testing CPU Memory Interface Speed: 100, full duplex
Initiating Power On Self Test (POST) Level 1 eTSEC1
PASS: BIST FPGA Load Enter three spaces to stop autoboot: 1
PASS: Testing Power Supplies 256 KiB ACFL at 0:1 is now current device
PASS: Testing CPU I2C Interface 256 KiB ACFL at 0:1 is now current device
PASS: Testing CPU SPI Interface Mac Address: 00:60:43:65:78:d8
PASS: Testing CPU MII Interface PPI: No update required
PASS: Testing CPU-NOR Local Bus Interface
Initiating Power On Self Test (POST) Level 2 U-Boot Ver 3.2
PASS: Testing FPGA Software Interface Device: FSL_ESDHC
PASS: Testing CPU-FPGA Local Bus Interface Manufacturer ID: 9
PASS: Testing CPU-FPGA PCIe Bus Interface OEM: 4150
PASS: Testing FPGA Memory Interface Name: AF UD
PASS: Testing FPGA SPI Interface Tran Speed: 25000000
PASS: Testing FPGA I2C Interface Rd Block Len: 512
PASS: Testing Modem Clocks SD version 2.0
PASS: Testing LNB Controller Interface High Capacity: No
Capacity: 1000341504
*************************** Bus Width: 1-bit
Overall Board Tests: PASS Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
*************************** ---------------------------+-2654793 bytes read
Loading file "/boot/gxbdu.dtb" from mmc device 0:2 (xxa2)
---------------------------------9492 bytes read
U-Boot 2009.11 (Sep 07 2017 - 01:37:31), Build: Watch Dog Timer set to timeout in 120 sec
jenkins-Embedded-ERT-kernel-vel-1.5.0-25 ## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-2.6.35
CPU0: P1020, Version: 1.1, (0x80e40011) Created: 2019-06-21 14:50:19 UTC
Core: E500, Version: 5.1, (0x80212051) Image Type: PowerPC Linux Kernel Image (gzip compressed)
Clock Configuration: Data Size: 2654729 Bytes = 2.5 MB
CPU0:800 MHz, CPU1:800 MHz, Load Address: 00000000
CCB:266.667 MHz, Entry Point: 00000000
DDR:333.333 MHz (666.667 MT/s data rate) Verifying Checksum ... OK
(Asynchronous), LBC:66.667 MHz ## Flattened Device Tree blob at 00c00000
L1: D-cache 32 kB enabled Booting using the fdt blob at 0xc00000
I-cache 32 kB enabled Uncompressing Kernel Image ... OK
Board: P1020RDB setup_arch: bootmem
I2C: ready mpc85xx_rdb_setup_arch()
SPI: ready setup_pci_atmu
DRAM: Configuring DDR for 666.667 MT/s data rate setup_one_atmu
CPU Memory Type: 02 DDR Size: 536870912 setup_pci_atmu
DDR: 512 MB setup_one_atmu
Now running in RAM - U-Boot at: 1ff30000 arch: exit
FLASH: 8 MB
L2: 256 KB already enabled pci 0001:01:00.0: ignoring class b20 (doesn't match header type 01)
MMC: Disable 4 Bit Support Attempting to bring link up
Disable High Speed Mode PCI express link up
Disable Multiblock Support Attempting to bring link up
FSL_ESDHC: 0 PCI express link up
eTSEC2 is in sgmii mode. fsl-lbc ffe05000.localbus: address did not match any chip selects
eTSEC3 is in sgmii mode. INIT: version 2.85 booting
/etc/init.d/rcS:INIT: Entering runlevel: 3
PCIE2: disabled Starting network
PCIE1 connected to Slot 2 as Root Complex (base addr run-parts: /etc/network/if-pre-up.d: No such file or directory
ffe0a000) run-parts: /etc/network/if-up.d: No such file or directory
Scanning PCI bus 01 Activating swap.
01 00 1172 0004 ff00 00 Mounting local filesystems...
PCIE1 on bus 00 - 01 Mounting local filesystems...
mount: according to /proc/mounts, proc is already mounted on /proc
File Systems Mounted from /etc/fstab:
rootfs on / type rootfs (rw)

Page 12/13
TECHNICAL NOTE
JUE-60GX_SY09_How_to_get_CM_serial_log_via_BIM August 2022 Edition 3

/dev/root on / type Creating

ext3 scpc-fp-rx at 233:32
(rw,sync,noatime,errors=continue,user_xattr,barrier=0,data=writebac
Creating tx-hpq at 233:33
k) Creating rcs-mac at 233:34
proc on /proc type proc (rw,relatime) Creating ipc-rx at 233:35
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620) Creating ipc-tx at 233:36
sysfs on /sys type sysfs (rw,relatime) Creating fpga-max-minor at 233:37
tmpfs on /var type tmpfs (rw,relatime,size=10240k) Creating nat-if at 233:38
tmpfs on /tmp type tmpfs (rw,relatime,size=4096k) Creating gtimer at 233:39
tmpfs on /squid type tmpfs (rw,relatime,size=16384k) Creating test-upipe at 233:40
/dev/mmcblk0p7 on /common type ext3 ip-demux at 233:41
Creating
(rw,sync,noatime,errors=continue,user_xattr,barrier=0,data=writebac
Creating lan-tunnel at 233:42
k) Creating ota-tunnel at 233:43
/dev/mtdblock0 on /sysopt type jffs2 (rw,sync,noatime) calibration file version: <!-- Software: S0000626 1.1.0.0 -->
none on /dev/shm type tmpfs (rw,nosuid,noexec,relatime,size=4k)
rootfs on / type rootfs (rw) sh: Software:: unknown operand
/dev/root on / type ext3
cpld version = 37
(rw,sync,noatime,errors=continue,user_xattr,barrier=0,data=writebac
Build No. 167 Built by jenkins on Fri Jun 21 15:55:03 UTC 2019
k)
proc on /proc type proc (rw,relatime) current partition: /dev/mmcblk0p2 /
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620) Starting Falcon
sysfs on /sys type sysfs (rw,relatime) 10
tmpfs on /var type tmpfs (rw,relatime,size=10240k) Starting falcon iDirect Falcon built from
tmpfs on /tmp type tmpfs (rw,relatime,size=4096k) /builds/release/vel-1.6.1/nuevo/control/apps/falcon/falcon.cpp at
tmpfs on /squid type tmpfs (rw,relatime,size=16384k) Jun 21 2019:15:22:42
/dev/mmcblk0p7 on /common type MssgBuf::init()
ext3 - using buf pool mutex protection=no
SetDateTime - Set Terminal time to date_time_file(sysopt) [date -s
(rw,sync,noatime,errors=continue,user_xattr,barrier=0,data=writebac
k) 2021.12.17-05:16:15]
/dev/mtdblock0 on /sysopt type jffs2 (rw,sync,noatime) Fri Dec 17 05:16:15 UTC 2021
WARNING: x509_CaHandler::VerifyLocalPKI - certificate common
none on /dev/shm type tmpfs (rw,nosuid,noexec,relatime,size=4k)
Starting system log daemon: syslogd klogd. name NOT MATCH!
starting /usr/sbin/sshd... ¥c [OK]
done. Starting falcon_monitor [OK]
Stopping Wd Timer
Watchdog Timer is stopped Welcome to the iDirect Core Module [ Approot ] System.
Creating device tree Branch: release/vel-1.6.1 Version: 1.6.1.8 Build: 167 on build server
Creating null-layer at 233:0 jenkins
Creating stk-control at 233:1
Creating tdma-shim at 233:2 iDirectCM login: Attempting to bring link up
Creating scpc-shim at 233:3 PCI express link up
Creating hw-ll at 233:4 Attempting to bring link up
Creating link at 233:5 PCI express link up
Creating enc at 233:6 Attempting to bring link up
Creating dist-chop at 233:7 PCI express link up
Creating sat-if at 233:8 Attempting to bring link up
Creating hdr-comp at 233:9 PCI express link up
Creating udp-payload-compress at 233:10
Creating tcp-accel at 233:11 Welcome to the iDirect Core Module [ Approot ] System.
Creating ip-mux at 233:12 Branch: release/vel-1.6.1 Version: 1.6.1.8 Build: 167 on build server
Creating classifier at 233:13 jenkins
Creating fpga-min-minor at 233:14
Creating fpga-tx at 233:15 iDirectCM login: root
Creating fpga-rx1 at 233:16 Password:
Creating fpga-rx2 at 233:17 Login incorrect
Creating scpc-tx at 233:18 iDirectCM login: iDroot
Creating scpc-rx at 233:19 Password:
Creating scpc-sof at 233:20 Login incorrect
Creating scpc-btp at 233:21 iDirectCM login:
Creating scpc-btp-rx1 at 233:22
Creating scpc-btp-rx2 at 233:23
Creating tdma-tx at 233:24
Creating tdma-rx1 at 233:25
Creating tdma-rx2 at 233:26
Creating tdma-btp-req at 233:27
Creating tdma-tx-sof at 233:28
Creating tdma-btp at 233:29
Creating nios-mem at 233:30
Creating mcd-int at 233:31

Page 13/13