Registers window works for core peripherals, but shows 0xfefefefe for all others

Comments

4 comments

  • Avatar
    Jon Elliott

    Hi Mike,

    Check that the clocks for each of the peripherals in question have been enabled.

    Regards,

    Jon

    0
    Comment actions Permalink
  • Avatar
    Michael Root

    Yes, the clocks are enabled, and I'm using the peripherals in question successfully.

    0
    Comment actions Permalink
  • Avatar
    Michael Root

    I figured it out.  

     

    Changed 'Restrict Memory Accesses' in my Target properties to 'No' and now I can view Registers.

     

    Thanks.

    0
    Comment actions Permalink
  • Avatar
    Hani Akeila

    I am using CrossWorks for MAXQ30 core. I am evaluating the CrossWorks (trial) and tried a simple GPIO read/write code. I am running MAXQ30 core simulator as a target.

    I have two issues while I am debugging the simulator:

    1) if I download the built code into the simulator and started the debugger, the debugger goes to infinite running state, in which I cannot debug through my code lines.

    2) If I didn't download the code into the simulator and run my debugger, I can go though the code lines. But the GPIO registers are not updated at all on the register view window. I tried to look at the properties in the register view window, but nothing is helpful

     

    Any suggestion?

     

    I attached the main.c code

    Kind Regards,

    Hani Akeila

    0
    Comment actions Permalink

Please sign in to leave a comment.