已解决! 转到解答。
If the firmware image size is less than half of the SPI Flash size it is possible to use available MT25QL512A.
If not - it will be needed to add new device referring the Code Warrior application note:
\Freescale\CW_PA_v10.5.1\PA\PA_Tools\FlashToolKit\Documentation\AppNote-FlashProgrammer-PowerArchitecture.pdf
If the firmware image size is less than half of the SPI Flash size it is possible to use available MT25QL512A.
If not - it will be needed to add new device referring the Code Warrior application note:
\Freescale\CW_PA_v10.5.1\PA\PA_Tools\FlashToolKit\Documentation\AppNote-FlashProgrammer-PowerArchitecture.pdf
<?xml version="1.0" encoding="UTF-8"?>
<device-file>
<device>
<version>0.1</version>
<content>
<name>MT25QL01GB</name>
<device_type>spi</device_type>
<manufacturerid>0x20</manufacturerid>
<chiperase>true</chiperase>
<sectors>
<sectorcount>2048</sectorcount>
<sectorsize>0x10000</sectorsize>
</sectors>
<ontargetverify>true</ontargetverify>
<organization>
<name>128Mx8x1</name>
<id>0xBA21</id>
<algorithm>MT25QL512A_SPI.elf</algorithm>
<utility>N25Q512A_SPI_Utility.elf</utility>
</organization>
<protecttype>spi</protecttype>
<verifyafterprogram>true</verifyafterprogram>
<autodetectprocessorinfo>true</autodetectprocessorinfo>
</content>
</device>
</device-file>
*The differences from the MT25QL512A.xml are the four places shown in bold.
Hi
I had a successful SPI flash boot.
The file of "MT25QL01GB.xml" I used are shown below.
I fixed the algorithm file name.
<?xml version="1.0" encoding="UTF-8"?>
<device-file>
<device>
<version>0.1</version>
<content>
<name>MT25QL01GB</name>
<device_type>spi</device_type>
<manufacturerid>0x20</manufacturerid>
<chiperase>true</chiperase>
<sectors>
<sectorcount>2048</sectorcount>
<sectorsize>0x10000</sectorsize>
</sectors>
<ontargetverify>true</ontargetverify>
<organization>
<name>128Mx8x1</name>
<id>0xBA21</id>
<algorithm>MT25QL512AB_SPI.elf</algorithm>
<utility>N25Q512A_SPI_Utility.elf</utility>
</organization>
<protecttype>spi</protecttype>
<verifyafterprogram>true</verifyafterprogram>
<autodetectprocessorinfo>true</autodetectprocessorinfo>
</content>
</device>
</device-file>