<?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 iMX8QM Android Automotive OS SCFW Firmware PMIC Issue in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/iMX8QM-Android-Automotive-OS-SCFW-Firmware-PMIC-Issue/m-p/1538353#M196423</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am developing on a custom board with iMX8QM on it.&lt;/P&gt;&lt;P&gt;I compiled Android Automotive OS 12.0.0_2.1.0, referring to the "Android_Auto_User's_Guide.pdf" document.&lt;/P&gt;&lt;P&gt;I wrote the compiled image to eMMC with the "uuu_imx_android_flash.bat" script on the NXP iMX8QM EVK board with the "uuu_imx_android_flash.sh -f imx8qm -e -d md" command and observed that the compiled image was running on the EVK board.&lt;/P&gt;&lt;P&gt;I tried to run the same image on my custom board but without success.&lt;/P&gt;&lt;P&gt;I compared the schematics of my EVK board and my custom board and observed that the PMICs are different.&lt;/P&gt;&lt;P&gt;While PF8100 is used as PMIC in EVK board, PF8200 is used in my custom board.&lt;/P&gt;&lt;P&gt;For this reason, it has been determined that the problem is in the SCFW firmware.&lt;/P&gt;&lt;P&gt;The steps we have taken to resolve this problem are listed below. NXP's "Android_Auto_User's_Guide.pdf" document is referenced while performing the steps.&lt;/P&gt;&lt;P&gt;1) The recommended “imx-scfw-porting-kit-1.13.0” porting kit for Android Automotive OS 12.0.0_2.1.0 has been downloaded.&lt;BR /&gt;2) Content of file “${MY_ANDROID}/vendor/nxp/fsl-proprietary/u-boot-firmware/imx8q/board-imx8qm.c” in Android Automotive OS 12.0.0_2.1.0 BSP is in scfw-porting-kit Copied to file “scfw_export_mx8qm_b0/platform/board/mx8qm_mek/board.c”.&lt;BR /&gt;3) The macros “#define PMIC_CRC” and “#define PMIC_SECURE_WRITE”, which are in the file “scfw_export_mx8qm_b0/platform/board/mx8qm_mek/board.h” in the scfw-porting-kit and are in the comment in status, have been commented out.&lt;BR /&gt;4) With this change, the file “scfw-tcm.bin” was generated with the command “make qm B=mek R=B0”.&lt;BR /&gt;5) Then the generated “scfw-tcm.bin” file was copied to “${MY_ANDROID}/vendor/nxp/fslproprietary/uboot-firmware/imx8q_car/mx8qx-scfw-tcm.bin” file in BSP.&lt;BR /&gt;6) Finally, the bootloader was compiled in the BSP with the command "./imx-make.sh bootloader -j4".&lt;/P&gt;&lt;P&gt;All the files that came out as a result of the compilation were tried to be uploaded to the custom board with the "uuu_imx_android_flash.bat" script, but it was unsuccessful.&lt;/P&gt;&lt;P&gt;The step left during the installation is shown in the image below.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;C:\Users\efecan.cebel\Desktop\android_auto_build&amp;gt;uuu_imx_android_flash.bat -f imx8qm -e -d md&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;This script is validated with uuu 1.4.182 version, it is recommended to align with this version.&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;dual bootloader is supported&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;dtbo is supported&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;dual slot is supported&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash spl-imx8qm.bin to the partition of bootloader0&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash partition-table.img to the partition of gpt&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash bootloader-imx8qm.img to the partition of bootloader_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash dtbo-imx8qm-md.img to the partition of dtbo_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash boot.img to the partition of boot_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash system.img to the partition of system_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash system_ext.img to the partition of system_ext_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash vendor.img to the partition of vendor_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash product.img to the partition of product_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash vbmeta-imx8qm-md.img to the partition of vbmeta_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash bootloader-imx8qm.img to the partition of bootloader_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash dtbo-imx8qm-md.img to the partition of dtbo_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash boot.img to the partition of boot_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash system.img to the partition of system_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash system_ext.img to the partition of system_ext_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash vendor.img to the partition of vendor_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash product.img to the partition of product_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash vbmeta-imx8qm-md.img to the partition of vbmeta_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;uuu script generated, start to invoke uuu with the generated uuu script&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.182-0-ga561ed7&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Success 0 Failure 0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1:2 1/ 1 [=================100%=================] SDPS: boot -f u-boot-imx8qm-mek-uuu.imx.link&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The download does not continue after that and stops.&lt;/P&gt;&lt;P&gt;The same problem was encountered in my image that I created with Yocto.&lt;/P&gt;&lt;P&gt;The image running on EVK board does not run on my custom board. This problem was solved by generating a new “scfw-tcm.bin” file by commenting out the “#define PMIC_CRC” and “#define PMIC_SECURE_WRITE” macros, which are also in the comment in state, and it worked on the image custom board as well.&lt;/P&gt;&lt;P&gt;Could you please help with the problem in Android Automotive OS?&lt;/P&gt;&lt;P&gt;I look forward to your support in this issues.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Efecan&lt;/P&gt;</description>
    <pubDate>Mon, 17 Oct 2022 07:07:29 GMT</pubDate>
    <dc:creator>cbl</dc:creator>
    <dc:date>2022-10-17T07:07:29Z</dc:date>
    <item>
      <title>iMX8QM Android Automotive OS SCFW Firmware PMIC Issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX8QM-Android-Automotive-OS-SCFW-Firmware-PMIC-Issue/m-p/1538353#M196423</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am developing on a custom board with iMX8QM on it.&lt;/P&gt;&lt;P&gt;I compiled Android Automotive OS 12.0.0_2.1.0, referring to the "Android_Auto_User's_Guide.pdf" document.&lt;/P&gt;&lt;P&gt;I wrote the compiled image to eMMC with the "uuu_imx_android_flash.bat" script on the NXP iMX8QM EVK board with the "uuu_imx_android_flash.sh -f imx8qm -e -d md" command and observed that the compiled image was running on the EVK board.&lt;/P&gt;&lt;P&gt;I tried to run the same image on my custom board but without success.&lt;/P&gt;&lt;P&gt;I compared the schematics of my EVK board and my custom board and observed that the PMICs are different.&lt;/P&gt;&lt;P&gt;While PF8100 is used as PMIC in EVK board, PF8200 is used in my custom board.&lt;/P&gt;&lt;P&gt;For this reason, it has been determined that the problem is in the SCFW firmware.&lt;/P&gt;&lt;P&gt;The steps we have taken to resolve this problem are listed below. NXP's "Android_Auto_User's_Guide.pdf" document is referenced while performing the steps.&lt;/P&gt;&lt;P&gt;1) The recommended “imx-scfw-porting-kit-1.13.0” porting kit for Android Automotive OS 12.0.0_2.1.0 has been downloaded.&lt;BR /&gt;2) Content of file “${MY_ANDROID}/vendor/nxp/fsl-proprietary/u-boot-firmware/imx8q/board-imx8qm.c” in Android Automotive OS 12.0.0_2.1.0 BSP is in scfw-porting-kit Copied to file “scfw_export_mx8qm_b0/platform/board/mx8qm_mek/board.c”.&lt;BR /&gt;3) The macros “#define PMIC_CRC” and “#define PMIC_SECURE_WRITE”, which are in the file “scfw_export_mx8qm_b0/platform/board/mx8qm_mek/board.h” in the scfw-porting-kit and are in the comment in status, have been commented out.&lt;BR /&gt;4) With this change, the file “scfw-tcm.bin” was generated with the command “make qm B=mek R=B0”.&lt;BR /&gt;5) Then the generated “scfw-tcm.bin” file was copied to “${MY_ANDROID}/vendor/nxp/fslproprietary/uboot-firmware/imx8q_car/mx8qx-scfw-tcm.bin” file in BSP.&lt;BR /&gt;6) Finally, the bootloader was compiled in the BSP with the command "./imx-make.sh bootloader -j4".&lt;/P&gt;&lt;P&gt;All the files that came out as a result of the compilation were tried to be uploaded to the custom board with the "uuu_imx_android_flash.bat" script, but it was unsuccessful.&lt;/P&gt;&lt;P&gt;The step left during the installation is shown in the image below.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;C:\Users\efecan.cebel\Desktop\android_auto_build&amp;gt;uuu_imx_android_flash.bat -f imx8qm -e -d md&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;This script is validated with uuu 1.4.182 version, it is recommended to align with this version.&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;dual bootloader is supported&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;dtbo is supported&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;dual slot is supported&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash spl-imx8qm.bin to the partition of bootloader0&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash partition-table.img to the partition of gpt&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash bootloader-imx8qm.img to the partition of bootloader_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash dtbo-imx8qm-md.img to the partition of dtbo_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash boot.img to the partition of boot_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash system.img to the partition of system_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash system_ext.img to the partition of system_ext_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash vendor.img to the partition of vendor_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash product.img to the partition of product_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash vbmeta-imx8qm-md.img to the partition of vbmeta_a&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash bootloader-imx8qm.img to the partition of bootloader_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash dtbo-imx8qm-md.img to the partition of dtbo_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash boot.img to the partition of boot_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash system.img to the partition of system_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash system_ext.img to the partition of system_ext_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash vendor.img to the partition of vendor_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash product.img to the partition of product_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;generate lines to flash vbmeta-imx8qm-md.img to the partition of vbmeta_b&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;uuu script generated, start to invoke uuu with the generated uuu script&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.4.182-0-ga561ed7&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Success 0 Failure 0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1:2 1/ 1 [=================100%=================] SDPS: boot -f u-boot-imx8qm-mek-uuu.imx.link&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;The download does not continue after that and stops.&lt;/P&gt;&lt;P&gt;The same problem was encountered in my image that I created with Yocto.&lt;/P&gt;&lt;P&gt;The image running on EVK board does not run on my custom board. This problem was solved by generating a new “scfw-tcm.bin” file by commenting out the “#define PMIC_CRC” and “#define PMIC_SECURE_WRITE” macros, which are also in the comment in state, and it worked on the image custom board as well.&lt;/P&gt;&lt;P&gt;Could you please help with the problem in Android Automotive OS?&lt;/P&gt;&lt;P&gt;I look forward to your support in this issues.&lt;/P&gt;&lt;P&gt;Best regards,&lt;BR /&gt;Efecan&lt;/P&gt;</description>
      <pubDate>Mon, 17 Oct 2022 07:07:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX8QM-Android-Automotive-OS-SCFW-Firmware-PMIC-Issue/m-p/1538353#M196423</guid>
      <dc:creator>cbl</dc:creator>
      <dc:date>2022-10-17T07:07:29Z</dc:date>
    </item>
    <item>
      <title>Re: iMX8QM Android Automotive OS SCFW Firmware PMIC Issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/iMX8QM-Android-Automotive-OS-SCFW-Firmware-PMIC-Issue/m-p/1546109#M197011</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/186248"&gt;@cbl&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Please cross-check if there is any USB compatibility or stuck issue.&lt;BR /&gt;Are there any logs on debug console after downloading uboot in emmc mode? If yes, kindly share the same.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;BR /&gt;Dhruvit.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2022 06:28:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/iMX8QM-Android-Automotive-OS-SCFW-Firmware-PMIC-Issue/m-p/1546109#M197011</guid>
      <dc:creator>Dhruvit</dc:creator>
      <dc:date>2022-10-31T06:28:52Z</dc:date>
    </item>
  </channel>
</rss>

