{"id":307,"date":"2019-03-19T15:51:33","date_gmt":"2019-03-19T22:51:33","guid":{"rendered":"https:\/\/sysprogs.com\/tutorials\/?p=307"},"modified":"2019-07-16T16:43:39","modified_gmt":"2019-07-16T23:43:39","slug":"preparing-petalinux-kernels-for-debugging-with-visualkernel","status":"publish","type":"post","link":"https:\/\/sysprogs.com\/VisualKernel\/tutorials\/xilinx\/petalinux\/","title":{"rendered":"Preparing Petalinux Kernels for Debugging with VisualKernel"},"content":{"rendered":"

This tutorial shows how to prepare a kernel built with the Petalinux tools<\/a> for importing it into VisualKernel and creating kernel modules for it. We will start with a basic Petalinux project, modify its settings to support debugging and will show the parameters necessary to import the kernel into VisualKernel.<\/p>\n

In order to debug the Petalinux-based kernel from VisualKernel, we will need to perform the following modifications:<\/p>\n

    \n
  1. Enable debug symbol generation so that the debugger can step through the kernel source and unwind stack traces.<\/li>\n
  2. Disable the memory protection attributes on the code sections of the kernel and modules, so that VisualKernel can set software breakpoints there.<\/li>\n
  3. Modify the kernel build scripts to dump the environment variables set by Petalinux so that VisualKernel can automatically configure IntelliSense.<\/li>\n
  4. Finally build the kernel with the new settings<\/li>\n<\/ol>\n

    In the rest of this tutorial we will provide detailed steps on accomplishing the tasks above.<\/p>\n

      \n
    1. Ensure you have a Linux-based machine (or a VM) where you can run the Petalinux tools. Download and install the tools<\/a>\u00a0from the Xilinx website and copy your Petalinux project to the same machine.<\/li>\n
    2. Connect to the build machine via SSH and run the following commands:\n
      cd <Petalinux tools directory>\r\n. settings.sh\r\ncd <Petalinux project directory>\r\npetalinux-config -c kernel<\/pre>\n
      This will start the process of downloading and configuring a Linux kernel:
      \n\"\"<\/li>\n
    3. Once the necessary files are downloaded, you will see the kernel configuration menu:\"\"
      \nNote that as of March 2019, the Petalinux menu background appears distorted when accessed from Windows SSH clients. This does not affect the functionality.<\/li>\n
    4. Enable the\u00a0Kernel hacking -> Compile-time checks and compiler options -> Compile the kernel with debug info<\/strong>\u00a0setting in the menu, but do not close it yet<\/strong>:\"\"
      \nOnce you close the menu, the Petalinux tools will delete the Linux kernel source files, so if we want to modify them to disable memory protection and support environment dumping, we need to do it while the menu is open, obtain a patch file and integrate it into the Petalinux project.<\/li>\n
    5. In another tab go to your Petalinux project directory (not the Petalinux tools directory) and run the following command:\n
      find . | grep \/printk.c<\/pre>\n
      This will help locate the directory where the Linux kernel sources have been deployed. Go to the parent directory, locate the Makefile in it and open it in a text editor:
      \n\"\"<\/li>\n
    6. Locate the recipe for the vmlinux<\/strong> target and add the following line to it:\n
      <TAB>set > kernel-env.txt<\/pre>\n
      \"\"<\/li>\n
    7. Now open the arch\/arm\/KConfig file and comment the lines setting the ARCH_HAS_STRICT_KERNEL_RWX<\/strong> and ARCH_HAS_STRICT_MODULE_RWX<\/strong> parameters:\"\"
      \nThis will allow software breakpoints (not limited to hardware breakpoint registers) inside the kernel and the modules, however would decrease the overall kernel security. Hence we only recommend to keep this option during debugging.<\/li>\n
    8. Now we need to configure Petalinux to apply our changes to the kernel each time it is built. Run the following commands from the kernel source directory:\n
      git commit -a -m \"Prepared for debugging with VisualKernel\"\r\ngit format-patch -1\r\nmkdir -p <Petalinux Project Directory>\/project-spec\/meta-user\/recipes-kernel\/linux\/linux-xlnx\r\ncp 0001-Prepared-for-debugging-with-VisualKernel.patch <Petalinux Project Directory>\/project-spec\/meta-user\/recipes-kernel\/linux\/linux-xlnx<\/pre>\n
      This will create a patch file that can be automatically applied to the Linux kernel.<\/li>\n
    9. Finally, open the <Project Directory>\/project-spec\/meta-user\/recipes-kernel\/linux\/linux-xlnx_%.bbappend<\/strong> file in a text editor (create it if it’s missing) and ensure it mentions the patch file as shown below:\"\"<\/li>\n
    10. Go back to the tab where you ran petalinux-config<\/strong>, save the changes and close the configuration menu. Once the command exits, re-open the\u00a0linux-xlnx_%.bbappend<\/strong> file and locate the last .cfg file listed in the SRC_URI statement. This file will contain the configuration changes we made through the menu. Ensure it contains the “CONFIG_DEBUG_INFO=y” line as otherwise the debug symbols will not be generated:\"\"<\/li>\n
    11. Now you can start building the Petalinux project. Go to the project directory (ensure you use the shell where you ran .\u00a0settings.sh<\/strong>) and run the following command:\n
      petalinux-build<\/pre>\n<\/li>\n
    12. Wait for the build to complete. You can ignore the “missing lsb_release” and “failed to copy built images to tftp dir” errors:\"\"<\/li>\n
    13. Now we will need to locate the kernel-env.txt<\/strong> file produced by our modified build scripts. Run the “find . | grep kernel-env.txt” command in the project directory and take a note of the output. Then run the following command from the project directory:\n
      sed -e 's\/^\\(AS\\|AR\\|NM\\|CPP\\|PATH\\|LD\\|CCLD\\|STRIP\\|CXX\\|OBJCOPY\\|ARCH\\|\r\nRANLIB\\|CROSS_COMPILE\\|CC\\|READELF\\|OBJDUMP\\|TARGET_CFLAGS\\|PETALINUX_.*\r\n\\|KERNEL_.*\\)=\\(.*\\)\/export \\1=\\2\/;t;d' < [full path to kernel-env.txt] > kernel.env<\/pre>\n
      This will convert the dump from the ‘set’ command into a shell script that can be loaded using the ‘.’ command.<\/li>\n
    14. Locate the full path to the GDB executable provided by the Xilinx tools by running “which arm-linux-gnueabihf-gdb”:\"\"<\/li>\n
    15. Finally, open the vmlinux<\/strong> file from the directory of the kernel-env.txt<\/strong> file with gdb<\/strong> and ensure it contains symbols by running the “info line printk” command:\"\"<\/li>\n
    16. Ensure you can boot into the new kernel. Typically, copying the image.ub<\/strong> file (the exact name is different for different boards) to the SD card should be sufficient. You can check the version of the kernel running on the device by running the “uname -a” command on it (not on the build machine):\"\"<\/a><\/li>\n
    17. Now we are ready to import the kernel into VisualKernel. Take a note of the following paths from your setup as you will need them to configure VisualKernel later:
      \n\n\n\n\n\n\n\n\n
      Path<\/th>\nSample value<\/th>\n<\/tr>\n
      Petalinux project directory<\/td>\n\/opt\/pkg\/petalinux\/project<\/td>\n<\/tr>\n
      Kernel environment file<\/td>\n\/opt\/pkg\/petalinux\/project\/kernel.env<\/td>\n<\/tr>\n
      Kernel image with symbols<\/td>\n\/opt\/pkg\/petalinux\/project\/build\/tmp\/work\/plnx_zynq7-xilinx-linux-gnueabi\/linux-xlnx\/4.14-xilinx-v2018.3+gitAUTOINC+eeab73d120-r0\/linux-plnx_zynq7-standard-build\/vmlinux<\/td>\n<\/tr>\n
      Kernel source directory<\/td>\n\/opt\/pkg\/petalinux\/project\/build\/tmp\/work\/plnx_zynq7-xilinx-linux-gnueabi\/linux-xlnx\/4.14-xilinx-v2018.3+gitAUTOINC+eeab73d120-r0\/linux-plnx_zynq7-standard-build\/source<\/td>\n<\/tr>\n
      GDB executable<\/td>\n\/opt\/pkg\/petalinux\/2018.3\/tools\/linux-i386\/gcc-arm-linux-gnueabi\/bin\/arm-linux-gnueabihf-gdb<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n<\/ol>\n
      Follow this tutorial<\/a> to create a basic kernel module for the Petalinux-based kernel using VisualKernel.<\/p>\n
       <\/p>\n","protected":false},"excerpt":{"rendered":"
      This tutorial shows how to prepare a kernel built with the Petalinux tools for importing it into VisualKernel and creating<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[51],"tags":[50,49,48],"_links":{"self":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts\/307"}],"collection":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/comments?post=307"}],"version-history":[{"count":7,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts\/307\/revisions"}],"predecessor-version":[{"id":395,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts\/307\/revisions\/395"}],"wp:attachment":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/media?parent=307"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/categories?post=307"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/tags?post=307"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}