SoloX :RDC register failed access , M4 can not boot

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SoloX :RDC register failed access , M4 can not boot

725 Views
subzero
Contributor I

Hi There,

 I have a custom board of and soloX and a SoloX sabre SD, both have the has a similar uboot build with only uart1 and the qspi enable. I have tried booting a simple MQX "helloworld" on my custom board and it failed. I am puzzle by this situation, because i have the same uboot setup for my SoloX sabre SD, and it work fined.

i found that the different between my custom board and the SoloX sabre SD is on the accessing the RDC register. RDC register access totally failed on my custom board.

this link below might shed some thing about the nature of my problem:

https://community.nxp.com/message/861365?commentID=861365#comment-861365 

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 anyonecould assist me, Thank you.

 

Best Regards,

Nidhal

Labels (1)
0 Kudos
4 Replies

589 Views
alkeke
Contributor I

Btw , Check M4 link file provided

It seems different from the one expected

M4 build result is different from the provided m4_bin.h content

Seem to be relative TCM-L adress  , may be aliased ...? 0x0000.0000 in LD file vs 0x1FFF8000 in the header file

0 Kudos

589 Views
subzero
Contributor I

Hi Igor,

Thank you for the reply, before i create service request, is there a fixed for it? is the fixed is by fusing the

PCIe_DISABLE only ? Thank you.

Nidhal

0 Kudos

589 Views
igorpadykov
NXP Employee
NXP Employee

Hi Nidhal

please check i.MX6SX Errata

http://cache.freescale.com/files/32bit/doc/errata/IMX6SXCE.pdf

Best regards
igor

0 Kudos

589 Views
igorpadykov
NXP Employee
NXP Employee

Hi Nidhal

youa are right, for RDC issues reason may be Errata #: ERR009572,

to check relevant fuse you can create service request to obtain additional

info about PCIe_DISABLE address.

How to create service request :
https://community.freescale.com/docs/DOC-329745

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos