Hot!Problems debug PIC32MZ

Author
Sens
New Member
  • Total Posts : 3
  • Reward points : 0
  • Joined: 2018/02/26 02:59:54
  • Location: 0
  • Status: offline
2018/02/27 01:55:04 (permalink)
0

Problems debug PIC32MZ

Hello,
 
I've designed my own board with PIC32MZ with internal DDR2 Ram.
I'm using a GLCD 480x272.
I can debug it, but when the PC reaches the line 529 of drv_gfx_glcd_static.c (I’ve attached a screenshot) the green arrow disappear and the ICD3 loses communication, then I have to disconnect and connect again the ICD3. This happen at the moment of clear the internal frame buffer pointer. At this point I don't have idea what is going on and what else to check. I've purchased the PIC32MZ demo and I can program and debug it without problems with a similar code.
 
Many thanks.
 

Attached Image(s)

#1

5 Replies Related Threads

    Autofahrn
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2018/02/15 21:14:06
    • Location: 0
    • Status: offline
    Re: Problems debug PIC32MZ 2018/03/02 05:33:38 (permalink)
    5 (1)
    If the screen buffer is in internal SDRAM, did you correctly initialize that memory controller and enabled the DDR clock in clock manager?
    I'm running the MZ on a custom board with attached LCD as well, so maybe I could help.
    #2
    Sens
    New Member
    • Total Posts : 3
    • Reward points : 0
    • Joined: 2018/02/26 02:59:54
    • Location: 0
    • Status: offline
    Re: Problems debug PIC32MZ 2018/03/02 07:07:41 (permalink)
    0
    I don't know if I've initialized the memory controller correcly, I suppose that this is done by Mplab Harmony: in graphics stack I see Frame Buffer Memory Location DDR2.
    I've enabled the DDR clock running to 200MHz.
     
    #3
    friesen
    Super Member
    • Total Posts : 1953
    • Reward points : 0
    • Joined: 2008/05/08 05:23:35
    • Location: Indiana, USA
    • Status: offline
    Re: Problems debug PIC32MZ 2018/03/02 08:51:13 (permalink)
    5 (1)
    Not sure if this helps, I have learned that losing communication like that is typically what it the MZ with ddr does when it attempts to access memory that isn't set up or doesn't exist, like perhaps trying to access a greater address than exists in ddr or xip, or accessing ddr or other memory space that isn't set up, etc..

    Erik Friesen
    #4
    Autofahrn
    New Member
    • Total Posts : 5
    • Reward points : 0
    • Joined: 2018/02/15 21:14:06
    • Location: 0
    • Status: offline
    Re: Problems debug PIC32MZ 2018/03/08 17:03:07 (permalink)
    5 (1)
    Did you enable the Memory system service to use internal DDR2 which effectively configures the DDR controller with proper parameters?
    I've personally had to learn that the timing parameters for the internal DDR2 RAM specified in the data sheet (Table 4-5) do not really work, using the Harmony defaults when selecting internal DDR seems to work.
    #5
    Sens
    New Member
    • Total Posts : 3
    • Reward points : 0
    • Joined: 2018/02/26 02:59:54
    • Location: 0
    • Status: offline
    Re: Problems debug PIC32MZ 2018/03/12 01:36:50 (permalink)
    0
    Hello,
     
    Yes, I forgot enable the Memory system service to use the DDR2, I thought that when the internal buffer location is in DDR2 harmony enables the initialization required. Now doesn’t turn on sometimes I still working on it. Thank you all.
    #6
    Jump to:
    © 2018 APG vNext Commercial Version 4.5