• AVR Freaks

Helpful ReplyHot!ICD4 and PIC32MZ2064DAG169 deathly slow

Author
jandle
Starting Member
  • Total Posts : 28
  • Reward points : 0
  • Joined: 2017/05/27 06:57:30
  • Location: 0
  • Status: offline
2020/10/14 14:46:02 (permalink)
5 (1)

ICD4 and PIC32MZ2064DAG169 deathly slow

C32 v. 2.30
MPLab X 5.25
Harmony framework 2.06.
FreeRTOS 10.0.1
 
stepping code is taking 20-60 seconds per step.  I literally forget what I was doing while debugging.
I installed the latest ICD4 packs, no help.
 
I never recall it being so slow, so *maybe* I have an unhandled interrupt firing over and over?
 
 
#1
ric
Super Member
  • Total Posts : 28975
  • Reward points : 0
  • Joined: 2003/11/07 12:41:26
  • Location: Australia, Melbourne
  • Status: online
Re: ICD4 and PIC32MZ2064DAG169 deathly slow 2020/10/14 15:43:50 (permalink) ☄ Helpfulby jandle 2020/10/15 11:49:59
3.5 (2)
Maybe you have a watch window open, that is refreshing its contents between every step.
 

I also post at: PicForum
Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
NEW USERS: Posting images, links and code - workaround for restrictions.
To get a useful answer, always state which PIC you are using!
#2
jandle
Starting Member
  • Total Posts : 28
  • Reward points : 0
  • Joined: 2017/05/27 06:57:30
  • Location: 0
  • Status: offline
Re: ICD4 and PIC32MZ2064DAG169 deathly slow 2020/10/15 11:54:07 (permalink)
0
ric
Maybe you have a watch window open, that is refreshing its contents between every step.
 


Well it is certainly MUCH slower with even call stack window and a new level of slow with a significant watch window, so that is very helpful.  Still, even coffee deprived, it is slow with none of these open.  It seems to cook right along just running between breakpoints and only stepping seems labored, so I might be less likely to blame an errant interrupt. 
 
I do have a RealICE on it's way next week just so i can see FreeRTOS plugin.  If it does not have the issue then i will circle back on the ICD4 specifically, or at least some bad setting in the project.
#3
MHS
Super Member
  • Total Posts : 371
  • Reward points : 0
  • Joined: 2010/04/23 10:05:39
  • Location: 0
  • Status: offline
Re: ICD4 and PIC32MZ2064DAG169 deathly slow 2020/10/15 13:11:51 (permalink)
1 (1)
Have you tried upgrading to to MPLAB 5.40 ?
#4
jandle
Starting Member
  • Total Posts : 28
  • Reward points : 0
  • Joined: 2017/05/27 06:57:30
  • Location: 0
  • Status: offline
Re: ICD4 and PIC32MZ2064DAG169 deathly slow 2020/10/15 13:16:06 (permalink)
0
MHS
Have you tried upgrading to to MPLAB 5.40 ?


I try not to change my build system mid project but if it might help, I suppose I should.
#5
ric
Super Member
  • Total Posts : 28975
  • Reward points : 0
  • Joined: 2003/11/07 12:41:26
  • Location: Australia, Melbourne
  • Status: online
Re: ICD4 and PIC32MZ2064DAG169 deathly slow 2020/10/15 14:48:10 (permalink)
0
Note, if you let it install to the default location, it does NOT remove your previous install of MPLABX.
So, you can try it without losing the old one.
 

I also post at: PicForum
Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
NEW USERS: Posting images, links and code - workaround for restrictions.
To get a useful answer, always state which PIC you are using!
#6
jandle
Starting Member
  • Total Posts : 28
  • Reward points : 0
  • Joined: 2017/05/27 06:57:30
  • Location: 0
  • Status: offline
Re: ICD4 and PIC32MZ2064DAG169 deathly slow 2020/10/21 09:39:01 (permalink)
0
I received the RealICE that I scrounged and for a brief moment it seemed faster even with watch windows open, but after  couple rounds back and forth I see no real difference.  I guess on the debugger I choose between RTOS viewer and number of breakpoints.  That does say either I have cable issues (same custom cable for both) or MPLabX issues. 
 
Are cable issues pass/fail or do these debuggers throttle bandwidth and or retry numerous times to make things work?  IE can I rule out the custom cable and focus on the software?
#7
NKurzman
A Guy on the Net
  • Total Posts : 19034
  • Reward points : 0
  • Joined: 2008/01/16 19:33:48
  • Location: 0
  • Status: offline
Re: ICD4 and PIC32MZ2064DAG169 deathly slow 2020/10/21 11:53:02 (permalink)
4 (1)
I did Not Find much of a Speed Difference Between the RealICE and ICD4.
Note: they Discontinued the RealICE and Now the ICD4 is the Top on the line Debugger.
#8
jandle
Starting Member
  • Total Posts : 28
  • Reward points : 0
  • Joined: 2017/05/27 06:57:30
  • Location: 0
  • Status: offline
Re: ICD4 and PIC32MZ2064DAG169 deathly slow 2020/10/21 12:55:29 (permalink)
0
NKurzman
I did Not Find much of a Speed Difference Between the RealICE and ICD4.
Note: they Discontinued the RealICE and Now the ICD4 is the Top on the line Debugger.


I did not expect any but:
I upgraded to ICD4 and gave away my RealICE years ago.
On this project it was very sluggish
It is incompatible with FreeRTOS viewer (still)
I obtained the RealIce on EBay to address RTOS and to see if the ICD4 was root cause of sluggishness.
#9
NKurzman
A Guy on the Net
  • Total Posts : 19034
  • Reward points : 0
  • Joined: 2008/01/16 19:33:48
  • Location: 0
  • Status: offline
Re: ICD4 and PIC32MZ2064DAG169 deathly slow 2020/10/21 13:28:53 (permalink)
0
What happens if you close all the viewing windows.
I am not having any issues with a PIC32MZ.  Well not no issues, But no Speed Issues.
#10
Jump to:
© 2020 APG vNext Commercial Version 4.5