10-15-2012 08:58 AM - edited 03-17-2019 11:58 PM
Hi folks
I am trying to fix and E20 that won't boot. I have managed to obtaint the appropriate serial cable and can log into it as root using teraterm, but am stuck as to what to do next. Any ideas what the appropriate console commands are?
Thanks
Solved! Go to Solution.
10-17-2012 04:11 AM
Got on the phone with Hazel and entered the system in u-boot mode by hitting
Set the u-boot environment to get into root :
setenv otherbootargs allowroot
So we could finally login to the system via root. admin did not work because the E20 crashed.
We looked at the /var/log/eventlog/all.log file and noticed one of the DSPs is not responding : hardware issue. Not possible to fix this but RMA the unit. Sorry for this...
[Snoopy:/var/log/eventlog] $ cat all.log Oct 17 11:58:04 (none) main: FPGA programmed OK Oct 17 11:58:04 (none) main: Product information Oct 17 11:58:04 (none) main: Snoopy Oct 17 11:58:04 (none) main: Board revision: G Oct 17 11:58:04 (none) main: Thread LedTask has TID 1746 Oct 17 11:58:04 (none) main: TE4.1.1.273710 Oct 17 11:58:04 (none) main: SVN Revision 273710 Oct 17 11:58:04 (none) main: Serial number: A1AA02A00080 Oct 17 11:58:04 (none) main: Program audio dsps [1] Oct 17 11:58:13 (none) osd: WARNING : Cannot parse value [ "" ] in "Config/Video/Selfview" to boolean. Treating it as "false". Oct 17 11:58:13 (none) osd: WARNING : TState has no desktop set Oct 17 11:58:13 (none) osd: WARNING : TState has no desktop set Oct 17 11:58:15 (none) main: shmemLoadDsp: Program video dsp Oct 17 11:58:17 (none) main: shmemLoadDsp: Program video dsp finished Oct 17 11:58:17 (none) video: DSP ID 1 Oct 17 11:58:17 (none) video: Product information Oct 17 11:58:17 (none) video: Snoopy Oct 17 11:58:17 (none) video: Board revision: G Oct 17 11:58:17 (none) main: Thread persistDb has TID 1763 Oct 17 11:58:18 (none) main: Thread persistDb has TID 1764 Oct 17 11:58:18 (none) video: fsm_procSetup: Open Interprocessor comm devs. Oct 17 11:58:18 (none) video: shmemdsp: Waiting for arm to init shmem area. (119) Oct 17 11:58:18 (none) main: Thread ShmemRx has TID 1765 Oct 17 11:58:19 (none) video: shmemdsp: Waiting for arm to init shmem area. (118) Oct 17 11:58:20 (none) video: fsm_procSetup: Initialize data structures. Oct 17 11:58:20 (none) video: fsm_procSetup: Create all FSM tasks[6]. Oct 17 11:58:20 (none) video: fsm_procSetup: Check for system synchronization. Oct 17 11:58:20 (none) video: registerAndWaitForNotify: Sending id = SYSTEM_VIDEO0(1) (16777216) Oct 17 11:58:20 (none) video: Wait for timeout, or incoming message Oct 17 11:58:28 (none) main: uhpihost: Can't boot dsp 0 Oct 17 11:58:28 (none) main: uhpihost: Can't boot all dsps Oct 17 11:58:29 (none) main: Received signal SIGSEGV (11) in thread 0x4082a4c0, TID 1713 Oct 17 11:58:29 (none) main: Illegal memory access at: 0xebffffb2 Oct 17 11:58:29 (none) main: Registers: Oct 17 11:58:29 (none) main: R0: 4010414c R1: ebffffb2 R2: bea1569c R3: 000000c8 Oct 17 11:58:29 (none) main: R4: 40100000 R5: bea1569c R6: ebffffb2 R7: bea1569c Oct 17 11:58:29 (none) main: R8: bea156c8 R9: ffffbd0c R10: bea156cc FP: bea199e4 Oct 17 11:58:29 (none) main: PC: 400e8864 IP: 400e8818 SP: bea15640 LR: 400e9790 Oct 17 11:58:29 (none) main: ERR: 00000005 CPSR: 60000010 FAULT: ebffffb2 TRAP: 0000000e Oct 17 11:58:29 (none) main: OLDMSK: 00000000
10-15-2012 09:17 AM
Hi Hazel,
First you will need to enable the root account before you can login.
Login using an admin account and type the following command:
rootsettings on
Once you have activated the account, you can then login using the username root.
Hope this helps,
Regards,
Mubashshir Akhtar
10-15-2012 09:19 AM
In case your E20 is not booting up at all, then you will not be able to login to its root account. In that case, it would not be possible for you to restore the E20 to a working image. What you can try is to do a factory reset using the buttons on the E20 device.
Regards,
Mubashshir Akhtar
10-15-2012 10:49 AM
Hello,
can you, from within root execute the command selectsw?
Normally, you should have 2 images on the E20, image1 and image2. One will show up as being the active one.
[C20-in-TP-lab-CUCM-controlled:~] $ selectsw
image1
image2 [ACTIVE] [SELECTED]
[C20-in-TP-lab-CUCM-controlled:~] $
So in my case, image2 is active.
See what the command returns in your case. The active image is bad in your case. Does not boot. So you can try the other image. To do this, e.g. when I want to select image1, I would do :
[C20-in-TP-lab-CUCM-controlled:~] $ selectsw image1
And then reboot your E20?
Hopefully the "other" backup image will work in your case.
Can you log the boot sequence to a file when you are connected on the console?
10-15-2012 04:45 PM
If switching software (as Danny mention) won’t help, try removing the configuration file and local phonebook file in case system boot failure due to corrupted files.
10-16-2012 01:37 AM
Hi folks
Thanks for the advice. Based on your posts I have deleted config.db and pb.xml from image 1 and rebooted with no success. I have alos swapped to image 2 using the selectsw command and repeated the delete of config.db and pb.xml. Unfortunatly neither of these has lead to a successful reboot. For info, the log of the latest reboot is below.
Thanks for all your help.
Hazel
login: root
Last login: Tue Oct 16 09:26:24 on ttyS0
[NHSGGC-Calum-Morrison:~] $ rm /mnt/base/active/config.db
[NHSGGC-Calum-Morrison:~] $ rm /config/pb.xml
[NHSGGC-Calum-Morrison:~] $ reboot
Broadcast message from root (ttyS0) (Tue Oct 16 09:28:25 2012):
The system is going down for reboot NOW!
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal
[NHSGGC-Calum-Morrison:~] $ umount: /mnt/base/image2/tools.img busy - remounted read-only
umount: /mnt/base/image2/extra.img busy - remounted read-only
umount: /dev/mtdblock1 busy - remounted read-only
umount: /var: device is busy
umount: none busy - remounted read-only
shutdown: sending all processes the TERM signal...
shutdown: sending all processes shutdown: turning off swap
swapoff: No such file or directory
shutdown: unmounting all file systems
umount: /mnt/base: device is busy
Restarting system.ce is busy
Please staþ
U-Boot 2009.03-37 (Feb 22 2011 - 13:38:41)
I2C: ready
DRAM: 256 MB
Flash: 4 MB
NAND: HW ECC on 1024 MiB
RTC: 2012-10-16 (Tuesday) - Time: 8:28:39
Ethernet PHY: Marvell
Snoopy
Rev: G
SN: A1AA02A00080
MAC: 00:50:60:04:05:67
ARM Clock :- 337MHz
DSP Clock :- 675MHz
DDR Clock :- 310MHz
Hold down '4' and '6' when power up to toggle image
yaffs: Mounting /flash
yaffs: restored from checkpoint
Hit any key to stop autoboot: 0
lcdpower: 1
lcdbacklight:1
Copy /flash/active/rootfs to 0x87000000... [DONE]
Copy /flash/active/kernel to 0x85000000... [DONE]
save exit: isCheckpointed 1
## Booting kernel from Legacy Image at 85000000 ...
Image Name: Linux-2.6.23.12-104
Created: 2010-09-03 10:59:49 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1736996 Bytes = 1.7 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 87000000 ...
Image Name: TANDBERG rootfs
Created: 2010-09-06 10:33:02 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7768103 Bytes = 7.4 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................................................................... done, booting the kernel.
Linux version 2.6.23.12-104 (hgb@prentice.rd.tandberg.com) (gcc version 4.2.2) #1 PREEMPT Fri Sep 3 12:59:38 CEST 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: DaVinciHD Tandberg Snoopy
Memory policy: ECC disabled, Data cache writeback
DM6467
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists in Zone order. Total pages: 48768
Kernel command line: basemount=/dev/mtdblock1 mem=192M@0x80000000 console=ttyS0,115200 eth=00:50:60:04:05:67 mainboard=0x06 u-boot=2009.03-37
TI DaVinci EMAC: Kernel Boot params Eth address: 00:50:60:04:05:67
PID hash table entries: 1024 (order: 10, 4096 bytes)
davinci_timer_init: PLL1_PLLM 24
Console: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 192MB = 192MB total
Memory: 183552KB available (3176K code, 220K data, 132K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Generic PHY: Registered new driver
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 2.2a/db-0.5.2, cppi-dma, host, debug=0
musb_hdrc: USB Host mode controller at cc800000 using DMA, IRQ 13
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
DaVinci I2C DEBUG: 12:59:12 Sep 3 2010
NET: Registered protocol family 2
Time: timer0_1 clocksource has been installed.
Switched to high resolution mode on CPU 0
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 7586K
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
io scheduler noop registered
io scheduler anticipatory registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a ST16654
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x1c20400 (irq = 41) is a ST16654
RAMDISK driver initialized: 16 RAM disks of 65000K size 1024 blocksize
TI DaVinci EMAC: MAC address is 00:50:60:04:05:67
TI DaVinci EMAC Linux version updated 5.0
TI DaVinci EMAC: Installed 1 instances.
Linux video capture interface: v2.00
Capture buffer 0 at 0x87400000, mapped to 0xc7400000, size 1925k
Capture buffer 1 at 0x80600000, mapped to 0xc0600000, size 1925k
Capture buffer 2 at 0x87000000, mapped to 0xc7000000, size 1925k
Capture buffer 3 at 0x87200000, mapped to 0xc7200000, size 1925k
snoopyfb0: Framebuffer at 0x87c01000, mapped to 0xc7c01000, size 1920k
snoopyfb0: Framebuffer registered on snoopy card
Display buffer 0 at 0x87800000, mapped to 0xc7800000, size 3847k
Display buffer 1 at 0x86c00000, mapped to 0xc6c00000, size 3847k
Display buffer 2 at 0x86800000, mapped to 0xc6800000, size 3847k
Display buffer 3 at 0x86400000, mapped to 0xc6400000, size 3847k
Display buffer 4 at 0x86000000, mapped to 0xc6000000, size 3847k
physmap platform flash device: 00400000 at 42000000
physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
physmap-flash.0: Swapping erase regions for broken CFI table.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
RedBoot partition parsing not available
DaVinci NAND Controller rev. 2.2
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 635 at 0x09ec0000
Bad eraseblock 663 at 0x0a5c0000
Bad eraseblock 1171 at 0x124c0000
Bad eraseblock 2278 at 0x23980000
Bad eraseblock 2295 at 0x23dc0000
Bad eraseblock 2344 at 0x24a00000
Bad eraseblock 2482 at 0x26c80000
Bad eraseblock 2908 at 0x2d700000
Bad eraseblock 3281 at 0x33440000
Bad eraseblock 3935 at 0x3d7c0000
Bad eraseblock 3971 at 0x3e0c0000
Creating 1 MTD partitions on "NAND 1GiB 3,3V 8-bit":
0x00000000-0x40000000 : "Flash partition 0"
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
rtc-ds1307 0-0068: rtc core: registered m41t00 as rtc0
i2c /dev entries driver
DaVinci I2C WARNING: i2c: NACK detected
DaVinci I2C WARNING: i2c: NACK detected
DaVinci I2C WARNING: i2c: NACK detected
DaVinci I2C WARNING: i2c: NACK detected
DaVinci I2C WARNING: i2c: NACK detected
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
oprofile: using timer interrupt.
netem: version 1.2
u32 classifier
Performance counters on
Actions configured
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
rtc-ds1307 0-0068: setting the system clock to 2012-10-16 08:28:59 (1350376139)
Freeing init memory: 132K
INIT: version 2.86 booting
chown: cannot access `/tmp': Function not implemented
chown: cannot access `/proc': Function not implemented
chown: cannot access `/sys': Function not implemented
chown: cannot access `/sbin': Function not implemented
chown: cannot access `/etc': Function not implemented
chown: cannot access `/bin': Function not implemented
chown: cannot access `/boot': Function not implemented
chown: cannot access `/var': Function not implemented
chown: cannot access `/libexec': Function not implemented
chown: cannot access `/info': Function not implemented
chown: cannot access `/usr': Function not implemented
chown: cannot access `/share': Function not implemented
chown: cannot access `/lib': Function not implemented
chown: cannot access `/root': Function not implemented
chown: cannot access `/dev': Function not implemented
Mounting filesystems
loop: module loaded
input: cradle_sense as /devices/virtual/input/input0
Registered led device: arm_led1
Registered led device: arm_led2
Registered led device: status_led
input: serial_mcasp_driver as /devices/virtual/input/input1
video_dsp_driver: DspCom: IRQ: 45
yaffs: dev is 32505857 name is "mtdblock1" rw
yaffs: passed flags ""
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
INIT: Entering runlevel: 2
login: root
Last login: Tue Oct 16 08:30:31 on ttyS0
[tandberg:~] $ help
10-16-2012 04:42 AM
Seem base operation system is running but not Cisco E20 application.
And seem network is alao available, are you able to ping from E20 ([tandberg:~] $ xx.xx.xx.xx)?
If base operation system is up and running and have network connection, please follow below procedure to install E20 software using SCP.
10-16-2012 05:23 AM
Thanks for the extra help. I have found the IP address and managed to ping it. However when using WinSCP, it keeps refusing the connection. Does it matter that there is no password on the root accout? (However I have tried the default and that does not work either)
Thanks
10-16-2012 05:29 AM
Can you ssh to E20 by using putty or other SSH application to verify root acount accessibility (yes, possibly lost rootsetting)?
10-16-2012 06:58 AM
This is so frustrating. Finally managed to get in using Win SCP. E20 keeps rebooting approx every 5 minutes, before the .pkg file was transferred. Finally seemed to get the transfer done in time, only to be to told that it had failed because the device was full.
10-16-2012 07:19 AM
you can do a "touch /tmp/noboot" to stop the cyclic boot
maybe try uploading the file directly to the /upgrade directory if you can, then rename it to pkg once the upload is complete.
10-16-2012 07:40 AM
Hello,
I think that's a good idea to do the touch "/tmp/noboot" from root or even, do a touch /user/noboot to make this semi-permanent. Also, it seems your main application crashes, so perhaps it is better to touch antoher file /user/nostart so the main application does not get started at all. Reload the codec, and then execute the scp and upload the file directly to /upgrade/pkg so the process which looks for software upgrades will extract the package automatically.
[dderidde-ex90-home:~] $ touch /user/noboot
[dderidde-ex90-home:~] $ touch /user/nostart
After the reload, the package should be installed, but then you need to remove the 2 files :
rm /user/noboot
rm /user/nostart
When you now reboot, all should work.
10-16-2012 07:50 AM
Danny,
I know this is kind of off topic, but any chance you could explain exactly what the 'touch /tmp/noboot' and the 'touch /user/noboot' and the 'touch /user/nostart' actually do? I am very curious about these commands, and I am trying to learn as much as I can about Linux.
Thanks,
Justin
10-16-2012 08:41 AM
The files are used by scripts which are going to check whether a file is present or not and take actions on it. E.g. when a system crashes, it will reboot, but if the file /tmp/noboot or /user/noboot is present, the unit will NOT reboot automaticall, thus avoiding cyclic reboots. The nostart means boot the software, but do not start the main application. I did this because the system here seemed to be crashing all the time, and we wanted to upgrade the E20 via scp.
10-16-2012 07:55 AM
Some progress. Have managed to upgrade the software by copying directly to the /upgrade directory as per the log below. However when the system reboots, I can no longer log in as root as it appears a password has been set. Has it changed from the old default? Also, the system still does not boot up - even with the new software te4.1.1.
[tandberg:~] $ [ 0] [* ] Obtaining lock
[ 1] [** ] Determining base directory
[ 2] [*** ] Determining install directory
[ 2] [**** ] Running early product-specific tasks
[ 4] [***** ] Cleaning install directory
[ 6] [****** ] Extracting software
[ 63] [******* ] Verifying data integrity
[ 64] [******** ] Copying user data
[ 68] [********* ] Copying release key file
[ 68] [********** ] Running product-specific tasks
[ 69] [*********** ] Running post-install hooks from installed package
[ 74] [************ ] Switching default installation and upgrade boot sw
[ 89] [************* ] Done
[ 91] [**************] Rebooting
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide