https://community.nxp.com/t5/S32K/ARINC615A-Data-loading-with-JTAG-Access-password-protected/m-p/2413932#M61045 <P>CUST_DB_PSWD_A only restricts SWD/JTAG debug access. I am not familiar with the details of your ARINC 615A implementation, but if the software load is handled entirely by your application or bootloader, I would not expect the debug password itself to have any impact.<BR />Ultimately, this is application-specific and depends on how ARINC 615A has been implemented in your system. If the update mechanism does not use the debug interface, debug access restrictions should generally be independent of the software loading process. Any additional limitations would depend on your lifecycle configuration and application security design.</P> Wed, 16 Sep 2026 08:07:39 GMT davidtosenovjan 2026-09-16T08:07:39Z https://community.nxp.com/t5/S32K/ARINC615A-Data-loading-with-JTAG-Access-password-protected/m-p/2413795#M61032 <P><SPAN>When HSE firmware is not installed, SWD/JTAG access on the S32K3 can be restricted using the </SPAN><SPAN>CUST_DB_PSWD_A</SPAN><SPAN> field and device lifecycle configuration. Would enabling this password protection have any impact on performing an ARINC 615A software data load to the processor, assuming the update is handled by application or bootloader software rather than through the debug interface?</SPAN></P> Tue, 15 Sep 2026 19:06:56 GMT https://community.nxp.com/t5/S32K/ARINC615A-Data-loading-with-JTAG-Access-password-protected/m-p/2413795#M61032 CTCoder1 2026-09-15T19:06:56Z https://community.nxp.com/t5/S32K/ARINC615A-Data-loading-with-JTAG-Access-password-protected/m-p/2413932#M61045 <P>CUST_DB_PSWD_A only restricts SWD/JTAG debug access. I am not familiar with the details of your ARINC 615A implementation, but if the software load is handled entirely by your application or bootloader, I would not expect the debug password itself to have any impact.<BR />Ultimately, this is application-specific and depends on how ARINC 615A has been implemented in your system. If the update mechanism does not use the debug interface, debug access restrictions should generally be independent of the software loading process. Any additional limitations would depend on your lifecycle configuration and application security design.</P> Wed, 16 Sep 2026 08:07:39 GMT https://community.nxp.com/t5/S32K/ARINC615A-Data-loading-with-JTAG-Access-password-protected/m-p/2413932#M61045 davidtosenovjan 2026-09-16T08:07:39Z