MPC5744P

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

MPC5744P

128 Views
GENG
Contributor I

Here's the English translation of your question: > Why is it that when I modify certain register values of the MPC5744P through S32DS, only some of the embsys registers can be modified? When modifying certain RW register values, an error is reported: "Error: Error in ONCE status register during instruction execution."

为什么我通过S32DS去修改MOC5744P的某些寄存器的值也是只有部分的embsys registers寄存器能被修改。修改某些RW寄存器值时会报出Error : Error in ONCE status register during instruction execution?
将上述一段话翻译为英文

Tags (1)
0 Kudos
Reply
1 Reply

57 Views
petervlna
NXP TechSupport
NXP TechSupport

Hello,

Without knowing any details I will answer just generally:

The error is NOT a register access error - It is a debug link failure triggered by your write
And that happens because those specific registers:

  • cause reset
  • are not accessible in current mode
  • require unlock / clock / sequence
  • or cannot be safely written via debugger

Best regards,

Peter

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2379951%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EMPC5744P%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2379951%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHere's%20the%20English%20translation%20of%20your%20question%3A%20%26gt%3B%20Why%20is%20it%20that%20when%20I%20modify%20certain%20register%20values%20of%20the%20MPC5744P%20through%20S32DS%2C%20only%20some%20of%20the%20embsys%20registers%20can%20be%20modified%3F%20When%20modifying%20certain%20RW%20register%20values%2C%20an%20error%20is%20reported%3A%20%22Error%3A%20Error%20in%20ONCE%20status%20register%20during%20instruction%20execution.%22%3C%2FP%3E%3CP%3E%E4%B8%BA%E4%BB%80%E4%B9%88%E6%88%91%E9%80%9A%E8%BF%87S32DS%E5%8E%BB%E4%BF%AE%E6%94%B9MOC5744P%E7%9A%84%E6%9F%90%E4%BA%9B%E5%AF%84%E5%AD%98%E5%99%A8%E7%9A%84%E5%80%BC%E4%B9%9F%E6%98%AF%E5%8F%AA%E6%9C%89%E9%83%A8%E5%88%86%E7%9A%84embsys%20registers%E5%AF%84%E5%AD%98%E5%99%A8%E8%83%BD%E8%A2%AB%E4%BF%AE%E6%94%B9%E3%80%82%E4%BF%AE%E6%94%B9%E6%9F%90%E4%BA%9BRW%E5%AF%84%E5%AD%98%E5%99%A8%E5%80%BC%E6%97%B6%E4%BC%9A%E6%8A%A5%E5%87%BAError%20%3A%20Error%20in%20ONCE%20status%20register%20during%20instruction%20execution%EF%BC%9F%3CBR%20%2F%3E%E5%B0%86%E4%B8%8A%E8%BF%B0%E4%B8%80%E6%AE%B5%E8%AF%9D%E7%BF%BB%E8%AF%91%E4%B8%BA%E8%8B%B1%E6%96%87%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2380581%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20MPC5744P%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2380581%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3EWithout%20knowing%20any%20details%20I%20will%20answer%20just%20generally%3A%3C%2FP%3E%0A%3CP%3EThe%20error%20is%20NOT%20a%20register%20access%20error%20-%20It%20is%20a%20debug%20link%20failure%20triggered%20by%20your%20write%3CBR%20%2F%3EAnd%20that%20happens%20because%20those%20specific%20registers%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3Ecause%20reset%3C%2FLI%3E%0A%3CLI%3Eare%20not%20accessible%20in%20current%20mode%3C%2FLI%3E%0A%3CLI%3Erequire%20unlock%20%2F%20clock%20%2F%20sequence%3C%2FLI%3E%0A%3CLI%3Eor%20cannot%20be%20safely%20written%20via%20debugger%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EBest%20regards%2C%3C%2FP%3E%0A%3CP%3EPeter%3C%2FP%3E%3C%2FLINGO-BODY%3E