<?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>MCUXpresso IDE中的主题 Assembly Language Input File Format</title>
    <link>https://community.nxp.com/t5/MCUXpresso-IDE/Assembly-Language-Input-File-Format/m-p/972591#M4910</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IDE:&amp;nbsp; MCUXpresso IDE v11.0.0 [Build 2516] [2019-06-05]&lt;/P&gt;&lt;P&gt;OS:&amp;nbsp; Linux (KDE)&lt;/P&gt;&lt;P&gt;Processor:&amp;nbsp; LPC1754&lt;/P&gt;&lt;P&gt;Libraries:&amp;nbsp;&amp;nbsp;CMSIS_CORE_LPC17xx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm having a hard time debugging some inline assembly I've written. I'm competent writing assembly language and this code is just being ported over from a different LPC processor (I wrote that code years ago).&amp;nbsp; The assembly code is currently written as inline and is about 4 pages long.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue I'm having is the MCUxpresso disassembly view is getting lost after a page or so of assembly instruction stepping and a long jump.&amp;nbsp; This used to work perfectly back in the Code Red days.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm thinking moving the code to its own file might help the debugger keep track of things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is I'm having a hard time finding out what the current required format is for the file (and is it .s, .a, .asm. ?).&amp;nbsp; I've tried saving temporaries&amp;nbsp;but but the .s file has a ton of debug stuff in it.&amp;nbsp; I need to know what the format for a hand written input file looks like.&amp;nbsp; I used to be pretty simple, a short header and then the assembly code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, if there's a way to get the debugger to stay in sync with the program counter, that would help a lot too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Aug 2019 21:47:35 GMT</pubDate>
    <dc:creator>jerrydurand</dc:creator>
    <dc:date>2019-08-08T21:47:35Z</dc:date>
    <item>
      <title>Assembly Language Input File Format</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/Assembly-Language-Input-File-Format/m-p/972591#M4910</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IDE:&amp;nbsp; MCUXpresso IDE v11.0.0 [Build 2516] [2019-06-05]&lt;/P&gt;&lt;P&gt;OS:&amp;nbsp; Linux (KDE)&lt;/P&gt;&lt;P&gt;Processor:&amp;nbsp; LPC1754&lt;/P&gt;&lt;P&gt;Libraries:&amp;nbsp;&amp;nbsp;CMSIS_CORE_LPC17xx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm having a hard time debugging some inline assembly I've written. I'm competent writing assembly language and this code is just being ported over from a different LPC processor (I wrote that code years ago).&amp;nbsp; The assembly code is currently written as inline and is about 4 pages long.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue I'm having is the MCUxpresso disassembly view is getting lost after a page or so of assembly instruction stepping and a long jump.&amp;nbsp; This used to work perfectly back in the Code Red days.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm thinking moving the code to its own file might help the debugger keep track of things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is I'm having a hard time finding out what the current required format is for the file (and is it .s, .a, .asm. ?).&amp;nbsp; I've tried saving temporaries&amp;nbsp;but but the .s file has a ton of debug stuff in it.&amp;nbsp; I need to know what the format for a hand written input file looks like.&amp;nbsp; I used to be pretty simple, a short header and then the assembly code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, if there's a way to get the debugger to stay in sync with the program counter, that would help a lot too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Aug 2019 21:47:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/Assembly-Language-Input-File-Format/m-p/972591#M4910</guid>
      <dc:creator>jerrydurand</dc:creator>
      <dc:date>2019-08-08T21:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: Assembly Language Input File Format</title>
      <link>https://community.nxp.com/t5/MCUXpresso-IDE/Assembly-Language-Input-File-Format/m-p/972592#M4911</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've found a default file format that works and am porting to that now.&amp;nbsp; Still, if anyone knows how to keep the debugger in sync with the PC while instruction stepping past long jumps, let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;File format for .asm file (I'm not sure if all the header is needed, but it does work):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[code]&lt;/P&gt;&lt;P&gt;.syntax unified&lt;BR /&gt; .text&lt;/P&gt;&lt;P&gt;.align 2&lt;BR /&gt; .section .text&lt;/P&gt;&lt;P&gt;.global __MyFunction&lt;BR /&gt; .func&lt;BR /&gt; .thumb_func&lt;BR /&gt; .type __MyFunction, %function&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;__MyFunction:&lt;BR /&gt; &amp;nbsp;&amp;nbsp;&amp;nbsp;push {lr} // save return address&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;do stuff here, passed arguments are in r0-r4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;place returned data in r0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;pop {pc}&amp;nbsp;&amp;nbsp;&amp;nbsp;// return from call&lt;/P&gt;&lt;P&gt;[/code]&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Aug 2019 00:15:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCUXpresso-IDE/Assembly-Language-Input-File-Format/m-p/972592#M4911</guid>
      <dc:creator>jerrydurand</dc:creator>
      <dc:date>2019-08-09T00:15:45Z</dc:date>
    </item>
  </channel>
</rss>

