ESP32 Forum

ESP32 Official Forum
http://esp32.io/

Can not get running the debugging with "Espressif IDF plugins for Eclipse"

http://esp32.io/viewtopic.php?f=40&t=28557

Page 1 of 1

Can not get running the debugging with "Espressif IDF plugins for Eclipse"

Posted: Sun Jun 26, 2022 1:23 pm
by MickPF
Hello,

I've got some problems to get running the debugging with Eclipse and the "Espressif IDF plugins for Eclipse"!

I use ESP-IDF 4.4.1 with the board ESP32-S3-DevKitC-1 and the JTAG adapter ESP-Prog under Ubuntu 22.04.

I've installed the "Eclipse IDE for Embedded C/C++ Developers" (ver. 2022-06) and "Espressif IDF plugins for Eclipse" (ver. 2.5.0.202206080113). This installation process installed the "Embedded C/C++ OpenOCD Debugging" also.

The first unanswered question: Is it necessary to install the following additional components as they appear when I run eclipse "Install New Software" again?

Code: Select all

    Espressif IDF
        Embedded C/C++ CMSIS Packs Core Plug-in
        Embedded C/C++ Core
        Embedded C/C++ GDB JTAG Debugging
Before that they didn't appear under "Espressif IDF"!

Following instructions in "ESP-IDF GDB OpenOCD Debugging" (https://github.com/espressif/idf-eclips ... bugging.md) I've made following changes to defaults in a new "Debug Configurations", tab "Debugger":

Code: Select all

    OpenOCD Setup
        Executable path   : ${env_var:IDF_TOOLS_PATH}/tools/openocd-esp32/v0.11.0-esp32-20220411/openocd-esp32/bin/openocd
        Config options    : -s ${env_var:IDF_TOOLS_PATH}/tools/openocd-esp32/v0.11.0-esp32-20220411/openocd-esp32/share/openocd/scripts -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp32s3-ftdi.cfg
    GDB Client Setup
        Actual executable : ${env_var:IDF_TOOLS_PATH}/tools/xtensa-esp32s3-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32s3-elf/bin/xtensa-esp32s3-elf-gdb
The dialog "Debug Configuration", tab "Debugger" does not contain the fields "Flash voltage", "Target" and "Board"!

The first problem after making these changes you can see in the attached screen shot. Nothing happens when I press one of both buttons! I can't recognize what I should change in the "Launch Target"!

The second unanswered question: I can select the serial interface "/dev/ttyUSB1" for flashing in the field "Launch Target" of the launch bar, but where do I enter the serial interface "/dev/ttyUSB0" for debugging?

Starting debugging with these settings generates following console output:

Code: Select all

Open On-Chip Debugger  v0.11.0-esp32-20220411 (2022-04-11-08:47)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz

Warn : Interface already configured, ignoring
adapter speed: 5000 kHz

Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 5000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: esp32s3.cpu0: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : target esp32s3.cpu0 examination failed
Warn : target esp32s3.cpu1 examination failed
Info : starting gdb server for esp32s3.cpu0 on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Error: Target not examined yet
Error executing event gdb-attach on target esp32s3.cpu0:

Warn : No symbols for FreeRTOS!
Error: Target not halted
Error: auto_probe failed
Error: Connect failed. Consider setting up a gdb-attach event for the target to prepare target for GDB connect, or use 'gdb_memory_m
ap disable'.
Error: attempted 'gdb' connection rejected
shutdown command invoked
The third unanswered question: The interface file "interface/ftdi/esp32_devkitj_v1.cfg" sets the clock speed to 20000 kHz, the board file "board/esp32s3-ftdi.cfg" changes it to 5000 kHz, is this clock changing really necessary?

Am I doing something wrong?

Can somebody help me to get running the debugging?

Thanks in advance,
Michael

Re: Can not get running the debugging with "Espressif IDF plugins for Eclipse"

Posted: Mon Jun 27, 2022 5:24 am
by ESP_kondalkolipaka
Hello,
The first unanswered question: Is it necessary to install the following additional components as they appear when I run eclipse "Install New Software" again?
Yes all of them are required except "Embedded C/C++ CMSIS Packs Core Plug-in". v2.4.0 and earlier versions were using GNU-based eclipse plugin for OpenOCD debugging and now this uses Embedded CDT OpenOCD plugins. CMSIS plugin dependency will be removed in the release.
Following instructions in "ESP-IDF GDB OpenOCD Debugging" (https://github.com/espressif/idf-eclips ... bugging.md) I've made following changes to defaults in a new "Debug Configurations", tab "Debugger":
GDBClient and OpenOCD paths will be auto-configured. We needn't to make any changes unless you want to use a different version of OpenOCD/GDBClient than what is installed by default.
The second unanswered question: I can select the serial interface "/dev/ttyUSB1" for flashing in the field "Launch Target" of the launch bar, but where do I enter the serial interface "/dev/ttyUSB0" for debugging?
The serial interface configured in the launch target will be used for debugging as well. I am not sure what do you mean by selecting a different interface for debugging? Could you provide more details on this
The first problem after making these changes you can see in the attached screen shot. Nothing happens when I press one of both buttons! I can't recognize what I should change in the "Launch Target"!
This prompt could be because the "launch target" that you have selected on the eclipse toolbar is different from what is selected in the debugger configuration. Could you verify this? For example, esp32s3 would have selected on the launch target but in the debugger configuration tab "target" and "board" selections might be different. Based on the target and board selection, config options will be auto-shown.

Re: Can not get running the debugging with "Espressif IDF plugins for Eclipse"

Posted: Mon Jun 27, 2022 7:09 am
by denys.almazov
Hi Michael,
The dialog "Debug Configuration", tab "Debugger" does not contain the fields "Flash voltage", "Target" and "Board"!

The first problem after making these changes you can see in the attached screen shot. Nothing happens when I press one of both buttons! I can't recognize what I should change in the "Launch Target"!
This problem can occur for two reasons:

1. Empty the "OPENOCD_SCRIPTS" variable. To check it in the Eclipse, go to "Preferences -> C/C++ -> Build -> Environment -> OPENOCD_SCRIPTS".
2. "esp-config.json" may not be in the openocd folder. The path for it should be like this "..\.espressif\tools\openocd-esp32\v0.11.0-esp32-20211220\openocd-esp32\share\openocd\scripts\esp-config.json"

Best regards,
Denys

Re: Can not get running the debugging with "Espressif IDF plugins for Eclipse"

Posted: Mon Jun 27, 2022 9:19 am
by ESP_Alexey
Hi Michael
The third unanswered question: The interface file "interface/ftdi/esp32_devkitj_v1.cfg" sets the clock speed to 20000 kHz, the board file "board/esp32s3-ftdi.cfg" changes it to 5000 kHz, is this clock changing really necessary?
No. This ambiguity will be removed in the next OpenOCD release.

BTW, If you use board config file "board/esp32s3-ftdi.cfg" you do not need to use interface one "interface/ftdi/esp32_devkitj_v1.cfg". The former one includes that. So "OpenOCD Setup" could be simplified:

Code: Select all

Config options    : -s ${env_var:IDF_TOOLS_PATH}/tools/openocd-esp32/v0.11.0-esp32-20220411/openocd-esp32/share/openocd/scripts -f board/esp32s3-ftdi.cfg

Code: Select all

Warn : target esp32s3.cpu0 examination failed
Warn : target esp32s3.cpu1 examination failed
Note that ESP32-S3 has builtin USB_JTAG interface and it is enabled by default. To use it you just need to connect USB cable to respective port on ESP32-S3-DevKitC-1 (marked as USB) and use "-f board/esp32s3-builtin.cfg" in OpenOCD command line. Please, check it.

If you want to use JTAG I/O pins you need to configure chip's efuses. Please, note all efuse operations are irreversible. You have two options:
  • Switch to JTAG I/O pins permanently by burning "DIS_USB_JTAG" efuse
  • Make JTAG interface selectable by GPIO3 (1 - USB_JTAG, 0 - JTAG I/O pins) by burning "STRAP_JTAG_SEL" efuse

Re: Can not get running the debugging with "Espressif IDF plugins for Eclipse"

Posted: Mon Jun 27, 2022 12:49 pm
by MickPF
Hello,

When I try to install these two of three modules/extensions ("Embedded C/C++ Core" and "Embedded C/C++ GDB JTAG Debugging"), I get the message that newer versions are already installed! Then what means this misleading message that these modules are to be installed!

A few days ago I noticed that the type "Build" was missing in the project properties. But I don't know if it's intentional or a mistake! So I can't check any build settings, also not the "OPENOCD_SCRIPTS"... See the attachment...

I've read again the chapter "OpenOCD Debugging" in the ESP-IDF manual for ESP32-S3 and changed the "Config options" to

Code: Select all

-s ${env_var:IDF_TOOLS_PATH}/tools/openocd-esp32/v0.11.0-esp32-20220411/openocd-esp32/share/openocd/scripts -f board/esp32s3-builtin.cfg
I'm stupid, it's not necessary to use any JTAG adapter, I can debug through the second USB connector. It gets the device "/dev/ttyACM0".

Now I'm a little bit further. After these changes:

The message window with the title "IDF Launch Target Changed" appears again...

When I start the debugging eclipse shows the following console output

Code: Select all

Open On-Chip Debugger  v0.11.0-esp32-20220411 (2022-04-11-08:47)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
Info : esp_usb_jtag: VID set to 0x303a and PID to 0x1001
Info : esp_usb_jtag: capabilities descriptor set to 0x2000
Warn : Transport "jtag" was already selected
Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : esp_usb_jtag: serial (7C:DF:A1:E1:7D:68)
Info : esp_usb_jtag: Device found. Base speed 40000KHz, div range 1 to 255
Info : clock speed 40000 kHz
Info : JTAG tap: esp32s3.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32s3.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32s3.cpu0: Debug controller was reset.
Info : esp32s3.cpu0: Core was reset.
Info : esp32s3.cpu1: Debug controller was reset.
Info : esp32s3.cpu1: Core was reset.
Info : starting gdb server for esp32s3.cpu0 on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : esp32s3.cpu0: Target halted, PC=0x42040496, debug_reason=00000000
Info : Set GDB target to 'esp32s3.cpu0'
Info : esp32s3.cpu1: Target halted, PC=0x42040496, debug_reason=00000000
Warn : No symbols for FreeRTOS!
Info : esp32s3.cpu0: Target halted, PC=0x403B245E, debug_reason=00000001
Info : Flash mapping 0: 0x10020 -> 0x3c050020, 69 KB
Info : Flash mapping 1: 0x30020 -> 0x42000020, 261 KB
Info : esp32s3.cpu0: Target halted, PC=0x403B245E, debug_reason=00000001
Info : Auto-detected flash bank 'esp32s3.cpu0.flash' size 8192 KB
Info : Using flash bank 'esp32s3.cpu0.flash' size 8192 KB
Info : esp32s3.cpu0: Target halted, PC=0x403B245E, debug_reason=00000001
Info : Flash mapping 0: 0x10020 -> 0x3c050020, 69 KB
Info : Flash mapping 1: 0x30020 -> 0x42000020, 261 KB
Info : Using flash bank 'esp32s3.cpu0.irom' size 264 KB
Info : esp32s3.cpu0: Target halted, PC=0x403B245E, debug_reason=00000001
Info : Flash mapping 0: 0x10020 -> 0x3c050020, 69 KB
Info : Flash mapping 1: 0x30020 -> 0x42000020, 261 KB
Info : Using flash bank 'esp32s3.cpu0.drom' size 72 KB
Info : New GDB Connection: 1, Target esp32s3.cpu0, state: halted
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
Info : JTAG tap: esp32s3.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32s3.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32s3.cpu0: Debug controller was reset.
Info : esp32s3.cpu0: Core was reset.
Info : esp32s3.cpu0: Target halted, PC=0x500000EF, debug_reason=00000000
Info : esp32s3.cpu0: Core was reset.
Info : esp32s3.cpu0: Target halted, PC=0x40000400, debug_reason=00000000
Info : esp32s3.cpu1: Debug controller was reset.
Info : esp32s3.cpu1: Core was reset.
Info : esp32s3.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
Info : JTAG tap: esp32s3.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32s3.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32s3.cpu0: Debug controller was reset.
Info : esp32s3.cpu0: Core was reset.
Info : esp32s3.cpu0: Target halted, PC=0x500000EF, debug_reason=00000000
Info : esp32s3.cpu0: Core was reset.
Info : esp32s3.cpu0: Target halted, PC=0x40000400, debug_reason=00000000
Info : esp32s3.cpu1: Debug controller was reset.
Info : esp32s3.cpu1: Core was reset.
Info : esp32s3.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
semihosting is enabled

Info : JTAG tap: esp32s3.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32s3.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : esp32s3.cpu0: Debug controller was reset.
Info : esp32s3.cpu0: Core was reset.
Info : esp32s3.cpu0: Target halted, PC=0x500000EF, debug_reason=00000000
Info : esp32s3.cpu0: Core was reset.
Info : esp32s3.cpu0: Target halted, PC=0x40000400, debug_reason=00000000
Info : esp32s3.cpu1: Debug controller was reset.
Info : esp32s3.cpu1: Core was reset.
Info : esp32s3.cpu1: Target halted, PC=0x40000400, debug_reason=00000000
===== Xtensa registers
(0) pc (/32): 0x40000400
(1) ar0 (/32): 0x00000000
(2) ar1 (/32): 0x00000000
(3) ar2 (/32): 0x00000000
(4) ar3 (/32): 0x00000000
(5) ar4 (/32): 0x00000000
(6) ar5 (/32): 0x00000000
(7) ar6 (/32): 0x00000000
(8) ar7 (/32): 0x00000000
(9) ar8 (/32): 0x00000000
(10) ar9 (/32): 0x00000000
(11) ar10 (/32): 0x00000000
(12) ar11 (/32): 0x00000000
(13) ar12 (/32): 0x00000000
(14) ar13 (/32): 0x00000000
(15) ar14 (/32): 0x00000000
(16) ar15 (/32): 0x00000000
(17) ar16 (/32): 0x00000000
(18) ar17 (/32): 0x00000000
(19) ar18 (/32): 0x00000000
(20) ar19 (/32): 0x00000000
(21) ar20 (/32): 0x00000000
(22) ar21 (/32): 0x00000000
(23) ar22 (/32): 0x00000000
(24) ar23 (/32): 0x00000000
(25) ar24 (/32): 0x00000000
(26) ar25 (/32): 0x00000000
(27) ar26 (/32): 0x00000000
(28) ar27 (/32): 0x00000000
(29) ar28 (/32): 0x00000000
(30) ar29 (/32): 0x00000000
(31) ar30 (/32): 0x00000000
(32) ar31 (/32): 0x00000000
(33) ar32 (/32): 0x00000000
(34) ar33 (/32): 0x00000000
(35) ar34 (/32): 0x00000000
(36) ar35 (/32): 0x00000000
(37) ar36 (/32): 0x00000000
(38) ar37 (/32): 0x00000000
(39) ar38 (/32): 0x00000000
(40) ar39 (/32): 0x00000000
(41) ar40 (/32): 0x00000000
(42) ar41 (/32): 0x00000000
(43) ar42 (/32): 0x00000000
(44) ar43 (/32): 0x00000000
(45) ar44 (/32): 0x00000000
(46) ar45 (/32): 0x00000000
(47) ar46 (/32): 0x00000000
(48) ar47 (/32): 0x00000000
(49) ar48 (/32): 0x00000000
(50) ar49 (/32): 0x00000000
(51) ar50 (/32): 0x00000000
(52) ar51 (/32): 0x00000000
(53) ar52 (/32): 0x00000000
(54) ar53 (/32): 0x00000000
(55) ar54 (/32): 0x00000000
(56) ar55 (/32): 0x00000000
(57) ar56 (/32): 0x00000000
(58) ar57 (/32): 0x00000000
(59) ar58 (/32): 0x00000000
(60) ar59 (/32): 0x00000000
(61) ar60 (/32): 0x00000000
(62) ar61 (/32): 0x00000000
(63) ar62 (/32): 0x00000000
(64) ar63 (/32): 0x00000000
(65) lbeg (/32): 0x00000000
(66) lend (/32): 0x00000000
(67) lcount (/32): 0x00000000
(68) sar (/32): 0x00000000
(69) windowbase (/32): 0x00000000
(70) windowstart (/32): 0x00000001
(71) configid0 (/32): 0x40000400
(72) configid1 (/32): 0x23090f1f
(73) ps (/32): 0x0000001f
(74) threadptr (/32): 0x00000000
(75) br (/32): 0x00000000
(76) scompare1 (/32): 0x00000000
(77) acclo (/32): 0x00000000
(78) acchi (/32): 0x00000000
(79) m0 (/32): 0x00000000
(80) m1 (/32): 0x00000000
(81) m2 (/32): 0x00000000
(82) m3 (/32): 0x00000000
(83) f0 (/32): 0x00000000
(84) f1 (/32): 0x00000000
(85) f2 (/32): 0x00000000
(86) f3 (/32): 0x00000000
(87) f4 (/32): 0x00000000
(88) f5 (/32): 0x00000000
(89) f6 (/32): 0x00000000
(90) f7 (/32): 0x00000000
(91) f8 (/32): 0x00000000
(92) f9 (/32): 0x00000000
(93) f10 (/32): 0x00000000
(94) f11 (/32): 0x00000000
(95) f12 (/32): 0x00000000
(96) f13 (/32): 0x00000000
(97) f14 (/32): 0x00000000
(98) f15 (/32): 0x00000000
(99) fcr (/32): 0x00000000
(100) fsr (/32): 0x00000000
(101) mmid (/32)
(102) ibreakenable (/32): 0x00000000
(103) memctl (/32): 0x00000001
(104) atomctl (/32): 0x00000028
(105) ibreaka0 (/32): 0x00000000
(106) ibreaka1 (/32): 0x00000000
(107) dbreaka0 (/32): 0x00000000
(108) dbreaka1 (/32): 0x00000000
(109) dbreakc0 (/32): 0x00000000
(110) dbreakc1 (/32): 0x00000000
(111) epc1 (/32): 0x00000000
(112) epc2 (/32): 0x00000000
(113) epc3 (/32): 0x00000000
(114) epc4 (/32): 0x00000000
(115) epc5 (/32): 0x00000000
(116) epc6 (/32): 0x40000400
(117) epc7 (/32): 0x00000000
(118) depc (/32): 0x00000000
(119) eps2 (/32): 0x00000000
(120) eps3 (/32): 0x00000000
(121) eps4 (/32): 0x00000000
(122) eps5 (/32): 0x00000000
(123) eps6 (/32): 0x0000001f
(124) eps7 (/32): 0x00000000
(125) excsave1 (/32): 0x00000000
(126) excsave2 (/32): 0x00000000
(127) excsave3 (/32): 0x00000000
(128) excsave4 (/32): 0x00000000
(129) excsave5 (/32): 0x00000000
(130) excsave6 (/32): 0x00000000
(131) excsave7 (/32): 0x00000000
(132) cpenable (/32): 0x000000ff
(133) interrupt (/32): 0x00018040
(134) intset (/32)
(135) intclear (/32)
(136) intenable (/32): 0x00000000
(137) vecbase (/32): 0x40000000
(138) exccause (/32): 0x00000000
(139) debugcause (/32): 0x00000020
(140) ccount (/32): 0x00000003
(141) prid (/32): 0x0000cdcd
(142) icount (/32): 0x00000000
(143) icountlevel (/32): 0x00000000
(144) excvaddr (/32): 0x00000000
(145) ccompare0 (/32): 0x00000000
(146) ccompare1 (/32): 0x00000000
(147) ccompare2 (/32): 0x00000000
(148) misc0 (/32): 0x00000000
(149) misc1 (/32): 0x00000000
(150) misc2 (/32): 0x00000000
(151) misc3 (/32): 0x00000000
(163) a0 (/32): 0x00000000
(164) a1 (/32): 0x00000000
(165) a2 (/32): 0x00000000
(166) a3 (/32): 0x00000000 (dirty)
(167) a4 (/32): 0x00000000
(168) a5 (/32): 0x00000000
(169) a6 (/32): 0x00000000
(170) a7 (/32): 0x00000000
(171) a8 (/32): 0x00000000
(172) a9 (/32): 0x00000000
(173) a10 (/32): 0x00000000
(174) a11 (/32): 0x00000000
(175) a12 (/32): 0x00000000
(176) a13 (/32): 0x00000000
(177) a14 (/32): 0x00000000
(178) a15 (/32): 0x00000000
(179) pwrctl (/32)
(180) pwrstat (/32)
(181) eristat (/32)
(182) cs_itctrl (/32)
(183) cs_claimset (/32)
(184) cs_claimclr (/32)
(185) cs_lockaccess (/32)
(186) cs_lockstatus (/32)
(187) cs_authstatus (/32)
(188) fault_info (/32)
(189) trax_id (/32)
(190) trax_ctrl (/32)
(191) trax_stat (/32)
(192) trax_data (/32)
(193) trax_addr (/32)
(194) trax_pctrigger (/32)
(195) trax_pcmatch (/32)
(196) trax_delay (/32)
(197) trax_memstart (/32)
(198) trax_memend (/32)
(199) pmg (/32)
(200) pmoc (/32)
(201) pm0 (/32)
(202) pm1 (/32)
(203) pmctrl0 (/32)
(204) pmctrl1 (/32)
(205) pmstat0 (/32)
(206) pmstat1 (/32)
(207) ocd_id (/32)
(208) ocd_dcrclr (/32)
(209) ocd_dcrset (/32)
(210) ocd_dsr (/32)
(211) ddr (/32)
(212) gpio_out (/32)
(213) accx_0 (/32)
(214) accx_1 (/32)
(215) qacc_h_0 (/32)
(216) qacc_h_1 (/32)
(217) qacc_h_2 (/32)
(218) qacc_h_3 (/32)
(219) qacc_h_4 (/32)
(220) qacc_l_0 (/32)
(221) qacc_l_1 (/32)
(222) qacc_l_2 (/32)
(223) qacc_l_3 (/32)
(224) qacc_l_4 (/32)
(225) sar_byte (/32)
(226) fft_bit_width (/32)
(227) ua_state_0 (/32)
(228) ua_state_1 (/32)
(229) ua_state_2 (/32)
(230) ua_state_3 (/32)
(231) q0 (/128)
(232) q1 (/128)
(233) q2 (/128)
(234) q3 (/128)
(235) q4 (/128)
(236) q5 (/128)
(237) q6 (/128)
(238) q7 (/128)
In a new register in the middle window area with title "0x40000400" appears the message

Code: Select all

Break at address "0x40000400" with no debug information available, or outside of program code.
with buttons "View Disassembly..." and "Preferences..." and the debugging is terminated.

What is going wrong now?
All times are UTC
Page 1 of 1
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/