Dear team,
I would like to ask about ERR009572 of i.MX6SX.
My customer found ERR009572 in your latest (Rev.1) errata document of i.MX6SX.
They are working on the similar issue on their proto-board.
The chip parts# which they are using is MCIMX6X3EVK10AB and the date-code is 1525.
As for the description on the errata document, they understand it as below.
If the date-code is bigger than 1524, PCIE_DISABLE fuse is not burned during your manufacturing process. And the issue does not occur.
Is it true?
Thanks,
Miyamoto
hello Igor,
i have a similar issue as above, assuming that the MCIMX6X3EVK10AB with the date-code 1525 is fixed similar as the 1533, why is it when i access the RDC register it failed on 1525 but not 1533?
I had build a simple helloworld using the MQX 4.1 for both the solox sabre sd and my custom board, both has only the uart1 and the qspi enable in uboot, but the custom board with 1525 failed at RDC access.
Custom Board(1525):
=> md 0x20FC204
020fc204: <<--Uboot hangs
SoloX sabre SD (1533):
Word 0x00000000: 00000000
=> md 0x20FC204
020fc204: 00000000 00000000 00000000 00000000 ................
020fc214: 00000000 00000000 00000000 00000000 ................
020fc224: 00000000 00000000 00000000 00000000 ................
020fc234: 00000000 00000000 00000000 00000000 ................
020fc244: 00000000 00000000 00000000 00000000 ................
020fc254: 00000000 00000000 00000000 00000000 ................
020fc264: 00000000 00000000 00000000 00000000 ................
020fc274: 00000000 00000000 00000000 00000000 ................
020fc284: 00000000 00000000 00000000 00000000 ................
020fc294: 00000000 00000000 00000000 00000000 ................
020fc2a4: 00000000 00000000 00000000 00000000 ................
020fc2b4: 00000000 00000000 00000000 00000000 ................
020fc2c4: 00000000 00000000 00000000 00000000 ................
020fc2d4: 00000000 00000000 00000000 00000000 ................
020fc2e4: 00000000 00000000 00000000 00000000 ................
020fc2f4: 00000000 00000000 00000000 00000000 ................
=> <<-- Uboot ok
Hope that you could assist me, Thank you.
Best Regards,
Andy
Hi Miyamoto
yes this is right understanding
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hello Igor,
Thanks for your support.
The customer is using MCIMX6X3EVK10AB with the date-code 1525, but the issue occurs on the customer's board.
Could you show me how to read the PCIE_DISABLE fuse value?
They want to check if the fuse are blown or not, but they could not find the location of PCIE_DISABLE on fuse-map in your reference manual.
Thanks,
Miyamoto
Hi Miyamoto
please create service request.
Best regards
igor