Debug mode keeps hangs

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Debug mode keeps hangs

2,864 Views
ping1
Contributor V

Dear all

I am using latest v24.12 IDE and J-Link Ultra+ debugger, recently moved to freeRTOS, try to debug and it keeps says "Not Responding" when I try to suspend it and exit the debug mode, sometimes it says something like suspend times out, and exit too. I am not sure this is to do with freeRTOS introduction or new IDE, these two things are all new to me.

Or am I missing something?

Thank you for your attention, anyone has similar issue? any suggestions please?

Ping

0 Kudos
Reply
10 Replies

2,860 Views
ping1
Contributor V
Further, clicked Suspect button and ended up Terminated.
0 Kudos
Reply

2,841 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @ping1 ,

 

Which example are you playing with? Is it some FreeRTOS demo out of the SDK? Please kindly clarify.  Actually I have experienced similar issue when I force the application jumping to an area without any code there.

 

Have a great day,
Kan


-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

 

0 Kudos
Reply

2,832 Views
ping1
Contributor V

Thanks for reply!

I am using my own firmware and board, the product is on market already and currently change it to be freeRTOS based.

It is earlier and quick to debug on non-OS based code. but also IDE version is changed too. So I am not sure what really causes this.

Regards!

Ping

0 Kudos
Reply

2,830 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @ping1 ,

 

Have you debug any SDK FreeTOS demo with the current IDE on your own board? If no issue happened, the root cause would not be on IDE side. 

 

Have a great day,
Kan


-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos
Reply

2,828 Views
ping1
Contributor V

Hi, Kan

Thanks for your reply, the issue is intermittent, and hard to find the root cause, it is probably down to my code, I just want to make sure there is no additional setting in debug side when using freeRTOS.

Regards!

Ping

0 Kudos
Reply

2,810 Views
ping1
Contributor V

Hi, Kan_Li

I found I lost debug communication when my code is calling LOCK_TCPIP_CORE() & UNLOCK_TCPIP_CORE() function. if I don't add these pair, it give me message "Function called without call locking" and hangs forever. when I add this pair, it seems executed through, but I lost debug communication afterwards, is this expected? any explanation  for this behaviour? or just a coincide?

Regards!

Ping

 

0 Kudos
Reply

2,790 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @ping1 ,

 

Did you use a console other than UART? From the source code, LOCK_TCPIP_CORE() & UNLOCK_TCPIP_CORE() function has nothing related with the UART. I think maybe you can try to debug some FreeRTOS LWIP demo out of SDK on your own board, if the problem is still there, please check your board design, and if not, please check your code implementation.

 

Hope that makes sense,

 

Have a great day,
Kan


-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos
Reply

2,787 Views
ping1
Contributor V

Hi, Kan_Li

Thanks for reply.

I don't use console Uart for debug if that is what you mean, I use J-Link Ultra on my target board, I don't understand how my debug issue is related to Uart, could you explain please? I do use a few UART on communication though.

Regards!

Ping

0 Kudos
Reply

2,782 Views
Kan_Li
NXP TechSupport
NXP TechSupport

Hi @ping1 ,

 

Thanks for the clarification! I just tried to debug lwip_mqtt_freertos demo on RT1050EVKB, the debug is fine as shown below.

Kan_Li_0-1744090577919.png

Have you ever try such demo on your own board?  was the problem still there? Please kindly clarify.

 

Have a great day,
Kan


-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

 

0 Kudos
Reply

2,767 Views
ping1
Contributor V

Hi, Kan_Li

My project is started from the mqtt demo, I tried twice to debug the earlier version, sometimes it is ok, sometimes not. The issue is intermittent, probably to do with my later code, which I am no sure, hence ask for help.

BTW, have you tried to debug with J-Link, it seems much harder than using LinkServer, it takes long time to jump to main sometimes, and sometimes exit the debug mode without a reason and when suspect button is clicked, it takes ages to stop.

Anyway, if you don't know any obvious reason for this, then it is probably no solution, I will have to battle on with it, thanks for your help.

Regards!

Ping

 

0 Kudos
Reply