Clarification on erratum

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

Clarification on erratum

327 Views
rhaas
Contributor IV

I have been reviewing A-008822 in the LS1028A errata (LS1028ACE, Rev2, 2/2023). In A-008822, the workaround asks for a write to the PCIe configurations space offset 8D0h to occur.

I looked in the LS1028A TRM and I was not able to find this register listed.

Is it possible to get the definition of this register. I would like to understand the workaround; in case someone asks.

0 Kudos
Reply
2 Replies

264 Views
Oswalag
NXP TechSupport
NXP TechSupport

Hello,

There isn't a public description of the register available.

Wording of the erratum A-008822 describes the issue in detail.
As stated, that workaround changes AXI slave response for all error scenarios on non-posted requests from default OKAY to ERROR.

Additional details cannot be provided to the customer because the PCIe IP internals are confidential.

Regards.

0 Kudos
Reply

229 Views
rhaas
Contributor IV

Thank you for the information.

I was wondering if any 'write enable' bit needs to be set before writing this data, similar to MISC_CONTROL_1_OFF.

 

Thank you

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2183979%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EClarification%20on%20erratum%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2183979%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EI%20have%20been%20reviewing%20A-008822%20in%20the%20LS1028A%20errata%20(LS1028ACE%2C%20Rev2%2C%202%2F2023).%20In%20A-008822%2C%20the%20workaround%20asks%20for%20a%20write%20to%20the%20PCIe%20configurations%20space%20offset%208D0h%20to%20occur.%3C%2FP%3E%3CP%3EI%20looked%20in%20the%20LS1028A%20TRM%20and%20I%20was%20not%20able%20to%20find%20this%20register%20listed.%3C%2FP%3E%3CP%3EIs%20it%20possible%20to%20get%20the%20definition%20of%20this%20register.%20I%20would%20like%20to%20understand%20the%20workaround%3B%20in%20case%20someone%20asks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2187551%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Clarification%20on%20erratum%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2187551%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EThank%20you%20for%20the%20information.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20was%20wondering%20if%20any%20'write%20enable'%20bit%20needs%20to%20be%20set%20before%20writing%20this%20data%2C%20similar%20to%20MISC_CONTROL_1_OFF.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2186072%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Clarification%20on%20erratum%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2186072%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3EThere%20isn't%20a%20public%20description%20of%20the%20register%20available.%3C%2FP%3E%0A%3CP%3EWording%20of%20the%20erratum%20A-008822%20describes%20the%20issue%20in%20detail.%3CBR%20%2F%3EAs%20stated%2C%20that%20workaround%20changes%20AXI%20slave%20response%20for%20all%20error%20scenarios%20on%20non-posted%20requests%20from%20default%20OKAY%20to%20ERROR.%3C%2FP%3E%0A%3CP%3EAdditional%20details%20cannot%20be%20provided%20to%20the%20customer%20because%20the%20PCIe%20IP%20internals%20are%20confidential.%3C%2FP%3E%0A%3CP%3ERegards.%3C%2FP%3E%3C%2FLINGO-BODY%3E