<?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>OSBDM and TBDMLのトピックRe: command line</title>
    <link>https://community.nxp.com/t5/OSBDM-and-TBDML/command-line/m-p/893887#M3610</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also had this same problem when using the application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to receive the appropriate error code from the command line, use "start/wait" to run the application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, using the command you posted "start/wait UsbdmFlashProgrammer.exe -requiredBdm=USBDM-JS16-SWD_SER-0001 -target=s12z FCA_WL_SBMD_A_02_01.sx -device=MC9S12ZVL32 -erase=mass -program -verify -secure"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason running the application on the command line without "start/wait" does not work as expected is that the application is inherently a GUI application, therefore when run from the command line, the console does not wait for the application's process to complete execution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On a side note, the "-program" command option also includes verify, therefore you don't need to include a "-verify" in the command. You can use "-verify" without "-program" if you specifically want to verify only.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Sep 2019 07:58:31 GMT</pubDate>
    <dc:creator>a_cyril</dc:creator>
    <dc:date>2019-09-04T07:58:31Z</dc:date>
    <item>
      <title>command line</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/command-line/m-p/893886#M3609</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;no feedback when using command line "UsbdmFlashProgrammer.exe -requiredBdm=USBDM-JS16-SWD_SER-0001 -target=s12z FCA_WL_SBMD_A_02_01.sx -device=MC9S12ZVL32 -erase=mass -program -verify -secure"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but from&amp;nbsp;&lt;A href="http://usbdm.sourceforge.net/USBDM_V4.12/USBDM_FlashProgrammers/html/index.html#sectionCommandLine"&gt;http://usbdm.sourceforge.net/USBDM_V4.12/USBDM_FlashProgrammers/html/index.html#sectionCommandLine&lt;/A&gt;,&amp;nbsp;&lt;SPAN style="color: #000000; background-color: #ffffff; font-size: 14px;"&gt;The program sets the error code to 0 on success, non-zero otherwise.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how to solve the issue?&lt;/P&gt;&lt;P&gt;PS, USBDM version is 4.12.1.210 and win10 64bit, and GUI mode works fine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 May 2019 13:44:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/command-line/m-p/893886#M3609</guid>
      <dc:creator>gabledon</dc:creator>
      <dc:date>2019-05-14T13:44:33Z</dc:date>
    </item>
    <item>
      <title>Re: command line</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/command-line/m-p/893887#M3610</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also had this same problem when using the application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to receive the appropriate error code from the command line, use "start/wait" to run the application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, using the command you posted "start/wait UsbdmFlashProgrammer.exe -requiredBdm=USBDM-JS16-SWD_SER-0001 -target=s12z FCA_WL_SBMD_A_02_01.sx -device=MC9S12ZVL32 -erase=mass -program -verify -secure"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason running the application on the command line without "start/wait" does not work as expected is that the application is inherently a GUI application, therefore when run from the command line, the console does not wait for the application's process to complete execution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On a side note, the "-program" command option also includes verify, therefore you don't need to include a "-verify" in the command. You can use "-verify" without "-program" if you specifically want to verify only.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Sep 2019 07:58:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/command-line/m-p/893887#M3610</guid>
      <dc:creator>a_cyril</dc:creator>
      <dc:date>2019-09-04T07:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: command line</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/command-line/m-p/1175511#M3629</link>
      <description>&lt;P&gt;Hi i am new with usbdm,&lt;/P&gt;&lt;P&gt;How can i get the result to know if the processor has been programed or not using cmd?&lt;/P&gt;&lt;P&gt;what should i add to see the result in this command.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;"start/wait UsbdmFlashProgrammer.exe -requiredBdm=USBDM-JS16-SWD_SER-0001 -target=s12z FCA_WL_SBMD_A_02_01.sx -device=MC9S12ZVL32 -erase=mass -program"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Thu, 29 Oct 2020 21:12:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/command-line/m-p/1175511#M3629</guid>
      <dc:creator>S21L</dc:creator>
      <dc:date>2020-10-29T21:12:05Z</dc:date>
    </item>
  </channel>
</rss>

