Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- //connect
- Connecting to target via SWD
- Found SW-DP with ID 0x1BA01477
- Active write protected STM32 device detected.
- This could cause problems during flash download.
- Note: Unsecuring will trigger a mass erase of the internal flash.
- Device will be unsecured now.
- Found SW-DP with ID 0x1BA01477
- Scanning AP map to find all available APs
- AP[1]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x14770011)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Core found
- AP[0]: AHB-AP ROM base: 0xE00FF000
- CPUID register: 0x411FC231. Implementer code: 0x41 (ARM)
- Found Cortex-M3 r1p1, Little endian.
- FPUnit: 6 code (BP) slots and 2 literal slots
- CoreSight components:
- ROMTbl[0] @ E00FF000
- ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 001BB000 SCS
- ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 001BB002 DWT
- ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 000BB003 FPB
- ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 001BB001 ITM
- ROMTbl[0][4]: E0040000, CID: B105900D, PID: 001BB923 TPIU-Lite
- Cortex-M3 identified.
- //flash
- J-Link connection not established yet but required for command.
- Connecting to J-Link via USB...O.K.
- Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
- Hardware version: V8.00
- S/N: 20150703
- License(s): RDI, FlashBP, FlashDL, JFlash, GDB
- VTref=3.306V
- Target connection not established yet but required for command.
- Device "STM32F103C8" selected.
- Connecting to target via SWD
- Found SW-DP with ID 0x1BA01477
- Active write protected STM32 device detected.
- This could cause problems during flash download.
- Note: Unsecuring will trigger a mass erase of the internal flash.
- Device will be unsecured now.
- Found SW-DP with ID 0x1BA01477
- Scanning AP map to find all available APs
- AP[1]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x14770011)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Core found
- AP[0]: AHB-AP ROM base: 0xE00FF000
- CPUID register: 0x411FC231. Implementer code: 0x41 (ARM)
- Found Cortex-M3 r1p1, Little endian.
- FPUnit: 6 code (BP) slots and 2 literal slots
- CoreSight components:
- ROMTbl[0] @ E00FF000
- ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 001BB000 SCS
- ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 001BB002 DWT
- ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 000BB003 FPB
- ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 001BB001 ITM
- ROMTbl[0][4]: E0040000, CID: B105900D, PID: 001BB923 TPIU-Lite
- Cortex-M3 identified.
- **************************
- WARNING: CPU could not be halted
- **************************
- Downloading file [build/STM32CubeMx.hex]...
- **************************
- WARNING: CPU could not be halted
- **************************
- ****** Error: Verification of RAMCode failed @ address 0x20000000.
- Write: 0xA801BE00 F0009900
- Read: 0x00000000 00000000
- Failed to prepare for programming.
- Failed to download RAMCode!
- Can not read register 16 (XPSR) while CPU is running
- Can not read register 20 (CFBP) while CPU is running
- Can not read register 0 (R0) while CPU is running
- Can not read register 1 (R1) while CPU is running
- Can not read register 2 (R2) while CPU is running
- Can not read register 3 (R3) while CPU is running
- Can not read register 4 (R4) while CPU is running
- Can not read register 5 (R5) while CPU is running
- Can not read register 6 (R6) while CPU is running
- Can not read register 7 (R7) while CPU is running
- Can not read register 8 (R8) while CPU is running
- Can not read register 9 (R9) while CPU is running
- Can not read register 10 (R10) while CPU is running
- Can not read register 11 (R11) while CPU is running
- Can not read register 12 (R12) while CPU is running
- Can not read register 14 (R14) while CPU is running
- Can not read register 15 (R15) while CPU
- Unspecified error -1
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement