[ERROR] Failed to write memory to target - GDB attempted to write to program memory via an "M" packet - this is not supported. #122

frankE · 2024-12-03T19:53:58Z

frankE
Dec 3, 2024

Hi,
I'm trying to use bloom with CLion and get the error from the title. I had to build avr-gdb 15.2 by myself since there is no such package in the Fedora 41 repositories.

The bloom debug log says:

2024-12-03 20:31:05.682 CET [MT]: [DEBUG] Debug log printing has been enabled
2024-12-03 20:31:05.683 CET [MT]: [DEBUG] Bloom version: 1.0.0
2024-12-03 20:31:05.683 CET [MT]: [INFO] Selected environment: "default"
2024-12-03 20:31:05.683 CET [MT]: [DEBUG] Number of environments extracted from config: 1
2024-12-03 20:31:05.683 CET [SH]: [DEBUG] Starting SignalHandler
2024-12-03 20:31:05.683 CET [SH]: [DEBUG] SignalHandler ready
2024-12-03 20:31:05.683 CET [TC]: [INFO] Starting TargetController
2024-12-03 20:31:05.689 CET [TC]: [INFO] Connecting to debug tool
2024-12-03 20:31:05.697 CET [TC]: [DEBUG] HID device path: 3-6.3.4:1.0
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
2024-12-03 20:31:05.743 CET [TC]: [INFO] Debug tool connected
2024-12-03 20:31:05.743 CET [TC]: [INFO] Debug tool name: Xplained Mini
2024-12-03 20:31:05.783 CET [TC]: [INFO] Debug tool serial: ATML2523052700012264
2024-12-03 20:31:05.783 CET [TC]: [DEBUG] Loading AVR8 target description file: /opt/bloom/bin/../resources/TargetDescriptionFiles/AVR/AVR8/MEGA/ATMEGA328PB.xml
2024-12-03 20:31:05.790 CET [TC]: [INFO] Activating target
2024-12-03 20:31:05.831 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x00, id: 0x00, value: 0x01)
2024-12-03 20:31:05.871 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x00, id: 0x01, value: 0x02)
2024-12-03 20:31:05.911 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x01, id: 0x00, value: 0x05)
2024-12-03 20:31:05.911 CET [TC]: [DEBUG] Setting FLASH_PAGE_SIZE AVR8 device parameter
2024-12-03 20:31:05.951 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x00, value: 0x8000)
2024-12-03 20:31:05.951 CET [TC]: [DEBUG] Setting FLASH_SIZE AVR8 device parameter
2024-12-03 20:31:05.991 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x02, value: 0x00800000)
2024-12-03 20:31:05.991 CET [TC]: [DEBUG] Setting FLASH_BASE AVR8 device parameter
2024-12-03 20:31:06.031 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x06, value: 0x00000000)
2024-12-03 20:31:06.031 CET [TC]: [DEBUG] Setting SRAM_START AVR8 device parameter
2024-12-03 20:31:06.071 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x0e, value: 0x0001)
2024-12-03 20:31:06.071 CET [TC]: [DEBUG] Setting EEPROM_SIZE AVR8 device parameter
2024-12-03 20:31:06.111 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x10, value: 0x0004)
2024-12-03 20:31:06.111 CET [TC]: [DEBUG] Setting EEPROM_PAGE_SIZE AVR8 device parameter
2024-12-03 20:31:06.151 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x12, value: 0x04)
2024-12-03 20:31:06.151 CET [TC]: [DEBUG] Setting OCD_REVISION AVR8 device parameter
2024-12-03 20:31:06.191 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x13, value: 0x01)
2024-12-03 20:31:06.191 CET [TC]: [DEBUG] Setting OCD_DATA_REGISTER AVR8 device parameter
2024-12-03 20:31:06.231 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x18, value: 0x31)
2024-12-03 20:31:06.231 CET [TC]: [DEBUG] Setting SPMCR_REGISTER AVR8 device parameter
2024-12-03 20:31:06.271 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x1d, value: 0x57)
2024-12-03 20:31:06.271 CET [TC]: [DEBUG] Setting BOOT_START_ADDR AVR8 device parameter
2024-12-03 20:31:06.311 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x0a, value: 0x003f0000)
2024-12-03 20:31:06.311 CET [TC]: [DEBUG] Setting OSCCAL_ADDR AVR8 device parameter
2024-12-03 20:31:06.351 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x1e, value: 0x46)
2024-12-03 20:31:06.351 CET [TC]: [DEBUG] Setting EEARL_ADDR AVR8 device parameter
2024-12-03 20:31:06.391 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x1a, value: 0x21)
2024-12-03 20:31:06.391 CET [TC]: [DEBUG] Setting EEARH_ADDR AVR8 device parameter
2024-12-03 20:31:06.431 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x19, value: 0x22)
2024-12-03 20:31:06.431 CET [TC]: [DEBUG] Setting EECR_ADDR AVR8 device parameter
2024-12-03 20:31:06.471 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x1b, value: 0x1f)
2024-12-03 20:31:06.471 CET [TC]: [DEBUG] Setting EEDR_ADDR AVR8 device parameter
2024-12-03 20:31:06.511 CET [TC]: [DEBUG] Setting AVR8 EDBG parameter (context: 0x02, id: 0x1c, value: 0x20)
2024-12-03 20:31:07.056 CET [TC]: [INFO] Target activated
2024-12-03 20:31:07.056 CET [TC]: [INFO] Target ID: 0x1e9516
2024-12-03 20:31:07.056 CET [TC]: [INFO] Target name: ATmega328PB
2024-12-03 20:31:07.056 CET [TC]: [INFO] Available hardware breakpoints: 0
2024-12-03 20:31:07.111 CET [TC]: [DEBUG] Event "TargetControllerThreadStateChanged" (1) registered for listener ApplicationEventListener
2024-12-03 20:31:07.111 CET [TC]: [DEBUG] TargetController ready and waiting for events.
2024-12-03 20:31:07.111 CET [DS]: [INFO] Starting DebugServer
2024-12-03 20:31:07.112 CET [DS]: [DEBUG] Issuing GetTargetDescriptor command (ID: 1) to TargetController
2024-12-03 20:31:07.143 CET [DS]: [DEBUG] Delivering response for GetTargetDescriptor command (ID: 1)
2024-12-03 20:31:07.143 CET [DS]: [INFO] Selected DebugServer: AVR GDB Remote Serial Protocol Debug Server
2024-12-03 20:31:07.143 CET [DS]: [INFO] GDB RSP address: 127.0.0.1
2024-12-03 20:31:07.143 CET [DS]: [INFO] GDB RSP port: 1442
2024-12-03 20:31:07.143 CET [DS]: [WARNING] Bloom's process is being managed by CLion - Bloom will automatically shutdown upon detaching from GDB.
2024-12-03 20:31:07.143 CET [DS]: [DEBUG] Event "DebugServerThreadStateChanged" (2) registered for listener ApplicationEventListener
2024-12-03 20:31:07.143 CET [DS]: [INFO] DebugServer ready
2024-12-03 20:31:07.144 CET [DS]: [INFO] Waiting for GDB RSP connection
2024-12-03 20:31:08.135 CET [DS]: [INFO] Accepted GDP RSP connection from 127.0.0.1
2024-12-03 20:31:08.135 CET [DS]: [DEBUG] Issuing StopTargetExecution command (ID: 2) to TargetController
2024-12-03 20:31:08.261 CET [TC]: [DEBUG] Event "TargetExecutionStopped" (4) registered for listener DebugServerEventListener
2024-12-03 20:31:08.261 CET [DS]: [DEBUG] Delivering response for StopTargetExecution command (ID: 2)
2024-12-03 20:31:08.261 CET [DS]: [DEBUG] Issuing ResetTarget command (ID: 3) to TargetController
2024-12-03 20:31:08.644 CET [DS]: [DEBUG] Delivering response for ResetTarget command (ID: 3)
2024-12-03 20:31:08.646 CET [DS]: [DEBUG] Read GDB packet: $qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;QThreadOptions+;no-resumed+;memory-tagging+#e7
2024-12-03 20:31:08.646 CET [DS]: [INFO] Handling QuerySupport packet
2024-12-03 20:31:08.646 CET [DS]: [DEBUG] Writing GDB packet: $qSupported:swbreak+;PacketSize=2097000;qXfer:memory-map:read+;vContSupported+;#49
2024-12-03 20:31:08.646 CET [DS]: [DEBUG] Dispatching event TargetExecutionStopped (4).
2024-12-03 20:31:08.648 CET [DS]: [DEBUG] Read GDB packet: $vCont?#49
2024-12-03 20:31:08.648 CET [DS]: [INFO] Handling VContSupportedActionsQuery packet
2024-12-03 20:31:08.648 CET [DS]: [DEBUG] Writing GDB packet: $vCont;c;C;s;S;r#0f
2024-12-03 20:31:08.689 CET [DS]: [DEBUG] Read GDB packet: $vMustReplyEmpty#3a
2024-12-03 20:31:08.689 CET [DS]: [INFO] Handling vMustReplyEmpty
2024-12-03 20:31:08.689 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:08.730 CET [DS]: [DEBUG] Read GDB packet: $Hg0#df
2024-12-03 20:31:08.730 CET [DS]: [DEBUG] Unknown GDB RSP packet: Hg0 - returning empty response
2024-12-03 20:31:08.730 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:08.771 CET [DS]: [DEBUG] Read GDB packet: $qTStatus#49
2024-12-03 20:31:08.771 CET [DS]: [DEBUG] Unknown GDB RSP packet: qTStatus - returning empty response
2024-12-03 20:31:08.771 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:08.812 CET [DS]: [DEBUG] Read GDB packet: $?#3f
2024-12-03 20:31:08.812 CET [DS]: [DEBUG] Writing GDB packet: $T05#b9
2024-12-03 20:31:08.853 CET [DS]: [DEBUG] Read GDB packet: $qfThreadInfo#bb
2024-12-03 20:31:08.853 CET [DS]: [DEBUG] Unknown GDB RSP packet: qfThreadInfo - returning empty response
2024-12-03 20:31:08.853 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:08.894 CET [DS]: [DEBUG] Read GDB packet: $qL1200000000000000000#50
2024-12-03 20:31:08.894 CET [DS]: [DEBUG] Unknown GDB RSP packet: qL1200000000000000000 - returning empty response
2024-12-03 20:31:08.894 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:08.935 CET [DS]: [DEBUG] Read GDB packet: $Hc-1#09
2024-12-03 20:31:08.935 CET [DS]: [DEBUG] Unknown GDB RSP packet: Hc-1 - returning empty response
2024-12-03 20:31:08.935 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:08.977 CET [DS]: [DEBUG] Read GDB packet: $qC#b4
2024-12-03 20:31:08.977 CET [DS]: [DEBUG] Unknown GDB RSP packet: qC - returning empty response
2024-12-03 20:31:08.977 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:09.018 CET [DS]: [DEBUG] Read GDB packet: $qAttached#8f
2024-12-03 20:31:09.018 CET [DS]: [INFO] Handling qAttached
2024-12-03 20:31:09.018 CET [DS]: [DEBUG] Writing GDB packet: $�#01
2024-12-03 20:31:09.059 CET [DS]: [DEBUG] Read GDB packet: $qOffsets#4b
2024-12-03 20:31:09.059 CET [DS]: [DEBUG] Unknown GDB RSP packet: qOffsets - returning empty response
2024-12-03 20:31:09.059 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:09.100 CET [DS]: [DEBUG] Read GDB packet: $g#67
2024-12-03 20:31:09.100 CET [DS]: [INFO] Handling ReadRegisters packet
2024-12-03 20:31:09.100 CET [DS]: [DEBUG] Issuing StartAtomicSession command (ID: 4) to TargetController
2024-12-03 20:31:09.100 CET [DS]: [DEBUG] Delivering response for StartAtomicSession command (ID: 4)
2024-12-03 20:31:09.100 CET [DS]: [DEBUG] Issuing ReadTargetRegisters command (ID: 5) to TargetController
2024-12-03 20:31:09.226 CET [DS]: [DEBUG] Delivering response for ReadTargetRegisters command (ID: 5)
2024-12-03 20:31:09.226 CET [DS]: [DEBUG] Issuing GetTargetProgramCounter command (ID: 6) to TargetController
2024-12-03 20:31:09.266 CET [DS]: [DEBUG] Delivering response for GetTargetProgramCounter command (ID: 6)
2024-12-03 20:31:09.266 CET [DS]: [DEBUG] Issuing EndAtomicSession command (ID: 7) to TargetController
2024-12-03 20:31:09.266 CET [DS]: [DEBUG] Delivering response for EndAtomicSession command (ID: 7)
2024-12-03 20:31:09.266 CET [DS]: [DEBUG] Writing GDB packet: $00000000000000000000000000000000000101000000000000000000ff08b00000ff0800000000#bc
2024-12-03 20:31:09.267 CET [DS]: [DEBUG] Read GDB packet: $qL1200000000000000000#50
2024-12-03 20:31:09.267 CET [DS]: [DEBUG] Unknown GDB RSP packet: qL1200000000000000000 - returning empty response
2024-12-03 20:31:09.267 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:09.308 CET [DS]: [DEBUG] Read GDB packet: $qSymbol::#5b
2024-12-03 20:31:09.308 CET [DS]: [DEBUG] Unknown GDB RSP packet: qSymbol:: - returning empty response
2024-12-03 20:31:09.308 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:09.350 CET [DS]: [DEBUG] Read GDB packet: $qXfer:memory-map:read::0,1000#ab
2024-12-03 20:31:09.350 CET [DS]: [INFO] Handling ReadMemoryMap packet
2024-12-03 20:31:09.350 CET [DS]: [DEBUG] Writing GDB packet: $l<memory-map><memory type="ram" start="8388608" length="66560"/><memory type="flash" start="0" length="32768"><property name="blocksize">128</property></memory></memory-map>#b0
2024-12-03 20:31:09.425 CET [DS]: [DEBUG] Read GDB packet: $X0,0:#1e
2024-12-03 20:31:09.425 CET [DS]: [DEBUG] Unknown GDB RSP packet: X0,0: - returning empty response
2024-12-03 20:31:09.425 CET [DS]: [DEBUG] Writing GDB packet: $ #00
2024-12-03 20:31:09.466 CET [DS]: [DEBUG] Read GDB packet: $M0,398:0c945a000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9479000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c9477000c94770011241fbecfefd8e0debfcdbf11e0a0e0b1e0e8e9f3e002c005900d92a430b107d9f721e0a4e0b1e001c01d92a031b207e1f70e94af010c94ca010c9400001f920f920fb60f9211242f933f938f939f9381e08093020180910c0190910d01019690930d0180930c0180910c0190910d0120910a0130910b01821b930b883c9105c9f080910c0190910d012091080130910901821b930b0297c9f085b190e2892785b99f918f913f912f910f900fbe0f901f90189581e08093010180910c0190910d0190930b0180930a01dbcf81e08093000180910c0190910d019093090180930801dbcf84b18e6084b984b1806284b984b5826084bd85b5856085bd8de487bdeee6f0e0808182608083e0e8f0e08081806f8083808181608083e1e8f0e0808188608083808181608083e0ebf0e08081836080838081806c8083e1ebf0e0808181608083089580910501811155c080910401823009f451c098f48115f9f0813059f482e080930f0183e08093040180e890e8a0e8b0e01cc080e090e0dc0118c0833041f480910f018093040180e090e0dc010ec080e090e0dc010ac081e080930f0183e08093040180e890e8a0e8b0e08093b300492f5a2f6b2f7727552750938b0040938a008a2f90e0909389008093880080910e0180fd1ac0e0e8f0e08081806f8083e0ebf0e08081806c808380910e018f5f80930e01089510920f0183e08093040180e890e8a0e8b0e0d1cfe0e8f0e080818f708083e0ebf0e080818f738083e5cf89b1847090910701913099f0923019f191112bc0811109c091e090930701909106019f5f90930601089510920701892f089581110cc090910601933020f082e08093070108959f5f9093060108951092070180e00895811104c092e09093070108951092070180e0089580e008950e946c01811539f081e090910501911180e08093050108950e94cc007894809102018130e1f71092020180910101811109c080910001811591f30e94a30110920001edcf0e94fd0010920101f2cff894ffcf#c0
2024-12-03 20:31:09.467 CET [DS]: [INFO] Handling WriteMemory packet
2024-12-03 20:31:09.467 CET [DS]: [ERROR] Failed to write memory to target - GDB attempted to write to program memory via an "M" packet - this is not supported. Please report this issue to Bloom developers with the full debug log.
2024-12-03 20:31:09.467 CET [DS]: [DEBUG] Writing GDB packet: $E01#a6
Load failed
2024-12-03 20:31:09.509 CET [DS]: [DEBUG] Read GDB packet: $D#44
2024-12-03 20:31:09.509 CET [DS]: [INFO] Handling Detach packet
2024-12-03 20:31:09.509 CET [DS]: [DEBUG] Issuing Shutdown command (ID: 8) to TargetController
2024-12-03 20:31:09.509 CET [TC]: [INFO] Shutting down TargetController
2024-12-03 20:31:09.509 CET [TC]: [INFO] Deactivating target
2024-12-03 20:31:09.674 CET [TC]: [INFO] Closing debug tool
2024-12-03 20:31:09.716 CET [TC]: [DEBUG] Event "TargetControllerThreadStateChanged" (6) registered for listener ApplicationEventListener
2024-12-03 20:31:09.716 CET [DS]: [DEBUG] Delivering response for Shutdown command (ID: 8)
2024-12-03 20:31:09.716 CET [DS]: [DEBUG] Writing GDB packet: $OK#9a
2024-12-03 20:31:09.717 CET [DS]: [INFO] GDB RSP client disconnected
2024-12-03 20:31:09.717 CET [DS]: [DEBUG] Event "DebugSessionFinished" (7) registered for listener ApplicationEventListener
2024-12-03 20:31:09.717 CET [DS]: [INFO] Waiting for GDB RSP connection
Debugger disconnected

Any suggestions?

Frank

Answered by frankE

Dec 4, 2024

Solved it. I had to manually delete the */config.cache files in the gdb source tree. A make clean didn't do it.

View full answer

navnavnav · 2024-12-03T20:03:31Z

navnavnav
Dec 3, 2024
Maintainer

Hmm, what version of CLion are you using?

Can you try connecting to Bloom via the avr-gdb CLI and then run the load command? Does that work? I'm trying to figure out if CLion is invoking a different command to program the target, resulting in this error.

0 replies

frankE · 2024-12-03T20:17:58Z

frankE
Dec 3, 2024
Author

Thanks for the quick reply!
CLion version is 2024.3.

When I try to load the program via the avr-gdb CLI the same error message occurs. Additionally avr-gdb says:

(gdb) load
warning: Can not parse XML memory map; XML support was disabled at compile time
Loading section .text, size 0x398 lma 0x0
Load failed

It seems I have done something stupid while building gdb. Looks expat is missing from gdb? expat-devel is installed and configure was run with --with-expat

5 replies

navnavnav Dec 3, 2024
Maintainer

expat-devel is installed and configure was run with --with-expat

Sorry, missed this. Do you still have the GCC output? Maybe that will shed some light on why XML support was not enabled.

You should find something like this in the output:

checking whether to use expat... yes
checking for libexpat...

I see that in the early stages of compiling, after running ../configure --target=avr --with-expat --with-libexpat-prefix=/usr/local/ and then invoking make.

frankE Dec 3, 2024
Author

Unfortunately I can't build gdb with expat at the moment. expat-devel is installed but gdb doesn't recognize it.
This is the error I get during compilation:

checking whether to use expat... yes
checking for libexpat... (cached) no
configure: error: expat is missing or unusable

I even tried to compile expat from source, installed it under $HOME/.local and used --with-libexpat-prefix=$HOME/.local. But still no success. I'll have another try tomorrow.

navnavnav Dec 3, 2024
Maintainer

BTW I just tried building GDB 15.2 on my machine (Ubuntu 22.04), and it seems to work fine with XML support enabled.

These are the commands I ran to build (after switching to the gdb-15.2-release tag and creating a build dir):

../configure --target=avr --with-expat --with-libexpat-prefix=/usr/local/
make -j 6

That was enough to make it work for me.

frankE Dec 4, 2024
Author

Solved it. I had to manually delete the */config.cache files in the gdb source tree. A make clean didn't do it.

Answer selected by frankE

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[ERROR] Failed to write memory to target - GDB attempted to write to program memory via an "M" packet - this is not supported. #122

{{title}}

Replies: 2 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

Select a reply

[ERROR] Failed to write memory to target - GDB attempted to write to program memory via an "M" packet - this is not supported. #122

frankE Dec 3, 2024

Replies: 2 comments · 5 replies

navnavnav Dec 3, 2024 Maintainer

frankE Dec 3, 2024 Author

navnavnav Dec 3, 2024 Maintainer

frankE Dec 3, 2024 Author

navnavnav Dec 3, 2024 Maintainer

frankE Dec 4, 2024 Author

frankE
Dec 3, 2024

Replies: 2 comments 5 replies

navnavnav
Dec 3, 2024
Maintainer

frankE
Dec 3, 2024
Author

navnavnav Dec 3, 2024
Maintainer

frankE Dec 3, 2024
Author

navnavnav Dec 3, 2024
Maintainer

frankE Dec 4, 2024
Author