<?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: TBDML + OSBDM ??</title>
    <link>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157039#M879</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;Sorry I haven't been around much lately...&lt;BR /&gt;&lt;BR /&gt;The hardware can do it and so does the debugger.&lt;BR /&gt;The issue is more in the different DLL that interface the debug cable with CodeWarrior.&lt;BR /&gt;You would need to rewrite the code of the JB16 for the OSBDM08 to be compatible with the DLL of the TBDML. Please note that there are slight differences between the two BDM and that is why one is not supporting the other.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Alban.&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 13 Nov 2007 04:48:58 GMT</pubDate>
    <dc:creator>Nabla69</dc:creator>
    <dc:date>2007-11-13T04:48:58Z</dc:date>
    <item>
      <title>TBDML + OSBDM ??</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157037#M877</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Does anyone know what it would take to create a version that would support both S08 and S12 devices?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I know the hardware can support them.&amp;nbsp; I don't see why the firmware could not be modified, but what about the DLL files?&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Would changes to the Codewarrior debugger&amp;nbsp;have to be made to recognize the TBDML and OSBDM as one in the same?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks,&lt;/DIV&gt;&lt;DIV&gt;BadDad&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Oct 2007 22:13:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157037#M877</guid>
      <dc:creator>baddad</dc:creator>
      <dc:date>2007-10-19T22:13:19Z</dc:date>
    </item>
    <item>
      <title>Re: TBDML + OSBDM ??</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157038#M878</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Well, TBDML.DLL and OPENSOURCEBDM.DLL have a different, but similar interfaces.&lt;BR /&gt;To make it so there are no changes to the debugger, I suppose you would have to make a new version&lt;BR /&gt;of OPENSOURCEBDM.DLL that talked to the TBDML instead.&lt;BR /&gt;&lt;BR /&gt;As for the firrmware, download the source code for both fo thern, and see what it would take to merge the code.&lt;BR /&gt;&lt;BR /&gt;_LibMain@12&lt;BR /&gt;_opensourcebdm_bdm_sts@4&lt;BR /&gt;_opensourcebdm_close@0&lt;BR /&gt;_opensourcebdm_dll_version@0&lt;BR /&gt;_opensourcebdm_get_last_sts@0&lt;BR /&gt;_opensourcebdm_get_speed@0&lt;BR /&gt;_opensourcebdm_get_version@0&lt;BR /&gt;_opensourcebdm_init@0&lt;BR /&gt;_opensourcebdm_mem_dlend@0&lt;BR /&gt;_opensourcebdm_mem_dlstart@0&lt;BR /&gt;_opensourcebdm_open@4&lt;BR /&gt;_opensourcebdm_read_bkpt@0&lt;BR /&gt;_opensourcebdm_read_block@12&lt;BR /&gt;_opensourcebdm_read_byte@4&lt;BR /&gt;_opensourcebdm_read_regs@4&lt;BR /&gt;_opensourcebdm_read_status@0&lt;BR /&gt;_opensourcebdm_set_speed@4&lt;BR /&gt;_opensourcebdm_set_target_type@4&lt;BR /&gt;_opensourcebdm_target_go@0&lt;BR /&gt;_opensourcebdm_target_halt@0&lt;BR /&gt;_opensourcebdm_target_readyfor_datald@0&lt;BR /&gt;_opensourcebdm_target_reset@4&lt;BR /&gt;_opensourcebdm_target_step@0&lt;BR /&gt;_opensourcebdm_target_sync@0&lt;BR /&gt;_opensourcebdm_write_bkpt@4&lt;BR /&gt;_opensourcebdm_write_block@12&lt;BR /&gt;_opensourcebdm_write_byte@8&lt;BR /&gt;_opensourcebdm_write_control@4&lt;BR /&gt;_opensourcebdm_write_reg_ccr@4&lt;BR /&gt;_opensourcebdm_write_reg_d@4&lt;BR /&gt;_opensourcebdm_write_reg_pc@4&lt;BR /&gt;_opensourcebdm_write_reg_sp@4&lt;BR /&gt;_opensourcebdm_write_reg_x@4&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;_LibMain@12&lt;BR /&gt;_tbdml_bdm_sts@4&lt;BR /&gt;_tbdml_close@0&lt;BR /&gt;_tbdml_dll_version@0&lt;BR /&gt;_tbdml_get_last_sts@0&lt;BR /&gt;_tbdml_get_speed@0&lt;BR /&gt;_tbdml_get_version@0&lt;BR /&gt;_tbdml_init@0&lt;BR /&gt;_tbdml_open@4&lt;BR /&gt;_tbdml_read_bd@4&lt;BR /&gt;_tbdml_read_block@12&lt;BR /&gt;_tbdml_read_byte@4&lt;BR /&gt;_tbdml_read_regs@4&lt;BR /&gt;_tbdml_read_word@4&lt;BR /&gt;_tbdml_set_speed@4&lt;BR /&gt;_tbdml_set_target_type@4&lt;BR /&gt;_tbdml_target_go@0&lt;BR /&gt;_tbdml_target_halt@0&lt;BR /&gt;_tbdml_target_reset@4&lt;BR /&gt;_tbdml_target_step@0&lt;BR /&gt;_tbdml_target_sync@0&lt;BR /&gt;_tbdml_write_bd@8&lt;BR /&gt;_tbdml_write_block@12&lt;BR /&gt;_tbdml_write_byte@8&lt;BR /&gt;_tbdml_write_reg_ccr@4&lt;BR /&gt;_tbdml_write_reg_d@4&lt;BR /&gt;_tbdml_write_reg_pc@4&lt;BR /&gt;_tbdml_write_reg_sp@4&lt;BR /&gt;_tbdml_write_reg_x@4&lt;BR /&gt;_tbdml_write_reg_y@4&lt;BR /&gt;_tbdml_write_word@8&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Oct 2007 08:04:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157038#M878</guid>
      <dc:creator>JimDon</dc:creator>
      <dc:date>2007-10-24T08:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: TBDML + OSBDM ??</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157039#M879</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;Sorry I haven't been around much lately...&lt;BR /&gt;&lt;BR /&gt;The hardware can do it and so does the debugger.&lt;BR /&gt;The issue is more in the different DLL that interface the debug cable with CodeWarrior.&lt;BR /&gt;You would need to rewrite the code of the JB16 for the OSBDM08 to be compatible with the DLL of the TBDML. Please note that there are slight differences between the two BDM and that is why one is not supporting the other.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Alban.&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Nov 2007 04:48:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157039#M879</guid>
      <dc:creator>Nabla69</dc:creator>
      <dc:date>2007-11-13T04:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: TBDML + OSBDM ??</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157040#M880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;SPAN class="title_big"&gt;Of course, the JM code needs to be changed as well. The problem is the GDI dll for the OSBDM does not currently use TBDML.DLL or those entry points, so my point is you would write a replacement DLL that "talks" to the new code in the JM chip, but "looks Like" the old DLL.&lt;BR /&gt;&lt;BR /&gt;The big question is where did&amp;nbsp; DanielM get off to?&lt;BR /&gt;&lt;BR /&gt;He could probably figure out the details quickly....&lt;BR /&gt;&lt;/SPAN&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Nov 2007 05:10:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157040#M880</guid>
      <dc:creator>JimDon</dc:creator>
      <dc:date>2007-11-13T05:10:46Z</dc:date>
    </item>
    <item>
      <title>Re: TBDML + OSBDM ??</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157041#M881</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;Hi&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I'm interested in taking a JB16 debugger system that supports 08 parts and giving it support for s12 parts as well using Turbo BDM.&amp;nbsp; I know I need to alter the dlls.&amp;nbsp; Do you know where I can find the source to the dlls?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Jan 2009 04:15:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157041#M881</guid>
      <dc:creator>gnzork</dc:creator>
      <dc:date>2009-01-28T04:15:18Z</dc:date>
    </item>
    <item>
      <title>Re: TBDML + OSBDM ??</title>
      <link>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157042#M882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;/DIV&gt;Dear Macias,&lt;BR /&gt;&lt;BR /&gt;Not really worth doing - unless for interest &lt;IMG alt=":smileyhappy:" class="emoticon emoticon-smileyhappy" id="smileyhappy" src="http://freescale.i.lithium.com/i/smilies/16x16_smiley-happy.gif" title="Smiley Happy" /&gt;&lt;BR /&gt;&lt;BR /&gt;Please see this link:&lt;BR /&gt;&lt;BR /&gt;&lt;A class="subj_read" href="http://forums.freescale.com/message?board.id=TBDML&amp;amp;thread.id=240" rel="nofollow" target="_blank"&gt;Combined TBDML/OSBDM Code&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;bye&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;BR /&gt;&lt;BR /&gt;Message Edited by pgo on &lt;SPAN class="date_text"&gt;2009-01-28&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;06:18 AM&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;Message Edited by pgo on &lt;SPAN class="date_text"&gt;2009-01-28&lt;/SPAN&gt; &lt;SPAN class="time_text"&gt;06:20 AM&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Jan 2009 14:16:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/OSBDM-and-TBDML/TBDML-OSBDM/m-p/157042#M882</guid>
      <dc:creator>pgo</dc:creator>
      <dc:date>2009-01-28T14:16:55Z</dc:date>
    </item>
  </channel>
</rss>

