Gdb server closes connection.

[Heron]

Please, I need help with this problem.

Initially I could do debugging without problems but after the last update (yesterday) of the MCUXpresso (ver 11.1.1_3241), when I try to do debugging I receive the following messages (see text at the end) and the gdb server closes the communication.

This happens the same with the frdm ke06, frdm k64 and frdm kl46 boards using "hello world" example.

I already checked the early posts related to breakpoints and I did what that they said, but without good results.

Any help or idea will be welcome. Thanks in advance.

Regards,

Luis

***********************************************************************************************

Pop up message: “Runtime error 216 at 03…..”

DEBUGGER CONSOLE

 “C:

xp\MCUXpressoIDE_11.1.1_3241\ide\plugins\com.nxp.mcuxpresso.tools.win32_11.1.0.202001081728            ools_in_rm-none-eabi-gdb.exe: warning: Couldn't determine a path for the index cache directory.

GNU gdb (GNU Tools for Arm Embedded Processors 8-2019-q3-update) 8.3.0.20190703-git

Copyright (C) 2019 Free Software Foundation, Inc.

License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software: you are free to change and redistribute it.

There is NO WARRANTY, to the extent permitted by law.

Type "show copying" and "show warranty" for details.

This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".

Type "show configuration" for configuration details.

For bug reporting instructions, please see:

<http://www.gnu.org/software/gdb/bugs/>.

Find the GDB manual and other documentation resources online at:

    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".

Type "apropos word" to search for commands related to "word".

monitor setexceptioncatching 2033

monitor selectcore 0

"monitor" command not supported by this target.

continue

The program is not being run.”

CONSOLE

“P&E Semihosting Console

 Connection closed by the GDB server._”

[snahmad]

I am getting below error. kindly help, cannot debug.

/mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-260_20210727_1627371386/src/gdb/gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 4064 bytes.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]

[snahmad]

I am getting time to time.

slow debug. how to increase RAM?

mnt/workspace/workspace/GCC-10-pipeline/jenkins-GCC-10-pipeline-260_20210727_1627371386/src/gdb/gdb/utils.c:671: internal-error: virtual memory exhausted: can't allocate 4064 bytes.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]

[frq03719]

Hello. I have the same error on a KE02 FRDM board. As this is meant to be an OpenSDA V1 board, can the solution proposed by Heron above works? 

[frq03719]

I actually went on the segger website, and looked for the FRDM KE02 binay Jlink code, and it exists for that board. 

Now, I can flash the board! 

[Heron]

I already solved the problem, with a quick and dirty solution. I put OpenSDA board as MSD and reprogrammed it as j-link OpenSDA and problem solved. It is not very elegant, I would have preferred to know how the P&E OpenSDA is corrected but there is no time to start fighting the tool that is supposed to save us time.

[cerma]

Hi All,

I have the same problem.
I use MCUxpresso 11.1.0_3209 and PEmicro MULTILINK Rev.D.
If I place the code for i.MX1052 in RAM or HyperFalsh, everything works properly. But if I place the code in QSPI I get the same error as above.
Can anyone advise me the final solution?

Thanks in advance.

Best regards,

Jaroslav

[Omar_Anguiano]

Hello Luis Espinal 

Are you using a specific debugger or are you using the OpenSDA on the board? If you are using any other debugger it is recommendable to update the device to the latest version.

If this isn't the case then I suggest you check chapter 10.10 "SEGGER Troubleshooting" of the MCUXpresso User guide https://www.nxp.com/docs/en/user-guide/MCUXpresso_IDE_User_Guide.pdf

Let me know if this is helpful, if you have more questions do not hesitate to ask me.

Best regards,

Omar

[Heron]

Hi, Omar.

Thaks for your support.

I’m using the OpenSDA on the board.

I’ve read the manual, chapter 10.10, but it’s for Segger debug troubleshooting, not for OpenSDA.

Regards,

Luis

De: Omar Anguiano

Enviado el: lunes, 23 de marzo de 2020 3:08 p. m.

Para: Luis Espinal <l.espinal@flextek-dev.com>

Asunto: You have been mentioned by Omar Anguiano in Re: Gdb server closes connection. in NXP Community

<https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg> NXP Community

You have been mentioned

by <https://community.nxp.com/people/nxf54944?et=notification.mention> Omar Anguiano in Re: Gdb server closes connection. in NXP Community - <https://community.nxp.com/message/1287517?commentID=1287517&et=notification.mention#comment-1287517> View Omar Anguiano's reference to you