s32k micro issue

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

s32k micro issue

1,055件の閲覧回数
vijayaguru1
Contributor I

we faced issue in s32k board flashing. we initiate the re flashing the s32k micro .it will hold while re flashing after 60% of flashing process completion period. how to resolve this issue.

vijayaguru1_0-1714710161040.png

vijayaguru1_1-1714710245469.png

 

0 件の賞賛
返信
3 返答(返信)

1,022件の閲覧回数
Robin_Shen
NXP TechSupport
NXP TechSupport

Hi

This issue is discussed in HOWTO: Create S32DS Project from Example 'Hello World' for S32K144 (w/o SDK). It seems that this issue is related to Admin rights.


Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 件の賞賛
返信

1,008件の閲覧回数
vijayaguru1
Contributor I

hi sir,

how it is possible to admin rights, here, micro does not allow to flash. i think, micro is lock, can you share your input for how to enable and how to unlock the micro.

0 件の賞賛
返信

997件の閲覧回数
Robin_Shen
NXP TechSupport
NXP TechSupport

If S32K is secured, when using the onboard PEMicro OpenSDA debugger, S32DS will pop up this reminder: Device is secure. Erase to unsecure?

Device is secure Erase to unsecure.png

Did you secure the S32K1 before? If the mass-erase was enabled, just re-program it as usual. Refer to AN12130 Production Flash Programming Best Practices for S32K1xx MCUs.pdf

Does the project that was loaded to the MCU before the error occured use CSEc?
Or has the MCU been partitioned for CSEc, even by trying an example project that utilizes the security engine?

Have you tried switching another workspace? Finally, I suggest you try giving S32DS admin rights.

0 件の賞賛
返信