C60 Stuck in reboot cycle

[jameshelemis]

Hey All,

PLEASE HELP!!!!

We have a Tandberg C60, and during configuration today it has got stuck in a loop/ reboot cycle.

Everytime you turn the device on, it loads, the camera turns on, the displays turn on, and then it freezes and reboots.

Any suggestions?

I figure a hardware reset would do the trick - any suggestions on how to do this? (I am a complete cisco novice!)

I have downloaded putty after reading a few forums, connected the serial port up to my laptop using these settings:

http://imageshack.us/a/img201/6749/16098725.jpg

and rebooted the device,

and I get the following messages which mean nothing to me...

http://imageshack.us/a/img341/5210/78796759.jpg

http://imageshack.us/a/img12/4940/13248734.jpg

Please help!!!

Thanks

J

[mapotter]

When you see garbled characters like that, it's a good indication that your data communication settings are off. In this case, you need to change the Speed(baud) setting to 38400.

If the system is rebooting, you likely won't get a login prompt. In that case, you'll have to break the boot cycle:

1) Connect to the serial port

2) Power cycle the system

3) Hit the "b" key repeatedly as soon as you turn the power on

4) If you hit "b" in time, the boot messages will stop scrolling, at which point you should you should hit "c".

At this point you should be sitting at a CASPER> (or CASPERII>) prompt.

Type "selectsw". This will show you the software images on the box. If more than one is present, switch to the one that isn't active by typing "selectsw image2" (or image1, depending which is inactive). Then type "boot" to boot the system from the new image.

If you only have one software image, you can clear the configuration on the system by typing "yrm /flash/image1/config.db" (or image2, depending which image is active). Then type "boot" to boot the system. A default config.db will be created.

Try those two steps and let us know how it goes.

[Danny De Ridder]

Matthew,

should we try, prior to perform the selectsw, check the logfiles to see what went wrong? In order to do so, I would use your break into u-boot procedure and do :

setenv othbootargs allowroot

reboot

And once the login prompt is seen enter root as username

login:

Once you see the prompt, do :

touch /tmp/noboot

This will avoid C60 rebooting so you can check the logfiles located at :

/var/log

and at

/var/log/eventlog

Files to display would be :

cat /var/log/console

cat /var/log/eventlog/main.log

cat /var/log/eventlog/all.log

Capture this data and we should hopefully see why the reboots are happening.

[Danny De Ridder]

Hello,

thanks for taking the time to connect the console!

The garbled data normally indicates a baudrate mismatch. For this type of codec, the speed needs to be set to 38400.

See following document. Look for console or RS232.

https://supportforums.cisco.com/docs/DOC-15643

Once you have readable data, can you post what's seen on your screen so we can decide which action to take.

Danny.