InitTarget() start
- Protection bytes in flash at addr. 0x400 - 0x40F indicate that readout protection is set.
For debugger connection the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash.
- Executing default behavior previously saved in the registry.
- Device will be unsecured now.
- Timeout while halting CPU.
- InitTarget() end
- Found SW-DP with ID 0x2BA01477
- DPIDR: 0x2BA01477
- CoreSight SoC-400 or earlier
In the process of using S32K144 chip to do information security development, the chip is always protected.When the phenomenon as shown above occurs, whether the protection can be removed.I have tried using jlink's unlock command to return ok, but I am unable to release the protection.
Have you solved the same problem, friend
没有,至今没有解决,那块板子废掉了
Usually we will modify the configuration of setting Flash Security in the startup file(etc:Startup_S32K1xx.S), as shown in the figure below, please confirm whether to modify this place in your project.
for your better undersantding the feature of flash security ,I recommand you to read this article which written in chinese
If the CSEc module is enabled and the chip is locked, can it still be unlocked.
When CSEc is enabled, some considerations must be taken prior to launch mass erase command.
If no CSEc keys have been configured or the part is not partitioned, then the mass erase operation will be allowed to run.
If CSEc key size field in the program partition command is set to zero keys (0x00), then you can mass erase at any time and it should always run as long as mass erase is enabled in the flash configuration field.
If any CSEc keys have been configured (so the part has been already partitioned)
user must finish the complete flow below otherwise the mass eras command will not work:
简单来说,就是如果你只是使能了CSEc模块,但是并没有配置CSEc的key,那么你依然可以通过mass erase 来恢复(前提mass erase已经被使能),相反,如果已经配置了key,那么必须要使用CSEc的命令来擦除CSEc的区域,然后再执行mass erase,如果你直接执行mass erase,那么芯片也会被锁。
问题是芯片被锁了,Debug访问不了,怎样进行您提到的操作