<?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>S32 Design StudioのトピックRe: MPC5748G AUTOSAR MCAL: Machine Check Interrupt</title>
    <link>https://community.nxp.com/t5/S32-Design-Studio/MPC5748G-AUTOSAR-MCAL-Machine-Check-Interrupt/m-p/766063#M2840</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dimitry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd suspect that machine check exception&amp;nbsp;could be related to the code execution issue rather than the debug probe you are using.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding flashing fail - could you possibly send us the debug console screenshot so we better understand what is going on here.&lt;/P&gt;&lt;P&gt;It should be possible to program your executable file with OpenSDA interface. Anyway there might always be a bug in the flasher that hasn't been revealed yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a general suggestion&amp;nbsp; I'd recommend you to check if the generated flash image fits into Flash memory boundaries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you also attach the generated elf file?&lt;/P&gt;&lt;P&gt;This will help us to resolve this issue much faster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 Feb 2018 14:43:11 GMT</pubDate>
    <dc:creator>stanish</dc:creator>
    <dc:date>2018-02-01T14:43:11Z</dc:date>
    <item>
      <title>MPC5748G AUTOSAR MCAL: Machine Check Interrupt</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/MPC5748G-AUTOSAR-MCAL-Machine-Check-Interrupt/m-p/766062#M2839</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I try to study how to work with AUTOSAR on MPC5748G board&amp;nbsp;The application sample is&amp;nbsp;&lt;SPAN&gt;MPC574XG_MCAL4_0_RTM_1_0_4_Sample_Application.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is my environment:&lt;/P&gt;&lt;P&gt;1. Windows&lt;/P&gt;&lt;P&gt;2. AUTOSAR MCAL AND OS:&amp;nbsp;MPC574xG_AUTOSAR_OS_4_0_92_RTM_1_0_3,&amp;nbsp;MPC574XG_MCAL4_0_RTM_1_0_4&lt;/P&gt;&lt;P&gt;3. EB Tresos 14.2&lt;/P&gt;&lt;P&gt;4.&amp;nbsp;S32 Design Studio for Power Architecture Version 2017.R1&lt;/P&gt;&lt;P&gt;5. Diab compiler 5.9&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Documentation (provided with&amp;nbsp;&lt;SPAN&gt;MPC574XG_MCAL4_0_RTM_1_0_4_Sample_Application) describes that application is flashed by Lauterbach Trace32 PowerView.&amp;nbsp; Unfortunately, I can't use this tool. So I try to flash application by&amp;nbsp;S32 Design Studio throught OpenSDA interface with nxp_mpc5748g_1x32x1520k_cflash.pcp flash algorithm. If application's elf file was built without OS, flashing is successfull and I see application's code throught debug session. But I get "&lt;SPAN&gt;Machine Check Interrupt" after start of&amp;nbsp;application. If application was build with OS, flashing fails.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible that&amp;nbsp;&lt;SPAN&gt;nxp_mpc5748g_1x32x1520k_cflash&lt;/SPAN&gt; flash algorithm can lead to&amp;nbsp;&lt;SPAN&gt;Machine Check Interrupt? If so, could any advise how to make AUTOSAR application's&amp;nbsp;flash algorithm which valid for S32&amp;nbsp;Design Studio?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;--&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in advance,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Dmitry Y.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;mpc5748g&amp;nbsp; autosar&amp;nbsp;s32 e200‌ diab compiler‌ machine_check‌ ‌flash mcu‌ pemicro‌ debuger‌ opensda‌&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Jan 2018 15:07:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/MPC5748G-AUTOSAR-MCAL-Machine-Check-Interrupt/m-p/766062#M2839</guid>
      <dc:creator>dmitryyudenich</dc:creator>
      <dc:date>2018-01-29T15:07:04Z</dc:date>
    </item>
    <item>
      <title>Re: MPC5748G AUTOSAR MCAL: Machine Check Interrupt</title>
      <link>https://community.nxp.com/t5/S32-Design-Studio/MPC5748G-AUTOSAR-MCAL-Machine-Check-Interrupt/m-p/766063#M2840</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Dimitry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd suspect that machine check exception&amp;nbsp;could be related to the code execution issue rather than the debug probe you are using.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regarding flashing fail - could you possibly send us the debug console screenshot so we better understand what is going on here.&lt;/P&gt;&lt;P&gt;It should be possible to program your executable file with OpenSDA interface. Anyway there might always be a bug in the flasher that hasn't been revealed yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a general suggestion&amp;nbsp; I'd recommend you to check if the generated flash image fits into Flash memory boundaries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you also attach the generated elf file?&lt;/P&gt;&lt;P&gt;This will help us to resolve this issue much faster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Stan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2018 14:43:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32-Design-Studio/MPC5748G-AUTOSAR-MCAL-Machine-Check-Interrupt/m-p/766063#M2840</guid>
      <dc:creator>stanish</dc:creator>
      <dc:date>2018-02-01T14:43:11Z</dc:date>
    </item>
  </channel>
</rss>

