<?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 MPC5777C Censorship Access in MPC5xxx</title>
    <link>https://community.nxp.com/t5/MPC5xxx/MPC5777C-Censorship-Access/m-p/685235#M8358</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;My group is currently trying to access an MPC5777C device that we've censored. &amp;nbsp;We know for sure that the JTAG password is programmed, as well as the password for PASS Group 0 and possibly Group 1, however it's my understanding that we can gain access with only one password.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The life cycle of the device is set to OEM Production.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using the Greenhills MULTI environment. &amp;nbsp;We've successfully been able to reset and halt the device by writing to the jtag_password_hi and jtag_password_lo registers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can read flash memory at this point using the "memory view" window. &amp;nbsp;However, when we try to download a program over the debugger, it seems to fail to read memory at all (i.e. the probe thinks a block is erased when it is actually populated).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally, we're having trouble accessing the CIN0-7 registers. &amp;nbsp;We've successfully written to the PASS_CHSEL register and have seen it change to acknowledge a new master, but writing the password to the CIN area has no effect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone help us better understand how to gain access to the device?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jeff Campbell&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P.S. &amp;nbsp;We figured this out for the most part, turned out it was a matter of having every password group loaded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The question now, though, is exactly how password words map into CIN0-7. &amp;nbsp;The manual says that CIN0 matches with the MSB of the password. &amp;nbsp;Does this mean, for instance, that for Group 0, CIN0 corresponds to the value at 0x00400160?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 May 2017 13:44:04 GMT</pubDate>
    <dc:creator>jeffcampbell</dc:creator>
    <dc:date>2017-05-18T13:44:04Z</dc:date>
    <item>
      <title>MPC5777C Censorship Access</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC5777C-Censorship-Access/m-p/685235#M8358</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;My group is currently trying to access an MPC5777C device that we've censored. &amp;nbsp;We know for sure that the JTAG password is programmed, as well as the password for PASS Group 0 and possibly Group 1, however it's my understanding that we can gain access with only one password.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The life cycle of the device is set to OEM Production.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using the Greenhills MULTI environment. &amp;nbsp;We've successfully been able to reset and halt the device by writing to the jtag_password_hi and jtag_password_lo registers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can read flash memory at this point using the "memory view" window. &amp;nbsp;However, when we try to download a program over the debugger, it seems to fail to read memory at all (i.e. the probe thinks a block is erased when it is actually populated).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additionally, we're having trouble accessing the CIN0-7 registers. &amp;nbsp;We've successfully written to the PASS_CHSEL register and have seen it change to acknowledge a new master, but writing the password to the CIN area has no effect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone help us better understand how to gain access to the device?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jeff Campbell&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;P.S. &amp;nbsp;We figured this out for the most part, turned out it was a matter of having every password group loaded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The question now, though, is exactly how password words map into CIN0-7. &amp;nbsp;The manual says that CIN0 matches with the MSB of the password. &amp;nbsp;Does this mean, for instance, that for Group 0, CIN0 corresponds to the value at 0x00400160?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 May 2017 13:44:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC5777C-Censorship-Access/m-p/685235#M8358</guid>
      <dc:creator>jeffcampbell</dc:creator>
      <dc:date>2017-05-18T13:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: MPC5777C Censorship Access</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC5777C-Censorship-Access/m-p/685236#M8359</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am not familiar with GHS debugging tools (only with compiler).&lt;/P&gt;&lt;P&gt;However there is no known issue when you unlock memory with programmed JTAG password to censored device.&lt;/P&gt;&lt;P&gt;You are now in &lt;STRONG&gt;OEM production or in field &lt;/STRONG&gt;life cycle with programed DCF censorship client (JTAG Password).&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/21593i2AD281965D927445/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;As you can see from above table the device is always read protected. Never only write protected. So without correct password you are not able even to read flash.&lt;/P&gt;&lt;P&gt;Before we can proceed further:&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P&gt;We can read flash memory at this point using the "memory view" window. &amp;nbsp;However, when we try to download a program over the debugger, it seems to fail to read memory at all (i.e. the probe thinks a block is erased when it is actually populated).&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Did you tried to use different debuggers? Like Lauterbach or PEMicro? Or just GHS probe?&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 May 2017 09:55:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC5777C-Censorship-Access/m-p/685236#M8359</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2017-05-19T09:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: MPC5777C Censorship Access</title>
      <link>https://community.nxp.com/t5/MPC5xxx/MPC5777C-Censorship-Access/m-p/685237#M8360</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Peter,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the quick response. &amp;nbsp;We only use the GHS probe, and will be in touch with Greenhills for further specific support there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Jeff&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 May 2017 12:30:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/MPC5777C-Censorship-Access/m-p/685237#M8360</guid>
      <dc:creator>jeffcampbell</dc:creator>
      <dc:date>2017-05-19T12:30:43Z</dc:date>
    </item>
  </channel>
</rss>

