omap35 出现 No more output is seen on the console after "Starting Kernel..." 调试信息
2011-01-09 16:27
597 查看
The first problem a user may encounter when booting the kernel, is that no further output after "Starting kernel..." is seen on the console. For example:
The above console output is printed by the u-boot boot-loader when starting linux and the message "Starting kernel..." is last message that u-boot will print before starting the kernel. The above problem is typically caused by mis-configuring the tty interface that the linux kernel uses by default for displaying the console messages. The default tty interface used the linux kernel for OMAP devices is configured in the kernel menuconfig. You can check the tty interface being used for an OMAP device by viewing the kernel .config file and seeing which CONFIG_OMAP_LL_DEBUG_UARTx is selected. For example, the OMAP3 beagle-board uses UART3 for displaying the console messages. Hence, when using the OMAP3 beagle-board the following should be found in the .config file:
The default tty interface used by the linux kernel for OMAP can be configured by starting the linux menuconfig utility (by executing "make menuconfig") and going to "System Type --> TI OMAP Implementations --> Low-level debug console UART".
## Booting kernel from Legacy Image at 80300000 ... Image Name: Linux-2.6.31 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1750680 Bytes = 1.7 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ...
The above console output is printed by the u-boot boot-loader when starting linux and the message "Starting kernel..." is last message that u-boot will print before starting the kernel. The above problem is typically caused by mis-configuring the tty interface that the linux kernel uses by default for displaying the console messages. The default tty interface used the linux kernel for OMAP devices is configured in the kernel menuconfig. You can check the tty interface being used for an OMAP device by viewing the kernel .config file and seeing which CONFIG_OMAP_LL_DEBUG_UARTx is selected. For example, the OMAP3 beagle-board uses UART3 for displaying the console messages. Hence, when using the OMAP3 beagle-board the following should be found in the .config file:
# CONFIG_OMAP_LL_DEBUG_UART1 is not set # CONFIG_OMAP_LL_DEBUG_UART2 is not set CONFIG_OMAP_LL_DEBUG_UART3=y
The default tty interface used by the linux kernel for OMAP can be configured by starting the linux menuconfig utility (by executing "make menuconfig") and going to "System Type --> TI OMAP Implementations --> Low-level debug console UART".
相关文章推荐
- xcode在真机调试的时候出现"The identity used to sign the executable is no longer valid"
- xcode在真机调试的时候出现"The identity used to sign the executable is no longer valid"
- xcode在真机调试的时候出现"The identity used to sign the executable is no longer valid"
- Xcode在真机调试的时候出现"The identity used to sign the executable is no longer valid"
- xcode在真机调试的时候出现"The identity used to sign the executable is no longer valid"
- Windows Azure - "The Path is too long after being fully qualified" 错误信息的解决方案(转)
- xcode在真机调试的时候出现"The identity used to sign the executable is no longer valid"
- 交叉调试时arm-linux-gdb提示:No symbol table is loaded. Use the "file" command.
- rh423 - 主辅同步报错:there is no replicated area "dc=server119,dc=example,dc=com" on the consumer server
- xcode7在真机调试的时候出现"The identity used to sign the executable is no longer valid"
- 真机调试时出现"The identity used to sign the executable is no longer valid"
- gdb调试错误:No symbol table is loaded. Use the "file&qu
- 出现 No more output is seen on the console after "booting the kernel" 调试信息
- omap35 出现 No console prompt seen after kernel boot
- 真机测试别人的demo才出现"The identity used to sign the executable is no longer valid"
- xcode在真机调试的时候出现"The identity used to sign the executable is no longer valid"
- gdb调试中出现No symbol table is loaded. Use the "file" command.问题
- postgresql 出现 Is the server running locally and accepting connections on Unix domain socket "/var/r
- 解决gdb调试报错“No symbol table is loaded. Use the "file" command.”
- IAR调试cc2540 时 出现The stack plug-in failed to set a breakpoint on "main". 解决方法