<?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>S32KのトピックRe: A question about ECUbus</title>
    <link>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1450391#M15176</link>
    <description>&lt;P&gt;Hello technical support: How does FLASH DRIVER map to RAM, that is how your flash_api.bin is made, is there any source code, can you provide it?&lt;BR /&gt;At present, I want to change the FLASH DRIVER mapping address to another (not starting from 0x1FFF8010) to another RAM address. I have tried several times and failed, so I would like to ask you how to make flash_api.bin. Can you provide the source code?&lt;/P&gt;</description>
    <pubDate>Thu, 28 Apr 2022 04:09:12 GMT</pubDate>
    <dc:creator>ywjack</dc:creator>
    <dc:date>2022-04-28T04:09:12Z</dc:date>
    <item>
      <title>A question about ECUbus</title>
      <link>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1444984#M15006</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="微信截图_20220418152516.png" style="width: 676px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/177143i16FA731CFDAF087B/image-size/large?v=v2&amp;amp;px=999" role="button" title="微信截图_20220418152516.png" alt="微信截图_20220418152516.png" /&gt;&lt;/span&gt;I am using NXP to provide S32KXX series BOOTLODER DEMO project debugging () unified_bootloader_framework) I am using S32K144, so NXP also provides a host computer software (ECUbus) to download the .BIN file generated by MCU compilation. During the debugging process, I found an ECUbus The problem is that I have some doubts,&lt;BR /&gt;The specific problem is: when downloading the .BIN (FLASH file) through the UDS 36 service, I found that the data length of each frame (in the 36 service frame) is 128, except for 36 01/02/03...etc. There are only 126 bytes, and as long as the FLASH programming starts with 128 bytes, it is not enough to fill OXFF. In this way, the last two bytes of some lines of FLASH are erased into OXFF every time. Therefore, I think whether the ECU bus can be made into 36 services to transmit data as 130 bytes as a frame.&lt;BR /&gt;The description is not clear, you can see my screenshot below&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2022 07:26:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1444984#M15006</guid>
      <dc:creator>ywjack</dc:creator>
      <dc:date>2022-04-18T07:26:00Z</dc:date>
    </item>
    <item>
      <title>Re: A question about ECUbus</title>
      <link>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1446006#M15028</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;I think you used the bootloader version is v1.0. This is a known issue for the v1.0. You can get the new version from: &lt;A href="https://community.nxp.com/t5/S32K-Knowledge-Base/Unified-bootloader-Demo/ta-p/1423099" target="_blank"&gt;https://community.nxp.com/t5/S32K-Knowledge-Base/Unified-bootloader-Demo/ta-p/1423099&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Best Regards!&lt;/P&gt;</description>
      <pubDate>Wed, 20 Apr 2022 01:53:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1446006#M15028</guid>
      <dc:creator>nxf10035</dc:creator>
      <dc:date>2022-04-20T01:53:22Z</dc:date>
    </item>
    <item>
      <title>Re: A question about ECUbus</title>
      <link>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1447721#M15074</link>
      <description>&lt;P&gt;Is there CANFD in version 2.0? Is there CAN? I compared the next version 2.0 with a lot of changes. For the problem I mentioned, only change BOOTLOADER without changing ECUBUS transmission. Can it be solved, or ECUBUS also changed the transmission byte length?&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2022 08:09:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1447721#M15074</guid>
      <dc:creator>ywjack</dc:creator>
      <dc:date>2022-04-22T08:09:28Z</dc:date>
    </item>
    <item>
      <title>Re: A question about ECUbus</title>
      <link>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1450391#M15176</link>
      <description>&lt;P&gt;Hello technical support: How does FLASH DRIVER map to RAM, that is how your flash_api.bin is made, is there any source code, can you provide it?&lt;BR /&gt;At present, I want to change the FLASH DRIVER mapping address to another (not starting from 0x1FFF8010) to another RAM address. I have tried several times and failed, so I would like to ask you how to make flash_api.bin. Can you provide the source code?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 04:09:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1450391#M15176</guid>
      <dc:creator>ywjack</dc:creator>
      <dc:date>2022-04-28T04:09:12Z</dc:date>
    </item>
    <item>
      <title>Re: A question about ECUbus</title>
      <link>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1450447#M15180</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; If you want to change the flash driver store address should:&lt;/P&gt;&lt;P&gt;1. Change the address of flash driver in &lt;STRONG&gt;ECUBUS&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;2. Modify flash driver address in &lt;STRONG&gt;flash_hal_Cfg.c(gs_astFlashDriverBlock) in bootloader &lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;3. Flash driver section should be change in&lt;STRONG&gt; link file&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Please note: the address of flash driver should be align with 4 bytes.&lt;/P&gt;&lt;P&gt;Best Regards!&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 06:18:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1450447#M15180</guid>
      <dc:creator>nxf10035</dc:creator>
      <dc:date>2022-04-28T06:18:19Z</dc:date>
    </item>
    <item>
      <title>Re: A question about ECUbus</title>
      <link>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1450452#M15182</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp; The ECU BUS resolved the issue. So, the bootloader and GUI should be match: &lt;/P&gt;
&lt;P&gt;1. Bootloader V1.0 with NXPOpenBus&lt;/P&gt;
&lt;P&gt;2. Bootloader V2.0 with ECU BUS&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards!&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 06:24:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/A-question-about-ECUbus/m-p/1450452#M15182</guid>
      <dc:creator>nxf10035</dc:creator>
      <dc:date>2022-04-28T06:24:55Z</dc:date>
    </item>
  </channel>
</rss>

