Hi,
I have a strange problem with a custom EFM32LG230F128 based-design and I am getting out of ideas.
I am using Tiny Gecko's SEGGER J-Link debugger to program my module and so far it works fine.
Display All
However, as soon as the debugger is detached (JLinkExe process killed), the CPU hangs and enters an infinite loop of rebooting because of the watchdog.
This issue is quite problematic and I have run out of clues.
I very much appreciate your help.
I have a strange problem with a custom EFM32LG230F128 based-design and I am getting out of ideas.
I am using Tiny Gecko's SEGGER J-Link debugger to program my module and so far it works fine.
Source Code: debugger.log
- $ JLinkExe -device EZR32LG230F128 -if swd -speed 1000 -autoconnect 1
- SEGGER J-Link Commander V6.52a (Compiled Oct 2 2019 09:45:00)
- DLL version V6.52a, compiled Oct 2 2019 09:44:47
- Connecting to J-Link via USB...O.K.
- Firmware: Energy Micro EFM32 compiled Dec 10 2012 15:59:12
- Hardware version: V7.00
- S/N: 440007513
- License(s): GDB, RDI
- VTref=3.427V
- Device "EZR32LG230F128RXX" selected.
- Connecting to target via SWD
- Found SW-DP with ID 0x2BA01477
- 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: 0x24770011)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Core found
- AP[0]: AHB-AP ROM base: 0xE00FF000
- CPUID register: 0x412FC231. Implementer code: 0x41 (ARM)
- Found Cortex-M3 r2p1, Little endian.
- FPUnit: 6 code (BP) slots and 2 literal slots
- CoreSight components:
- ROMTbl[0] @ E00FF000
- ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB000 SCS
- ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
- ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
- ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
- ROMTbl[0][4]: E0040000, CID: B105900D, PID: 003BB923 TPIU-Lite
- ROMTbl[0][5]: E0041000, CID: B105900D, PID: 003BB924 ETM-M3
- Cortex-M3 identified.
- > loadbin file.bin,0
- > r
- > g
However, as soon as the debugger is detached (JLinkExe process killed), the CPU hangs and enters an infinite loop of rebooting because of the watchdog.
This issue is quite problematic and I have run out of clues.
I very much appreciate your help.