Need Support for i.MX93 Tamper Functionality Configuration and Access in Linux

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

Need Support for i.MX93 Tamper Functionality Configuration and Access in Linux

342 Views
IXM
Contributor I

Hello NXP Team,

I am working on a custom board based on the NXP i.MX93 processor and am currently trying to enable and test the tamper detection functionality under Linux.

System Details

  • Processor: NXP i.MX93

  • BSP Version: LF 6.6.52_2.2.0

  • Operating System: Linux (Yocto-based build)

    What I Have Tried

    1. Reviewed the BBNSM (Battery-Backed Non-Secure Monitor) block and identified relevant registers:

      • Base Address: 0x44440000

      • Tamper Status / Enable / Clear Offsets: 0x30 / 0x34 / 0x38

    2. Developed a small kernel module to map this region using ioremap() and read the registers.

      • However, the system crashes or powers off immediately after accessing these addresses.

      • Error observed:
        => Internal error: synchronous external abort: 000000009600001

      • Attempted reading with devmem2, but it results in a Bus error.

        These symptoms suggest that the BBNSM or tamper registers are secure-only, and thus not accessible from the non-secure (Linux) domain.


    Could you please provide guidance or documentation on:

    • How to enable and access the tamper detection functionality from Linux on i.MX93.

    • Whether tamper registers are accessible only in the secure domain.

    • Any device tree examples, reference drivers, or firmware configuration steps.required to expose tamper events to Linux.

    Thank you for your support and guidance.

    Thanks.

     

0 Kudos
Reply
1 Reply

227 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

We do not have/nor provide tamper documentation/example publicly, I would recommend to reach out your NXP sales office for more information related to this.

Best regards/Saludos,
Aldo.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2197556%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ENeed%20Support%20for%20i.MX93%20Tamper%20Functionality%20Configuration%20and%20Access%20in%20Linux%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2197556%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%20NXP%20Team%2C%3C%2FP%3E%3CP%3EI%20am%20working%20on%20a%20custom%20board%20based%20on%20the%20%3CSTRONG%3ENXP%20i.MX93%3C%2FSTRONG%3E%20processor%20and%20am%20currently%20trying%20to%20enable%20and%20test%20the%20%3CSTRONG%3Etamper%20detection%20functionality%3C%2FSTRONG%3E%20under%20Linux.%3C%2FP%3E%3CH3%20id%3D%22toc-hId-1977578426%22%20id%3D%22toc-hId-1999799693%22%3E%3CSTRONG%3ESystem%20Details%3C%2FSTRONG%3E%3C%2FH3%3E%3CUL%3E%3CLI%3E%3CP%3E%3CSTRONG%3EProcessor%3A%3C%2FSTRONG%3E%20NXP%20i.MX93%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CSTRONG%3EBSP%20Version%3A%3C%2FSTRONG%3E%20LF%206.6.52_2.2.0%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CSTRONG%3EOperating%20System%3A%3C%2FSTRONG%3E%20Linux%20(Yocto-based%20build)%3C%2FP%3E%3CH3%20id%3D%22toc-hId-170123963%22%20id%3D%22toc-hId-192345230%22%3E%3CSTRONG%3EWhat%20I%20Have%20Tried%3C%2FSTRONG%3E%3C%2FH3%3E%3COL%3E%3CLI%3E%3CP%3EReviewed%20the%20%3CSTRONG%3EBBNSM%20(Battery-Backed%20Non-Secure%20Monitor)%3C%2FSTRONG%3E%20block%20and%20identified%20relevant%20registers%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3E%3CSTRONG%3EBase%20Address%3A%3C%2FSTRONG%3E%200x44440000%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3E%3CSTRONG%3ETamper%20Status%20%2F%20Enable%20%2F%20Clear%20Offsets%3A%3C%2FSTRONG%3E%200x30%20%2F%200x34%20%2F%200x38%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3E%3CP%3EDeveloped%20a%20small%20kernel%20module%20to%20map%20this%20region%20using%20ioremap()%20and%20read%20the%20registers.%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3EHowever%2C%20the%20system%20%3CSTRONG%3Ecrashes%20or%20powers%20off%3C%2FSTRONG%3E%20immediately%20after%20accessing%20these%20addresses.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EError%20observed%3A%3CBR%20%2F%3E%3D%26gt%3B%20Internal%20error%3A%20synchronous%20external%20abort%3A%20000000009600001%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EAttempted%20reading%20with%20devmem2%2C%20but%20it%20results%20in%20a%20%3CSTRONG%3EBus%20error.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EThese%20symptoms%20suggest%20that%20the%20%3CSTRONG%3EBBNSM%20or%20tamper%20registers%20are%20secure-only%3C%2FSTRONG%3E%2C%20and%20thus%20not%20accessible%20from%20the%20non-secure%20(Linux)%20domain.%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%3CBR%20%2F%3ECould%20you%20please%20provide%20guidance%20or%20documentation%20on%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3EHow%20to%20%3CSTRONG%3Eenable%20and%20access%20the%20tamper%20detection%20functionality%3C%2FSTRONG%3E%20from%20Linux%20on%20i.MX93.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EWhether%20%3CSTRONG%3Etamper%20registers%3C%2FSTRONG%3E%20are%20accessible%20only%20in%20the%20%3CSTRONG%3Esecure%20domain%3C%2FSTRONG%3E.%3C%2FP%3E%3C%2FLI%3E%3CLI%3E%3CP%3EAny%20%3CSTRONG%3Edevice%20tree%20examples%3C%2FSTRONG%3E%2C%20reference%20drivers%2C%20or%20%3CSTRONG%3Efirmware%20configuration%3C%2FSTRONG%3E%20steps.required%20to%20expose%20tamper%20events%20to%20Linux.%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3EThank%20you%20for%20your%20support%20and%20guidance.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks.%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2198598%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Need%20Support%20for%20i.MX93%20Tamper%20Functionality%20Configuration%20and%20Access%20in%20Linux%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2198598%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20do%20not%20have%2Fnor%20provide%20tamper%20documentation%2Fexample%20publicly%2C%20I%20would%20recommend%20to%20reach%20out%20your%20NXP%20sales%20office%20for%20more%20information%20related%20to%20this.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20regards%2FSaludos%2C%3CBR%20%2F%3EAldo.%3C%2FP%3E%3C%2FLINGO-BODY%3E