MPC5xxxのトピックRe: MPC5741 INTC_0.PSR register cannot be written

MPC5741 INTC_0.PSR register cannot be written

lihui1 — Mon, 09 Dec 2024 14:36:38 GMT

Hi：

We have encountered a problem that INTC_0.PSR register cannot be written due too only different link order，although the same project.

We checked the assembly instruction when the fault was repeated, and found that there was no problem with the assembly instruction, and there was no problem with the kernel register, but some INTC_0.PSR registers still could not be written in. Here are the results of our tests.

And we want to know if there are any special circumstances in which the INTC_0.PSR register cannot be written.

picture(1) shows before writing the INTC_0.PSR register, check that the assembly instruction and the kernel register are all right

picture(2) shows after writing the INTC_0.PSR register, check that the INTC_0.PSR register is not written successfully

Re: MPC5741 INTC_0.PSR register cannot be written

davidtosenovjan — Mon, 09 Dec 2024 16:34:13 GMT

Could you specify used compiler? Possibly other information we should know..

Thanks

Re: MPC5741 INTC_0.PSR register cannot be written

lihui1 — Tue, 10 Dec 2024 01:30:33 GMT

we use S32DS for S32 Design Studio for Power Architecture Version 2017

Re: MPC5741 INTC_0.PSR register cannot be written

davidtosenovjan — Tue, 10 Dec 2024 12:51:40 GMT

That's interesting. Haven't you seen any warning message after compiling the code?

Re: MPC5741 INTC_0.PSR register cannot be written

lihui1 — Wed, 11 Dec 2024 01:48:30 GMT

Yes，exactly no warning

Re: MPC5741 INTC_0.PSR register cannot be written

davidtosenovjan — Wed, 11 Dec 2024 13:51:08 GMT

Could you use newest version of the S32DS? Latest version is 2.1, issued in 2019, latest update from 2020:

https://www.nxp.com/design/design-center/software/automotive-software-and-tools/s32-design-studio-ide/s32-design-studio-for-power-architecture:S32DS-PA

Re: MPC5741 INTC_0.PSR register cannot be written

lihui1 — Thu, 12 Dec 2024 01:38:06 GMT

Actually we had used latest version to compare but the same result as before.

We think it might be caused by some code we add to our previous version. we'll do more test and confirm.