Failed to burn bin file, could not find core in coresight setup, erase error
Problem-solving method
Question
Flash is locked and cannot be erased when burning bin. What should I do?
Solution:
Use the j-flash tool to select the corresponding kernel model (I use cortex-m33) for erase chip operation. Note that when erasing, the erasing start address is set to 0x8030000. If the default address is 0x8000000, the PBL and SBL will be erased together, and the PBL and SBL need to be burned again.
Read More:
- RabbitMQ：address (cannot connect to host/port) [How to Solve]
- Docker Build Error: Failed to get D-Bus connection: Operation not permitted [Solved]
- [Solved] kernel: nvme nvme0: I/O xxx QID xxx timeout, aborting
- [Solved] 01654 error: the index cannot be extended through 8
- SVN Update Error Please execute the ‘Cleanup‘ command [How to Solve]
- [Solved] Error: Flash Download failed – “Cortex-M3“
- [Solved] INSTALL_FAILED_DEXOPT (DEX optimization verification failed)
- [Solved] MinIO Start Error: “WARNING: Console endpoint is listening on a dynamic port…”
- The execution of ExecuteNonQuery by oraclecommand is suspended
- [Solved] GP tool Call Error: ERROR 000824: The tool is not licensed.
- How to Solve Hexo init error: bash: hexo: command not found
- ubuntu20.04——hdaudioC0D2: unable to bind the codec
- Error getting authority: Error initializing authority: Could not connect: No such file or directory
- Error: an error occurred while performing the step: “building kernel modules”. See/var/log/NV
- How to Sovle expdp/impdp Data Pump Error
- How to Solve Redis Cluster Build Error
- [Solved] Triton-inference-server Start Error: Internal – failed to load all models
- Git pull code error fatal: authentication failed fo
- Filezilla Error: You appear to be behind a NAT router. Please configure the passive mode settings and …
- Internalerror: GPU sync failed error (How to Solve)