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:
- [Solved] Keil5 burn STM32F chip Error: error: Flash download failed – “cortex-m4″“
- [Solved] Keil Error: Error: Flash Download failed – “Cortex-M4“
- [Solved] STM32F4 MDK5 Software Simulate Error: error 65: no ‘read‘ permission
- RabbitMQ：address (cannot connect to host/port) [How to Solve]
- [Solved] No corresponding flash error is found during MDK download
- ST-LINK Download Program Error: flash download failed – ‘cortex m4‘
- How to Solve svn error: WC DB
- [Solved] ZYNQ download program error: Memory write error at 0x100000. APB
- Docker Build Error: Failed to get D-Bus connection: Operation not permitted [Solved]
- [Solved] ZYNQ Programs Error: memory write error at 0x100000.APB AP transaction error,DAP status f0000021
- [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]
- Matlab Raspberry Pi Error: External Mode Open Protocol Connect command failed
- [Solved] Tensorflow-gpu Error: self._traceback = tf_stack.extract_stack()
- [Solved] Parcel Service Error: regeneratorRuntime is not defined
- Wildfly (JBoss) startup error: ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation (“add”) failed
- [Solved] Error: Flash Download failed – “Cortex-M3“
- [Solved] MinIO Start Error: “WARNING: Console endpoint is listening on a dynamic port…”
- [Solved] adb Error: error: no devices/emulators found error: cannot connect to daemon