• AVR Freaks

Can I use MPLAB-X to view the internal SDRAM 32MB memory (for the PIC32MZ1025DAG169)

Author
cbeif
Starting Member
  • Total Posts : 53
  • Reward points : 0
  • Joined: 2012/05/09 14:28:30
  • Location: 0
  • Status: offline
2019/07/10 11:43:47 (permalink)
0

Can I use MPLAB-X to view the internal SDRAM 32MB memory (for the PIC32MZ1025DAG169)

I am having alot of trouble writing and reading to the SDRAM.
Is there a way to use the debugger to see what's inside the internal DDR2 SDRAM?
 
I don't see any of the "Target Memory Views" which contain the address of 0x88000000.
#1

3 Replies Related Threads

    crennolet
    Super Member
    • Total Posts : 128
    • Reward points : 0
    • Joined: 2012/03/15 09:51:58
    • Location: 0
    • Status: offline
    Re: Can I use MPLAB-X to view the internal SDRAM 32MB memory (for the PIC32MZ1025DAG169) 2019/07/11 10:15:40 (permalink)
    0
    OK, I'll bite.
    Are you sure you have the part right? The specs sheet for the part you say you have says "256K" for internal static ram.
    #2
    jdeguire
    Super Member
    • Total Posts : 459
    • Reward points : 0
    • Joined: 2012/01/13 07:48:44
    • Location: United States
    • Status: offline
    Re: Can I use MPLAB-X to view the internal SDRAM 32MB memory (for the PIC32MZ1025DAG169) 2019/07/11 10:29:35 (permalink)
    +1 (1)
    Hmmm...the webpage for your part (https://www.microchip.com/wwwproducts/en/PIC32MZ1025DAG169) is recommending using the PIC32MZ1025DAR169 instead and no longer indicates that your part has internal DDR2 memory (though the datasheet says it does).  Perhaps the early parts are flaky or defective in some way.
    #3
    cbeif
    Starting Member
    • Total Posts : 53
    • Reward points : 0
    • Joined: 2012/05/09 14:28:30
    • Location: 0
    • Status: offline
    Re: Can I use MPLAB-X to view the internal SDRAM 32MB memory (for the PIC32MZ1025DAG169) 2019/07/11 11:21:07 (permalink)
    0
    Ahh rats, I have been struggling for about 3 weeks to get the internal SDRAM to work,
    I guess I now know why. (I wish there was a reason given for the obsolescence)
    #4
    Jump to:
    © 2019 APG vNext Commercial Version 4.5