Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
10 years, 9 months ago.
Debug not working, message "Ignoring packet error, continuing..." keeps showing
Hello,
I've done all the configuration and it builds to the mbed and the code is ok, every thing is working. The only problem is, when i try to debug it get stuck. I put a breakppint at the beggining of the main and in the main lood but i never reaches none of them. The messages that are printed in the console are:
Ignoring packet error, continuing... warning: unrecognized item "timeout" in "qSupported" response Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing...
They keep showing for like 3 or 4 minutes, than it stops. Am i missing something??
Great tutorial by the way, helped me a lot!!! Thanks!!!!
Regards,
José Claudio
Question relating to:
4 Answers
10 years, 8 months ago.
I suspect that you need to update the firmware on the mbed device to support the debug monitor. Download http://mbed.org/media/uploads/simon/mbedmicrocontroller_21164.if. Copy this file to your mbed device and then power cycle it. This will update the firmware on the interface chip so that the debug monitor can be used for debugging the device.
I had forgotten that step somehow from the Cookbook page. Sorry about that. I have added it.
Hope that helps,
Adam
It's working now! Thank you Adam. I would like to know which file should I use to return to the previous state of the mbed. I searched and found nothing related to this, maybe I searched wrong.
Regards, José Claudio
posted by 13 Aug 2013There is really no reason to return to the previous interface firmware. The version I pointed you to is just a newer and more capable version of the firmware. One of those capabilities is the ability for me to temporarily disable the JTAG usage of the interface chip so that my debug monitor will work. When you aren't using the debugger, you are just getting a more capable interface firmware. You can go here to download the latest version of the interface firmware for your device which is newer than the one I pointed you to but I haven't tested it as much.
posted by 13 Aug 2013Update: I recommend just sticking with the 21164 firmware that I pointed you to originally. Especially if you use OS X as I do. I upgraded to the latest firmware earlier today (just before I wrote my previous comment) and my Mac ended up with hung processes multiple times as I was trying to use the virtual serial port. Reverting back to 21164 fixed the problem. I have been using 21164 for over a year on Windows, Ubuntu, and OS X with no issues.
posted by 14 Aug 2013
10 years, 3 months ago.
Hi all,
[EDIT] N.v.m it already works [/EDIT]
I'm encountering the same problem, although i do run the 21164 firmware. Any suggestions? I do have to mention, that i had to leave out GCC4MBED_TYPE=Debug of the Incremental Build field, for it to compile correct. I'm guessing this has something to do with it?
Regards, Boris
10 years, 7 months ago.
May I slightly hijack this thread a bit? for what device is the 21164 firmware? can i use it with the frdm-kl25z? and has anyone tried that. I am trying to use arm-none-eabi-gdb with a project generated using the python SDK, have this same problem.