• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 495 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS6, TMS320F28069 - GPIO reg changes don't "stick"

Edward Averill
Genius 3100 points

Other Parts Discussed in Thread: TMS320F28069

Latest CCS6 updated this morning.  TMS320F28069 target being debugged. Win7 64-bit.

I'm debugging some GPIO-driven peripheral issues and need to bash the GPIOs directoy to see how the device responds.  Clicking on, and typing in, GPADAT causes the old number to magickally re-appear!  Bashing GPASET won't cause the corresponding GPIO bits to set, either.

Is there a limitation on what registers CCS6 can alter while the device is running?

All help appreciated!

Ed Averill

 

  • 0
    TI__Guru**** 171519 points

    Ed,

    One quick clarification: are you trying to modify the registers while the core is running? If so, that is not possible unless the core is halted or the option Halt the target before any debugger access is enabled (menu Tools --> Debugger Options --> Auto Run and Launch options).

    Regards,

    Rafael

  • 0 in reply to desouza
    Genius 3100 points

    I stop the core, make the change, but don't see the expected result.  This is an inherited project so it's possible the original engneer has misprogrammed a bunch of I/Os.. other registers change Just Fine.

    Back to debugging...

     

  • 0 in reply to Edward Averill
    TI__Guru**** 171519 points

    Ed,

    I would expect this if the referred GPIO pins/port is configured for input by mistake - in this case you would only be able to read back what is being fed to the pins. Keep in mind that CCS performs standard memory accesses to these memory mapped registers, but the results and functionality are completely dependent on the peripheral/device configuration.

    In this case, perhaps you will have some better luck at the C2000 forum itself - they are more knowledgeable about the peripherals themselves.

    Regards,

    Rafael

  • 0 in reply to desouza
    Genius 3100 points

    After a long while digging through the schematic and sitting w/ the hardware guy, looks like most of the GPIOs were mis-programmed.  NOW things are working as expected.

    Thanks for all the help!

    Ed Averill