LX2080

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

LX2080

841 Views
YY2410
Contributor III

你好,我处理器为LX2080,禁用安全启动模式,调试时调整了核电VDD和IO电OVDD,然后CPU扇区写保护了,无法正常加载,二次烧写时如附件所示,必须要先解除保护unprotect,然后可以正常烧写,请问下这个为什么会出现保护情况?谢谢!

Hello, my processor is LX2080. I disabled the secure boot mode. During debugging, I adjusted the VDD of the CPU core and the OVDD of the IO. Then the CPU sector was made write-protected. As a result, it couldn't be loaded normally. When re-writing, as shown in the attachment, it was necessary to first remove the protection (unprotect), and then it could be written normally. Could you please explain why this protection situation occurred? Thank you!

0 Kudos
Reply
3 Replies

821 Views
pemaj88983
Contributor I

Hello!

Adjusting VDD and OVDD during debugging may have triggered a hardware self-protection mechanism, especially with secure boot disabled. This can cause flash sectors to become write-protected due to voltage irregularities or bootloader behavior. To resolve it, you need to manually unprotect before reprogramming. Check your initialization scripts and ensure voltage settings stay within recommended ranges to avoid triggering protection again. 

0 Kudos
Reply

799 Views
YY2410
Contributor III
请问下如何手动解保护,我之前通过codewarrior可以,现在通过codewarrior的unprotect解保不了。
Could you please tell me how to manually remove the protection? Previously, I could do it using Codewarrior, but now I can't use Codewarrior's "unprotect" function to remove the protection.
0 Kudos
Reply

626 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please try to use the flash unprotected function provided in CodeWarrior IDE.

If it fails, please check whether the flash algorithm is suitable for your custom board.

Did you use the same QSPI flash MT35XU512ABA as LX2160ARDB on your custom board?

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2176342%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3ELX2080%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2176342%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%20my%20processor%20is%20LX2080%2C%20disable%20the%20safe%20boot%20mode%2C%20debugging%20adjusted%20the%20core%20power%20VDD%20and%20IO%20power%20OVDD%2C%20then%20the%20CPU%20sector%20write%20protection%2C%20can%20not%20be%20loaded%20normally%2C%20the%20second%20burn%20as%20shown%20in%20the%20attachment%2C%20you%20must%20first%20unprotect%20unprotect%2C%20and%20then%20can%20be%20burned%20normally%2C%20may%20I%20ask%20why%20this%20will%20be%20the%20case%20of%20protection%3F%20Thank%20you!%3C%2FP%3E%3CP%3EHello%2C%20my%20processor%20is%20LX2080.%20I%20disabled%20the%20secure%20boot%20mode.%20During%20debugging%2C%20I%20adjusted%20the%20VDD%20of%20the%20CPU%20core%20and%20the%20OVDD%20of%20the%20IO.%20Then%20the%20CPU%20sector%20was%20made%20write-protected.%20As%20a%20result%2C%20it%20couldn't%20be%20loaded%20normally.%20When%20re-writing%2C%20as%20shown%20in%20the%20attachment%2C%20it%20was%20necessary%20to%20first%20remove%20the%20protection%20(unprotect)%2C%20and%20then%20it%20could%20be%20written%20normally.%20Could%20you%20please%20explain%20why%20this%20protection%20situation%20occurred%3F%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2184469%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LX2080%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2184469%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EPlease%20try%20to%20use%20the%20flash%20unprotected%20function%20provided%20in%20CodeWarrior%20IDE.%3C%2FP%3E%0A%3CP%3EIf%20it%20fails%2C%20please%20check%20whether%20the%20flash%20algorithm%20is%20suitable%20for%20your%20custom%20board.%3C%2FP%3E%0A%3CP%3EDid%20you%20use%20the%20same%20QSPI%20flash%26nbsp%3BMT35XU512ABA%20as%20LX2160ARDB%20on%20your%20custom%20board%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2177030%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LX2080%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2177030%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3ECould%20you%20please%20tell%20me%20how%20to%20manually%20remove%20the%20protection%2C%20I%20used%20to%20be%20able%20to%20do%20it%20through%20codewarrior%2C%20but%20now%20I%20can't%20do%20it%20through%20codewarrior's%20unprotect.%20%3CBR%20%2F%3ECould%20you%20please%20tell%20me%20how%20to%20manually%20remove%20the%20protection%3F%20Previously%2C%20I%20could%20do%20it%20using%20Codewarrior%2C%20but%20now%20I%20can't%20use%20Codewarrior's%20%22unprotect%20%22%20function%20to%20remove%20the%20protection.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2176530%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20LX2080%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2176530%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHello!%3C%2FP%3E%3CP%3EAdjusting%20VDD%20and%20OVDD%20during%20debugging%20may%20have%20triggered%20a%20hardware%20self-protection%20mechanism%2C%20especially%20with%20secure%20boot%20disabled.%20This%20can%20cause%20flash%20sectors%20to%20become%20write-protected%20due%20to%20voltage%20irregularities%20or%20bootloader%20behavior.%20To%20resolve%20it%2C%20you%20need%20to%20manually%20unprotect%20before%20reprogramming.%20Check%20your%20initialization%20scripts%20and%20ensure%20voltage%20settings%20stay%20within%20recommended%20ranges%20to%20avoid%20triggering%20protection%20again.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E