<?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>MQX Software SolutionsのトピックTrouble running MQX USB stack from DRAM (K61)</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/Trouble-running-MQX-USB-stack-from-DRAM-K61/m-p/259006#M7668</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm working on a K61-based product whose main application runs from DRAM.&amp;nbsp; I use MQX 4.x RTOS, RTCS &amp;amp; the MQX USB stack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to use the USB device stack in order to have serial port emulation.&amp;nbsp; This port will act as the main terminal-mode user interface for the product, so I'm basing my USB code on the CDC demo application.&amp;nbsp; I've been able to get the stack running on a FLASH-based boot-loader application.&amp;nbsp; At some point, the boot-loader copies the RAM-based application to DRAM and jumps to it.&amp;nbsp; The RAM-based application is also MQX-based.&amp;nbsp; This all works fine, with the exception of the USB stack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The code that configures the USB parts of the processor is identical to that of the FLASH-based boot loader and the rest of the system clocking and configuration is also taken care of by the boot-loader.&amp;nbsp; I've confirmed that the register values remain the same across execution from the boot loader to the RAM application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I initially added in the USB stack to the RAM application, I made no changes.&amp;nbsp; After having trouble and confirming the hardware configuration was the same, I took a shot and relocated the USB buffer descriptors from DRAM to the K61 internal SRAM, at the same location as they were in the boot-loader.&amp;nbsp; The PC gets further along the enumeration process, in that instead of showing an unrecognized device, it now sees a Virtual COM port.&amp;nbsp; However, the PC claims the USB device won't start.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My application portion of the code has a call-out routine that is invoked at various points along the stack's enumeration process, yet it never reaches the "USB_APP_ENUM_COMPLETE" stage (based on the CDC demo project provided with the MQX USB stack).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, has anyone experienced anything like this?&amp;nbsp; I'm mystified that relocating the BDT to SRAM made any difference and more mystified by the fact that it doesn't work directly from DRAM.&amp;nbsp; Could this be related to cache-able regions or something like that?&amp;nbsp; Or, is there configuration somewhere that assumes the code will run from FLASH and data will be located in SRAM?&amp;nbsp; Why would it run perfectly well from FLASH/SRAM and not DRAM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for any help,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Todd&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Oct 2013 18:46:53 GMT</pubDate>
    <dc:creator>twadepgh</dc:creator>
    <dc:date>2013-10-01T18:46:53Z</dc:date>
    <item>
      <title>Trouble running MQX USB stack from DRAM (K61)</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Trouble-running-MQX-USB-stack-from-DRAM-K61/m-p/259006#M7668</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm working on a K61-based product whose main application runs from DRAM.&amp;nbsp; I use MQX 4.x RTOS, RTCS &amp;amp; the MQX USB stack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I need to use the USB device stack in order to have serial port emulation.&amp;nbsp; This port will act as the main terminal-mode user interface for the product, so I'm basing my USB code on the CDC demo application.&amp;nbsp; I've been able to get the stack running on a FLASH-based boot-loader application.&amp;nbsp; At some point, the boot-loader copies the RAM-based application to DRAM and jumps to it.&amp;nbsp; The RAM-based application is also MQX-based.&amp;nbsp; This all works fine, with the exception of the USB stack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The code that configures the USB parts of the processor is identical to that of the FLASH-based boot loader and the rest of the system clocking and configuration is also taken care of by the boot-loader.&amp;nbsp; I've confirmed that the register values remain the same across execution from the boot loader to the RAM application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I initially added in the USB stack to the RAM application, I made no changes.&amp;nbsp; After having trouble and confirming the hardware configuration was the same, I took a shot and relocated the USB buffer descriptors from DRAM to the K61 internal SRAM, at the same location as they were in the boot-loader.&amp;nbsp; The PC gets further along the enumeration process, in that instead of showing an unrecognized device, it now sees a Virtual COM port.&amp;nbsp; However, the PC claims the USB device won't start.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My application portion of the code has a call-out routine that is invoked at various points along the stack's enumeration process, yet it never reaches the "USB_APP_ENUM_COMPLETE" stage (based on the CDC demo project provided with the MQX USB stack).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, has anyone experienced anything like this?&amp;nbsp; I'm mystified that relocating the BDT to SRAM made any difference and more mystified by the fact that it doesn't work directly from DRAM.&amp;nbsp; Could this be related to cache-able regions or something like that?&amp;nbsp; Or, is there configuration somewhere that assumes the code will run from FLASH and data will be located in SRAM?&amp;nbsp; Why would it run perfectly well from FLASH/SRAM and not DRAM?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for any help,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Todd&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Oct 2013 18:46:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Trouble-running-MQX-USB-stack-from-DRAM-K61/m-p/259006#M7668</guid>
      <dc:creator>twadepgh</dc:creator>
      <dc:date>2013-10-01T18:46:53Z</dc:date>
    </item>
  </channel>
</rss>

