Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

CISCO C60 Codec


the system does not start up, potentially it is stuck in bootloop. At the start there only appears shortly the CISCO Logo. I will send my contacts by mail now a log for review.

Everyone's tags (5)
Cisco Employee

CISCO C60 Codec


I looked at the log you sent via email. The codec boots as far as the login prompt, but then apparently reboots.


U-Boot 2010.06-89 (Aug 10 2011 - 14:36:51) MPC83XX

Reset Status:

CPU:   e300c1, MPC8347_TBGA_EA, Rev: 3.0 at 600 MHz, CSB: 200 MHz

I2C:   ready

DRAM:  DDR2 RAM: 512 MiB

RAM data bus test          [PASS]

RAM address bus test          [PASS]

Either the main application crashes or there's some hardware issue.

Since you have console access I would let the codec reboot and enter followed by at reboot.

Press 'b' to enter u-boot prompt

Press 'c' to stop autoboot:  0

The you should get the u-boot prompt.

From there, we need to set some environment parameters so the codec does not reboot when it crashes and we can access the root shell to get the logfiles.

CASPER>setenv othbootargs allowroot noboot


Now when there's a crash, it should not reboot.

login as root and get all the logfiles

tar -cvf /tmp/historical_log_bundle_tar /config/logs/*

gzip /tmp/historical_log_bundle.tar

scp /tmp/historical_log_bundle.tar.gz user@system:historical_log_bundle.tar.gz

Last is secure copy to get file from your codec to some unix system.

You can also use winscp or some other program to get the file of the codec so it can be sent over.

If there are crashes, we should be able to run the files through a tool to look for known issues.

That would be the first step.

Also, at the CASPER> prompt, collect the output of hwmon :


That will show the voltages are in spec or not.

If you can get these files, that would be great!

Another way of looking at error messages would be to use following procedures, ones you broke into u-boot.

CASPER> setenv othbootargs allowroot noconsolefile noboot timestamp

CASPER>setenv console ttyS0


Now all the logging info is sent straight to your console.

Good luck,