目前日期文章:201305 (5)

瀏覽方式: 標題列表 簡短摘要

In the previous post, we’ve successfully launched KGDB on BeagleBoard. Now we need to execute GDB with BeagleBoard’s symbol table and and remote connect to KGDB on BeagleBoard.

1. Go to the folder we built arm-angstrom-linux-gnueabi-gdb and type:
./arm-angstrom-linux-gnueabi-gdb [path to vmlinux file]

silentlain 發表在 痞客邦 PIXNET 留言(0) 人氣()

Now all the files are ready. We need to boot BeagleBoard to KGDB. How?

Here’s the flow chart for KGDB:

silentlain 發表在 痞客邦 PIXNET 留言(0) 人氣()

In this post I will address GDB on the PC side.

GDB comes preinstalled with most Linux distributions. You can definitely find one in your PC. However, these GDBs are not what we need here. We need a GDB that runs on PC (x86, x86-64) but can debug ARM architecture. Therefore we need to build it. Fortunately, OpenEmbedded already has pre-written recipes for it. All we need to do is type the following commands:

source ~/.oe/environment-angstromv2012.05

silentlain 發表在 痞客邦 PIXNET 留言(0) 人氣()

In this post I will show how to enable KGDB in Angstrom.

In order to enable KGDB, we need to modify kernel configurations and rebuild the kernel. For desktop Linux distributions, we can do this by make menuconfig. In Angstrom, it’s similar. We only need to replace the make command by bitbake command and setup its environment. Here are the steps:
1. source ~/.oe/environment-angstromv2012.05

silentlain 發表在 痞客邦 PIXNET 留言(0) 人氣()

Generally speaking there are two ways to do kernel debugging in Angstrom:
1. Using KGDB as a remote GDB agent.
2. Using a hardware JTAG to control the processor.

silentlain 發表在 痞客邦 PIXNET 留言(0) 人氣()