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.
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
CPU: e300c1, MPC8347_TBGA_EA, Rev: 3.0 at 600 MHz, CSB: 200 MHz
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
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/*
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.
I have a cisco c60 codec, it powers up and show the green LED in front of the codec, but no display. i connected a serial cable via usb to my laptop and tried connecting using PUTTY and SecureCRT, but no response from the codec. pls can anyone help resolve this issue. am i connecting wrongly. serial connection is (Baud Rate- 38400, Data bits- 8, Parity- None, Stop bits-1, Flow Control-RTS/CTS -ticked.
Try with XON/XOFF flow control instead of RTS/CTS. The 38400, 8, N, 1 is correct.
Have the serial cable connected and the terminal app running before powering on the endpoint, then turn it on and see if you can see any of the boot messages on the screen.
If you need to, you can also repeatedly press "b" while the system is being powered on, which should break out in to the u-boot where you can then use the "selectsw" command to try to swap to a different software image, or perform some other low level troubleshooting.
Neither of the images you put in your reply seem to work at this end. Are you able to attach them again?
Other than the serial port, or accessing via the network, there aren't really any other "diagnostics tools" you can use. If it's looking really dead, your best bet would be to RMA the device through the TAC.