CV Shashank Nigam

Ed.
00
Method of Procedure
LTE eNB UAMA/L9CA SW Fusion
MOP-23
Date of Release: 31-July-14
Prepared By: Mr. Manish Singh
Reviewed By: Mr. Hiren Joshi
1|P a g e
NEO eNB Part (R4G Project)

© SAMSUNG Electronics Co., Ltd.
LTE eNB UAMA/L9CA SW Fusion / Ed 00
COPYRIGHT
This manual is proprietary to SAMSUNG Electronics Co., Ltd. and is protected by copyright.
No information contained herein may be copied, translated, transcribed or duplicated for any commercial
purposes or disclosed to the third party in any form without the prior written consent of SAMSUNG
Electronics Co., Ltd.
TRADEMARKS
Product names mentioned in this manual may be trademarks and/or registered trademarks of their
respective companies.
2|P a g e

Document History
Edition Date of Issue Author Remarks
00 31-July-14 Manish Singh New Document
3|P a g e

Table of Contents
LTE eNB UAMA/L9CA SW Fusion MOP 5

1) Case-1: Booter is working fine, able to Login to eNB through EDBG port…………….6
2) Case-2: Booter is working fine but unable to login through EDBG port………………..8
3) Case-3: Booter is not OK and unable to login through EDGB port…………………….11
4) Appendix: Setting up the TFTP Server…………………………...…………………….15
4|P a g e

LTE eNB UAMA/L9CA SW Fusion MOP / Ed 00
LTE eNB UAMA/L9CA SW Fusion MOP

LTE eNB UAMA/L9CA SW fusion MOP can be used for Local Firmware upgrade of
eNB and Troubleshooting the Remote Firmware upgrade failure due to backhaul or
Power fluctuation failure (etc.).In the case of Firmware upgrade failure, eNB cannot be
accessed remotely.
So this MOP can be used for Firmware fusion of eNB Locally and applies for UAMA and
L9CA board.
Firmware files can be fused on UAMA and L9CA locally by two ports present on
UAMA/L9CA Board. One is DBG port(Serial Port) and another is EDBG Port(RJ45) Port as
shown in below picture.
L9CA DBG Port

L9CA EDBG Port
UAMA DBG Port

UAMA EDBG Port
Note:
 Booter prompt can be accessed through DBG port of UAMA/L9CA.
 Normal Firmware upgrade can be done through EDBG Port.
To troubleshoot the Firmware fusion issues, fault can be categorized as below.
 Case-1: Booter is working fine, able to Login to eNB through EDBG port.
 Case-2: Booter is working fine but unable to login through EDBG port.
 Case-3: Booter is not OK and unable to login through EDGB port.
© SAMSUNG Electronics Co., Ltd. page 5 of 15

Case-1
Description: Booter is working fine, able to Login to eNB through EDBG port.
Prerequisite:
 FileZilla and Tera Term software must be installed on the Local PC.
 Latest eNB Firmware file must be copied on Local PC.
Procedure:
1) Connect the RJ45 cable on EDBG port of eNB and Login by using Tera Term.
2) Check the current Firmware file version of eNB by command gettail 0.
3) Open the Filezilla, put the EDGB port IP (192.168.32.27) and Username(root) and
Password(123qwe).
4) Put below latest Firmware files to root folder of eNB by Filezilla.

 booter.enb_uama.0
 kernel.enb_uama.0
 rfs.enb_uama.0
 rfs_raw.enb_uama.0
5) Run the chmod 777 FW_File_name for all above files to change the read write authority of files.
root@UAMA:/root> chmod 777 booter.enb_uama.0
root@UAMA:/root> chmod 777 kernel.enb_uama.0
root@UAMA:/root> chmod 777 rfs.enb_uama.0
root@UAMA:/root> chmod 777 rfs_raw.enb_uama.0
root@UAMA:/root> ls -ltr
total 34259
-rwxrwxrwx 1 root root 443884 Jul 31 14:23 booter.enb_uama.0
-rwxrwxrwx 1 root root 2314116 Jul 31 14:23 kernel.enb_uama.0
-rwxrwxrwx 1 root root 11643054 Jul 31 14:24 rfs.enb_uama.0
-rwxrwxrwx 1 root root 20535680 Jul 31 14:24 rfs_raw.enb_uama.0
6|P a g e

6) Then execute the below command one by one for each file for firmware fusion.
 root@UAMA:/root> flashupdate.sh -b booter.enb_uama.0
 root@UAMA:/root> flashupdate.sh -k kernel.enb_uama.0
 root@UAMA:/root> flashupdate.sh -r rfs.enb_uama.0
 root@UAMA:/root> flashupdate.sh -raw rfs_raw.enb_uama.0
7) After running this command Firmware fusion will get complete.

8) Reboot the eNB and check the Final Firmware version by gettail 0 command.
9) Same procedure will be followed for L9CA Firmware upgrade.Below are the file list for L9CA.
 booter.enb_l9ca_b4f.0;
 kernel.enb_l9ca_b4t.0
 rfs.enb_l9ca_b4t.0
 rfs_raw.enb_l9ca_b4t.0
7|P a g e

Case-2
Description: Booter is working fine but unable to login through EDBG port.
Prerequisite:
 Latest eNB Firmware file must be copied on Local PC.
 TFTP server software must be installed on Local PC.
 eNB debug cable(Serial Cable).
Procedure:
1) Fusing through TFTP, EDBG port

Fusing through the TFTP can be done only when the Booter is proper& IP connectivity to EDBG port is
Up.
Debugging path
Flash Image
Downloadpath
DBG EDBG LAN
(USB) (RJ45) (RJ45)
Serial
(RS232) Local PC
2) Setting up a TFTP server

 Assign the IP 10.254.205.128 and Sub Mask 255.255.255.0 to the Local PC.
 Open the tftpd32.exe software.
 Change current directory to where flash images for UAMA are located
8|P a g e

Above window is displayed, after configuration is done
3) Connect the serial cable on eNB at DBG port and another end at Local
PC.
 Open the Tera Term software and selct the serial option.
 Then click on Setup ->>Serial Port.
 Select the baudrate to 115200 and Press Ok.
 Connect the RJ45 cable to Local PC and another end of cable at EDBG port of eNB.
4) Reboot the Board by pressing the RST button on it.

5) Enter into the booter prompt by continuously pressing the Ctrl+C.
Note: Procedure for entering into boot prompt for UAMA and L9CA is same.
6) How to fuse images through booter, EDBG port On an UAMA Board

Following configuration are required at booter prompt
# watchdog disable
# network enable ( if “unknown command” is displayed, don’t need to execute this )
# setenv serverip 10.254.205.128 (10.254.205.128 is IP for tftp server )
# setenv ipaddr 10.254.205.200 ( use IP within same subnet with tftp server )
# setenv netmask 255.255.255.0
# setenv ethact octeth5( Be sure to connect EDBG port with NotePC directly )
# Octeon uama# ping 10.254.205.128 (ping the TFTP server (Local PC) )
Interface 0 has 4 ports (RGMII)
Interface 1 has 3 ports (RGMII)
Interface 2 has 4 ports (NPI)
eth_get_dev()->name: octeth5
Using octeth5 device
octeth5: Up 1000 Mbps Full duplex (port 17)
9|P a g e

host 10.254.205.128 is alive( Ping status must be alive from eNB to Local PC )
Copy below commands and execute them under booter. ( Check image names once again )
tftp 0x20000000 booter.enb_uama.0;erase 0x1be00000 0x1befffff;cp.b 0x20000000 0x1be00000
BOOTER
0x00080000;booterbackup 1
tftp 0x20000000 kernel.enb_uama.0;erase 0x18000000 0x185fffff;cp.b 0x20000000 0x18000000
KERNEL
0x00300000;cp.b 0x20000000 0x18300000 0x00300000
tftp 0x20000000 rfs.enb_uama.0;erase 0x19a00000 0x1b1fffff;cp.b 0x20000000 0x19a00000

RFS
0x00c00000;cp.b 0x20000000 0x1a600000 0x00c00000
tftp 0x20000000 rfs_raw.enb_uama.0;erase 0x18600000 0x199fffff;cp.b 0x20000000 0x18600000

RFS_RAW
0x01400000
7) On L9CA channel card

Following configuration are required at booter prompt
# network enable (if “unknown command” is displayed, don’t need to execute this. )
# setenv serverip 10.254.205.128 (10.254.205.128 is IP for tftp server)
# setenv ipaddr 10.254.205.200 (use IP within same subnet with tftp server)
# setenv gatewayip 10.254.205.1
# setenv netmask 255.255.255.0
# setenv ethaddr 12:00:00:12:00:00
# setenv ethact octeth0(Be sure to connect EDBG port with NotePC directly)
Copy below commands and execute them under bother. ( Check image names once again ).
tftp 0x0aa00000 booter.enb_l9ca_b4f.0;erase 0xbbe00000 0xbbefffff;cp.b 0x0aa00000 0xbbe00000
BOOTER
0x00080000;booterbackup 1
tftp 0x0aa00000 kernel.enb_l9ca_b4t.0;erase 0xbc000000 0xbc5fffff;cp.b 0x0aa00000 0xbc000000

KERNEL
0x00300000;cp.b 0x0aa00000 0xbc300000 0x00300000
tftp 0x0aa00000 rfs.enb_l9ca_b4t.0;erase 0xbda00000 0xbedfffff;cp.b 0x0aa00000 0xbda00000

RFS
0x00a00000;cp.b 0x0aa00000 0xbe400000 0x00a00000
tftp 0x0aa00000 rfs_raw.enb_l9ca_b4t.0;erase 0xbc600000 0xbd9fffff;cp.b 0x0aa00000 0xbc600000

RFS_RAW
0x01400000;gettail
8) Reboot the UAMA/L9CA board and verify the version by gettail 0 command.
10 | P a g e

Case-3
Description: Booter is not OK and unable to login through EDGB port.

Prerequisite:
 Latest eNB Firmware file must be pasted on Local PC.
 TFTP server software must be installed on Local PC.
 eNB debug cable(Serial Cable).
Procedure: Fusing Normal Booter from Fail-safe booter
1. Refer to below picture and look for S1 switch DIPswitch. Moving the fourth switch to the left will
make normal booter mode to be changed with fail-safe mode.
b2. Refer to figure “UAMA DIP switch setting to boot form failsafe booter" and change mode to fail-safe
booter.
11 | P a g e

3. Turn on board
4. Execute the recovery through kermit function in teraterm
 Open the Tera Term software and selct the serial option.
 Then click on Setup ->>Serial Port.
 Select the baudrate to 115200 and Press Ok.

* How to recover booter through Kermit
a. execute following command after booting fail-safe booter
loadb 0x20000000
b. Click on File->>Transfer->>Kermit->>Send and select below files one by one for Transfer.
For UAMA :
1) booter.enb_uama.0
For L9CA :
2) booter.enb_l9ca_b4f.0
c. execute following command after booting fail-safe booter

For UAMA->>
erase 0x1be00000 0x1be7ffff;cp.b 0x20000000 0x1be00000 0x80000
For L9CA->>
erase 0xbbe00000 0xbbefffff;cp.b 0x0aa00000 0xbbe00000 0x00080000;
5. Revert the DIP switch to Old configuration to boot in normal booter mode and
continuously press CTRL+C to enter in booter prompt. Execute the following
commands and check the flash version
12 | P a g e

watchdog disable
getinv
getenv
gettail checksum
Check result of 'gettail 0' is OK and flash version is correct.
Abnormal: move to step 6a.

Normal: OS will be booted successfully (done) move to 6b.
6. Fusing remaining FW file on flash through normal booter.
a. if result of "gettail checksum" is NOK, proceed "dump" and report log
a. Execute "flashmap" from booter
UAMA L9CA
Octeon ubma_t# flashmap Octeon l9ca_b4t# flashmap
------------------------------------------------------------ ------------------------------------------------------------
DISPLAY FLASH MAP INFORMATION DISPLAY FLASH MAP INFORMATION
------------------------------------------------------------ ------------------------------------------------------------
Start Addr End Addr Size Start Addr End Addr Size
------------------------------------------------------------ ------------------------------------------------------------
Fail-safe 0xbf800000 0xbf87ffff 0x00080000 Fail-safe 0xbbc00000 0xbbc7ffff 0x00080000
Key 0xbf900000 0xbf97ffff 0x00080000 Resv0 0xbbc80000 0xbbdfffff 0x00180000
Resv1 0xbf980000 0xbfbfffff 0x00280000 Booter0 0xbbe00000 0xbbe7ffff 0x00080000
Kernel0 0x18000000 0x182fffff 0x00300000 Booter1 0xbbe80000 0xbbefffff 0x00080000
Kernel1 0x18300000 0x185fffff 0x00300000 Resv1 0xbbf00000 0xbbfbffff 0x000c0000
Rfs_raw 0x18600000 0x199fffff 0x01400000 IM 0xbbfc0000 0xbbfdffff 0x00020000
Rfs0 0x19a00000 0x1a5fffff 0x00c00000 Env 0xbbfe0000 0xbbffffff 0x00020000
Rfs1 0x1a600000 0x1b1fffff 0x00c00000 Kernel0 0xbc000000 0xbc2fffff 0x00300000
HW_test 0x1b200000 0x1b3fffff 0x00200000 Kernel1 0xbc300000 0xbc5fffff 0x00300000
Resv2 0x1b400000 0x1b8fffff 0x00500000 Rfs-Raw 0xbc600000 0xbd9fffff 0x01400000
UFH 0x1b900000 0x1bafffff 0x00200000 Rfs0 0xbda00000 0xbe3fffff 0x00a00000
Resv1 0x1bb00000 0x1bdfffff 0x00300000 Rfs1 0xbe400000 0xbedfffff 0x00a00000
Booter0 0x1be00000 0x1be7ffff 0x00080000 HW-test 0xbee00000 0xbf2fffff 0x00500000
13 | P a g e

Booter1 0x1be80000 0x1befffff 0x00080000 FPGA 0xbf300000 0xbf7fffff 0x00500000

Resv3 0x1bf00000 0x1bf9ffff 0x000a0000 Ufh 0xbf800000 0xbf9fffff 0x00200000
ENV_R 0x1bfa0000 0x1bfbffff 0x00020000 Resv2 0xbfa00000 0xbfbdffff 0x001e0000
IM 0x1bfc0000 0x1bfdffff 0x00020000 ENV_R 0xbfbe0000 0xbfbfffff 0x00020000
ENV 0x1bfe0000 0x1bffffff 0x00020000 ------------------------------------------------------------
------------------------------------------------------------ [example] booter0 image update
[example] booter0 image update ------------------------------------------
------------------------------------------ tftp 0x0aa00000 booter.enb_l9ca_b4t.0
tftp 0x20000000 booter.enb_ubma_t.0 erase 0xbbe00000 0xbbe7ffff
erase 0x1be00000 0x1be7ffff cp.b 0x0aa00000 0xbbe00000 0x80000
cp.b 0x20000000 0x1be00000 0x80000 ------------------------------------------
------------------------------------------
b. regarding image checksum error happen, dump image area and report them to HQ
md.b [Start Addr] [Size]
b. fusing under normal booter
1) Refer to section Case-2 for fusing below remaining three FW files.
UAMA:
 kernel.enb_uama.0
 rfs.enb_uama.0
 rfs_raw.enb_uama.0
L9CA:
 kernel.enb_l9ca_b4t.0
 rfs.enb_l9ca_b4t.0
 rfs_raw.enb_l9ca_b4t.0
2) Check result of 'gettail checksum' is OK and flash version is correct.
Abnormal:analyze all logs and forward them to NEO-eNB

Normal: OS will be booted successfully done.
14 | P a g e

APPENDIX
Setting up a TFTP server:

1-1. Install tftp server into Local PC.
download file with zip format: http://tftpd32.jounin.net/tftpd32_download.html

1-2. extract zip file.
1-3. execute tftpd32.exe.
1-4. Change current directory to where flash images for UAMA are located
Above window is displayed, after configuration is done

Tftp server should be installed into a PC where ESCORT is not installed;Since ESCORT could block tftp service
port due to security policy
15 | P a g e


CV Shashank Nigam

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CV Shashank Nigam

Uploaded by

Copyright:

Available Formats

Ed.

Date of Release: 31-July-14

Prepared By: Mr. Manish Singh

Reviewed By: Mr. Hiren Joshi

NEO eNB Part (R4G Project)

NEO eNB Part (R4G Project)

00 31-July-14 Manish Singh New Document

NEO eNB Part (R4G Project)

LTE eNB UAMA/L9CA SW Fusion MOP 5

NEO eNB Part (R4G Project)

LTE eNB UAMA/L9CA SW Fusion MOP

L9CA DBG Port

UAMA DBG Port

To troubleshoot the Firmware fusion issues, fault can be categorized as below.

© SAMSUNG Electronics Co., Ltd. page 5 of 15

4) Put below latest Firmware files to root folder of eNB by Filezilla.

NEO eNB Part (R4G Project)

7) After running this command Firmware fusion will get complete.

NEO eNB Part (R4G Project)

1) Fusing through TFTP, EDBG port

(USB) (RJ45) (RJ45)

2) Setting up a TFTP server

 Open the tftpd32.exe software.

NEO eNB Part (R4G Project)

Above window is displayed, after configuration is done

 Then click on Setup ->>Serial Port.

 Select the baudrate to 115200 and Press Ok.

4) Reboot the Board by pressing the RST button on it.

6) How to fuse images through booter, EDBG port On an UAMA Board

NEO eNB Part (R4G Project)

tftp 0x20000000 rfs.enb_uama.0;erase 0x19a00000 0x1b1fffff;cp.b 0x20000000 0x19a00000

tftp 0x20000000 rfs_raw.enb_uama.0;erase 0x18600000 0x199fffff;cp.b 0x20000000 0x18600000

7) On L9CA channel card

tftp 0x0aa00000 kernel.enb_l9ca_b4t.0;erase 0xbc000000 0xbc5fffff;cp.b 0x0aa00000 0xbc000000

tftp 0x0aa00000 rfs.enb_l9ca_b4t.0;erase 0xbda00000 0xbedfffff;cp.b 0x0aa00000 0xbda00000

tftp 0x0aa00000 rfs_raw.enb_l9ca_b4t.0;erase 0xbc600000 0xbd9fffff;cp.b 0x0aa00000 0xbc600000

NEO eNB Part (R4G Project)

Description: Booter is not OK and unable to login through EDGB port.

Procedure: Fusing Normal Booter from Fail-safe booter

NEO eNB Part (R4G Project)

4. Execute the recovery through kermit function in teraterm

 Then click on Setup ->>Serial Port.

 Select the baudrate to 115200 and Press Ok.

a. execute following command after booting fail-safe booter

c. execute following command after booting fail-safe booter

erase 0x1be00000 0x1be7ffff;cp.b 0x20000000 0x1be00000 0x80000

erase 0xbbe00000 0xbbefffff;cp.b 0x0aa00000 0xbbe00000 0x00080000;

continuously press CTRL+C to enter in booter prompt. Execute the following

commands and check the flash version

NEO eNB Part (R4G Project)

Check result of 'gettail 0' is OK and flash version is correct.

Abnormal: move to step 6a.

6. Fusing remaining FW file on flash through normal booter.

a. if result of "gettail checksum" is NOK, proceed "dump" and report log

a. Execute "flashmap" from booter

NEO eNB Part (R4G Project)

Booter1 0x1be80000 0x1befffff 0x00080000 FPGA 0xbf300000 0xbf7fffff 0x00500000

md.b [Start Addr] [Size]

b. fusing under normal booter

1) Refer to section Case-2 for fusing below remaining three FW files.

2) Check result of 'gettail checksum' is OK and flash version is correct.

Abnormal:analyze all logs and forward them to NEO-eNB

NEO eNB Part (R4G Project)

Setting up a TFTP server: