GDB crashes using KDS3 KSDK1.2 and MQX on FRDM-22F

[ivanvernot]

Hello,

I just installed KDS 3 and KSDK1.2 and tried to compile and run the 'hello' mqx  example from C:\Freescale\KSDK_1.2.0\rtos\mqx\mqx\examples\hello\build\kds\hello_frdmk22f

The build was ok (I rebuilt all libraries etc) but when launching a debug session (usinf FRMS22F and mdbed OpenSDA (221)

the arm-none-eabi-gdb application crashes.

FWFW this is the console output

Warning: the current language does not match this frame.

/home/build/work/GCC-4-8-build/src/gdb/gdb/linespec.c:2445: internal-error: decode_line_full: Assertion `state->canonical_names[i].suffix != NULL' failed.

A problem internal to GDB has been detected,

further debugging may prove unreliable.

Quit this debugging session? (y or n) [answered Y; input not from terminal]

/home/build/work/GCC-4-8-build/src/gdb/gdb/linespec.c:2445: internal-error: decode_line_full: Assertion `state->canonical_names[i].suffix != NULL' failed.

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]

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

Any ideas what is going on.

FWIW when I build and try to debug  the demon at in C:\Freescale\KSDK_1.2.0\examples\frdmk22f\demo_apps\hello_world\kds (ie not MQX) it runs and debug fine.

Any Ideas what might be happening. I am an

I am an experienced dev new to Freescale KDS +KDSK +MSQ.its steep learning curve, especially n the

Its steep learning curve, especially when the tools seem to be evolring rapidly and the on-line docs seem unable to keep pace.

Thanks and Regards

Ivan Vernot

///realtimedesigns.com.au

[DavidS]

Hi Ivan,

Did a re-boot help?

Did you select the GDB OpenOCD Debugging->hello_frdmk22f int flash debug cmsisdap project to debug?

I just loaded the example and was able to successfully have hello world work for me.

Attached is my MBED firmware ZIPed.

Regards,

David

[ivanvernot]

Hello David,

Thank you so much for checking this.

(Multiple) reboots made no difference

Your MBED firmware does work! Interesting. The firmware I'm running is for here

https://developer.mbed.org/handbook/Firmware-FRDM-K22F

It is supposed to be the latest., I did not see your version

Cab I ask where you got your version from and do you know of its 'geneology', I did not see your version

Would you be able to try the version from the mbed site and see it works for you.

(Here is the direct link)

https://developer.mbed.org/media/uploads/sam_grove/0221_k20dx128_k22f_0x8000.bin

If not perhaps they have an issue they are unaware of.

(Then again - debugging is work fine if I build the non-mqx version

in C:\Freescale\KSDK_1.2.0\examples\frdmk22f\demo_apps\hello_world\kds )

Thanks again.

Ivan

[DavidS]

Hi Ivan,

The firmware I uploaded was from a training class I did last year so just happened to have it.  Not 100% sure where I got it.

The firmware from MBED web site works for me too.

I can successfully use PEMicro, MBED, and JLink firmware on my Freedom board.

My FRDM-K22F has Rev D on the back side.  Is that what yours is?  Wondering you just have an older board.

But if the firmware I uploaded works for you keep it.

Attached is my PEMicro OpenSDA firmware too.

Note below picture that sometimes you need to make sure the correct debugger settings have been set.

Regards,

David

[ivanvernot]

David,

I hope I do not offend by addressing you directly in a open forum.

I need to find someone experienced with the Freescale tools to help us come up-to-speed quickly by creating a working project with several tasks that sends and receives via uarts, SPI and I2C.  (I will provide details later, but it will be just a 'demo' project)

This will be used as a basis for out 'real project'.

I have spent a couple of weeks battling with issues that I am sure are mainly because I don't yet know how everythig fits togetther.

This Freescale stuff has really kicked my butt!

I am not sure what scope there is for anyone to do this as part of their 'work-hours' role, or for free in these forums, but as I have already spent a lot of time on this without result, I am prepared to pay for your time if you are unable to do this during 'work-hours'.

If you are able to help out (or know someone that can) please let me know here of prefereably directly at ivanv@realtimedesigns.com.au.

Thanks and Reagards

Ivan Vernot

[DavidS]

Hi Ivan,

Not offended and honored to be asked but I am not the right resource for this.

We have many examples of using UART/SPI/I2C in the KSDK with and without RTOS.

People that you could reach out to include:

Design Services – Embedded Access

http://softwareforhire.com/

As well as Freescale Design Services:

Professional Engineering Services|Freescale

Others may contact you as well.

Regards,

David

[ivanvernot]

Thanks David,

I'll contact those you suggested.

In the meantime if anyone else reading this feels that are able to help out (or know someone that can) please let me know at ivanv@realtimedesigns.com.au.

[BlackNight · Accepted solution]

Hi Ivan,

Could it be that you have imported the projects *with* the breakpoints? I think the problem you face is an existing issue in gdb dealign with breakpoints (which might not point to valid locations).

Try to delete all breakpoints from your breakpoints view. This should fix it.

I hope this helps,

Erich

[zwilcox]

This helped me :smileyhappy: Thanks!

[ve3id]

Thanks, Eric, that worked for me!  However the bug occurred when I was in the zilionth iteration of a debug session!

[calvinjohnson-b]

It helped me too. And later on, once the bebugger started running, I was able to insert breakpoints.

[ivanvernot]

Thank you Eric,

That was it! Brillant.

I hope this saves someone else some pain

Regards

Ivan

[ivadorazinova]

Hello Ivan,

I moved your thread to Kinetis Design Studio, because GDB crashes are not problem of KSDK.

It could be the reason why you have not gotten answer so quickly.

For the next time and for better visibility of your threads is better to put your issue to appropriate group.

Thank you.

Have a nice day,

Best Regards,

Iva