<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cross-compiling device driver with Visual Studio Code in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376905#M183530</link>
    <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/193741"&gt;@hello-world123&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; It would be better to build toolchain, build / load Kernel in standalone environment,&lt;BR /&gt;as mentioned in "IMX_PORTING_GUIDE.pdf", unpack driver package with sources &lt;BR /&gt;and follow driver's documentation. Yocto approach is not used here.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Yuri.&lt;/P&gt;</description>
    <pubDate>Thu, 25 Nov 2021 08:50:24 GMT</pubDate>
    <dc:creator>Yuri</dc:creator>
    <dc:date>2021-11-25T08:50:24Z</dc:date>
    <item>
      <title>Cross-compiling device driver with Visual Studio Code</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1375979#M183461</link>
      <description>&lt;P&gt;Hello, My name is john. I'm currently building cross-compile environment with visual studio code.&lt;/P&gt;&lt;P&gt;With Variscite's document and NXP's i.MX Porting Guide, I successfully built user-space application cross-compile environment with visual studio code.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The following links are what I referred.&lt;/P&gt;&lt;P&gt;Variscite's document&lt;/P&gt;&lt;P&gt;&lt;A href="https://variwiki.com/index.php?title=Yocto_Programming_with_VSCode&amp;amp;release=RELEASE_HARDKNOTT_V1.0_DART-MX8M-MINI#Install_Yocto_Toolchain" target="_blank"&gt;https://variwiki.com/index.php?title=Yocto_Programming_with_VSCode&amp;amp;release=RELEASE_HARDKNOTT_V1.0_DART-MX8M-MINI#Install_Yocto_Toolchain&lt;/A&gt;&lt;/P&gt;&lt;P&gt;NXP's document (2.1.1 How to build and load Kernel in standalone environment)&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.nxp.com/docs/en/user-guide/IMX_PORTING_GUIDE.pdf" target="_blank"&gt;https://www.nxp.com/docs/en/user-guide/IMX_PORTING_GUIDE.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I want to build device driver with the same method, but I have difficulties about setting kernel headers.&lt;/P&gt;&lt;P&gt;When I bitbake, I added the following to my recipe to include kernel source to sdk which generated by populate_sdk.&lt;/P&gt;&lt;P&gt;TOOLCHAIN_TARGET_TASK_append = " kernel-devsrc"&lt;/P&gt;&lt;P&gt;I made dummy device driver 'dummy.c' in&amp;nbsp;&lt;A href="https://github.com/PacktPublishing/Mastering-Embedded-Linux-Programming-Second-Edition/blob/master/Chapter09/dummy-driver/dummy.c" target="_blank"&gt;https://github.com/PacktPublishing/Mastering-Embedded-Linux-Programming-Second-Edition/blob/master/Chapter09/dummy-driver/dummy.c&lt;/A&gt;&lt;/P&gt;&lt;P&gt;With dummy.c, I run 'make' and VScode show me lots of errors. I think I have to match kernel header carefully, but I don't know how to do.&lt;/P&gt;&lt;P&gt;&amp;nbsp;The following figure is errors which VScode shows to me.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Daewoong92_0-1637733707482.png" style="width: 700px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/163036i9446D5E126AC9E55/image-dimensions/700x322?v=v2" width="700" height="322" role="button" title="Daewoong92_0-1637733707482.png" alt="Daewoong92_0-1637733707482.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The following figure is my c_cpp_properties.json in VScode and my SDK's location is '/opt/fsl-imx-wayland/4.14-sumo/sysroots/aarch64-poky-linux/*'.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Daewoong92_1-1637733859981.png" style="width: 698px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/163037i9CEF9036AD76AD15/image-dimensions/698x274?v=v2" width="698" height="274" role="button" title="Daewoong92_1-1637733859981.png" alt="Daewoong92_1-1637733859981.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The following figure is my Makefile in VScode.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Daewoong92_2-1637733914999.png" style="width: 699px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/163038iB6017DC935B6D172/image-dimensions/699x219?v=v2" width="699" height="219" role="button" title="Daewoong92_2-1637733914999.png" alt="Daewoong92_2-1637733914999.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Nov 2021 06:06:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1375979#M183461</guid>
      <dc:creator>hello-world123</dc:creator>
      <dc:date>2021-11-24T06:06:00Z</dc:date>
    </item>
    <item>
      <title>Re: Cross-compiling device driver with Visual Studio Code</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376175#M183473</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/193741"&gt;@hello-world123&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; VSCode can be used for development of relatively simple applications.&lt;BR /&gt;Hardly it is suitable for Linux driver design, since this area is very kernel / version&lt;BR /&gt;sensitive. &amp;nbsp; I think it makes sense to rely on standard approaches here.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Yuri.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Nov 2021 09:30:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376175#M183473</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2021-11-24T09:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: Cross-compiling device driver with Visual Studio Code</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376195#M183477</link>
      <description>&lt;P&gt;Is there a manual for cross compiling?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2022 06:20:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376195#M183477</guid>
      <dc:creator>bladerunner1010</dc:creator>
      <dc:date>2022-07-25T06:20:07Z</dc:date>
    </item>
    <item>
      <title>Re: Cross-compiling device driver with Visual Studio Code</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376752#M183518</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/190113"&gt;@bladerunner1010&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp; usually driver sources are provided with instructions how to compile them.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Yuri.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2021 06:12:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376752#M183518</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2021-11-25T06:12:24Z</dc:date>
    </item>
    <item>
      <title>Re: Cross-compiling device driver with Visual Studio Code</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376828#M183524</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/1941"&gt;@Yuri&lt;/a&gt;&amp;nbsp;. Thank you for your reply.&lt;/P&gt;&lt;P&gt;Your saying is that typical way to develop device driver is like this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Edit/add device driver code and Makefile of kernel source in Yocto build directory with editor like vim.&lt;/P&gt;&lt;P&gt;2. Bitbake to build.&lt;/P&gt;&lt;P&gt;3. Test the device driver&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If so, I think it's quite&amp;nbsp;inefficient ways for developing.&lt;/P&gt;&lt;P&gt;According to your mention, am I understand right?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2021 08:03:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376828#M183524</guid>
      <dc:creator>hello-world123</dc:creator>
      <dc:date>2021-11-25T08:03:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cross-compiling device driver with Visual Studio Code</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376905#M183530</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/193741"&gt;@hello-world123&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; It would be better to build toolchain, build / load Kernel in standalone environment,&lt;BR /&gt;as mentioned in "IMX_PORTING_GUIDE.pdf", unpack driver package with sources &lt;BR /&gt;and follow driver's documentation. Yocto approach is not used here.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Yuri.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2021 08:50:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Cross-compiling-device-driver-with-Visual-Studio-Code/m-p/1376905#M183530</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2021-11-25T08:50:24Z</dc:date>
    </item>
  </channel>
</rss>

