On 02/08/2012 14:55, Fabio Estevam wrote:
On 8/2/12, Michael Hornung mhornung.linux@gmail.com wrote:
Hi Fabio,
Hi Michael,
Starting kernel ...
Uncompressing Linux...................................................................................................................................... done, booting the kernel.
And that's it, no more kernel output.
At this point, there is no difference for u-boot starting the kernel if it has booted in external or internal mode. It seems an unrelated issue.
On mx35pdk you can reset the board without powerd off. You should check the address in kernel for the log buffer (__log_buf in System.map) and then check it after a reset in u-boot with the "md" command. If we are lucky, the RAM does not lose its values. Better will be if you have a JTAG debugger and can you check inside memory directly when the kernel hangs without rebooting.
Here my environment
addip=if test -n ${ipdyn};then run addip_dyn;else run addip_sta;fi addip_dyn=setenv bootargs ${bootargs} ip=dhcp addip_sta=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off panic=1 addmisc=setenv bootargs ${bootargs} ${misc} addmtd=setenv bootargs ${bootargs} ${mtdparts} addtty=setenv bootargs ${bootargs} console=ttymxc0,${baudrate} baudrate=115200 bootargs_nfs=setenv bootargs console=ttymxc0,${baudrate} root=/dev/nfs
Depending on the kernel version, ttymxc0 could be wrong. Have you checked it ?
Best regards, Stefano Babic