<?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 Help to debug VCOM+FreeRTOS example on KDS in Kinetis Software Development Kit</title>
    <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Help-to-debug-VCOM-FreeRTOS-example-on-KDS/m-p/612228#M6338</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I modified the code from the VCOM + FreeRTOS example from the SDK.&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My setup:&lt;/P&gt;&lt;P&gt;FRDMK82f &amp;nbsp; --&amp;gt; usb --&amp;gt; Win7 PC --&amp;gt; Virtualbox --&amp;gt; Ubuntu14.04 --&amp;gt; Kinetis DesignStudio&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am able to communicate with the CDC device when I program the board using JLinkEXE.&lt;/P&gt;&lt;P&gt;I am also able to start the debugging from KDS. In other words, I see that the 'main' starts to run.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have also installed the FreeRTOS Task Aware Debugger for GDB.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The difference I see is that the VCOM device cannot connect to the virtual machine when in debugging mode. The USB device is reported as "busy". I read somewhere on the net that this may be the result of some MPU protection. But no more details on why or where to change this. I am also not sure if there could be another setting that stops me from using the VCOM device in a normal way when debugging.&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I cannot test my application without communicating with the VCOM device.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any pointers will be greatly appreciated.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Javier&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;EDIT: In order to discard the effects of using a virtual machine, I am now testing on a laptop that has Ubuntu 14.04 installed. My observations are pretty much the same. In other words, when running the application without a debugger, I can communicate with the CDC VCOM device. However when I try to open the same device while in debug mode (in Kinetis design studio), the VCOM device is simply not reported.&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;dmesg says : "device not accepting address N, error -32"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 28 Oct 2016 15:02:21 GMT</pubDate>
    <dc:creator>javiersoriano</dc:creator>
    <dc:date>2016-10-28T15:02:21Z</dc:date>
    <item>
      <title>Help to debug VCOM+FreeRTOS example on KDS</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Help-to-debug-VCOM-FreeRTOS-example-on-KDS/m-p/612228#M6338</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I modified the code from the VCOM + FreeRTOS example from the SDK.&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My setup:&lt;/P&gt;&lt;P&gt;FRDMK82f &amp;nbsp; --&amp;gt; usb --&amp;gt; Win7 PC --&amp;gt; Virtualbox --&amp;gt; Ubuntu14.04 --&amp;gt; Kinetis DesignStudio&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am able to communicate with the CDC device when I program the board using JLinkEXE.&lt;/P&gt;&lt;P&gt;I am also able to start the debugging from KDS. In other words, I see that the 'main' starts to run.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have also installed the FreeRTOS Task Aware Debugger for GDB.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The difference I see is that the VCOM device cannot connect to the virtual machine when in debugging mode. The USB device is reported as "busy". I read somewhere on the net that this may be the result of some MPU protection. But no more details on why or where to change this. I am also not sure if there could be another setting that stops me from using the VCOM device in a normal way when debugging.&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I cannot test my application without communicating with the VCOM device.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any pointers will be greatly appreciated.&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Javier&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;EDIT: In order to discard the effects of using a virtual machine, I am now testing on a laptop that has Ubuntu 14.04 installed. My observations are pretty much the same. In other words, when running the application without a debugger, I can communicate with the CDC VCOM device. However when I try to open the same device while in debug mode (in Kinetis design studio), the VCOM device is simply not reported.&amp;nbsp;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;dmesg says : "device not accepting address N, error -32"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Oct 2016 15:02:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Help-to-debug-VCOM-FreeRTOS-example-on-KDS/m-p/612228#M6338</guid>
      <dc:creator>javiersoriano</dc:creator>
      <dc:date>2016-10-28T15:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: Help to debug VCOM+FreeRTOS example on KDS</title>
      <link>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Help-to-debug-VCOM-FreeRTOS-example-on-KDS/m-p/612229#M6339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am sorry for the delay.&lt;/P&gt;&lt;P&gt;Regarding your question that VCOM can not work in debug mode, I do not think it is related to MPU protection, anyway, you can disable MPU by the code: MPU_CESR&amp;amp;=~(0x01); //clear VLD bit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because the K82 uses interrupt mechanism to transfer data, if you debug step by step, the interrupt can not be triggered, how about click&amp;nbsp; "go" so that the K82 can run in normal mode.&lt;/P&gt;&lt;P&gt;Hope it can help you&lt;/P&gt;&lt;P&gt;BR&lt;/P&gt;&lt;P&gt;XiangJun Rong&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Dec 2016 07:06:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Software-Development-Kit/Help-to-debug-VCOM-FreeRTOS-example-on-KDS/m-p/612229#M6339</guid>
      <dc:creator>xiangjun_rong</dc:creator>
      <dc:date>2016-12-14T07:06:12Z</dc:date>
    </item>
  </channel>
</rss>

