• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 135 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.

LAUNCHXL-F280039C: GPIO GPAAMSEL analog bits change back to 1's

Genatco
Guru 55913 points
Part Number: LAUNCHXL-F280039C

Tool/software:

Hello,

Having issue with migration from x49c to x39c, user LEDS GPIO-20 / 21 analog mode disabled on both pins, set to digital mode. GPIO write was set 1 both user LED 4, 5 briefly turn on then refuse to toggle and seems to be the cause STOP fault trap. These user LEDS toggled on/off prior to migration. The odder part being the MCU goes into boot loops when removed from debug and runs up to the point of GPIO toggling of user LEDS never turn on just remain off. It seems the GPIO toggle of both GPIO 20 and 22 are causing STOP fault and GPAAMSEL bits to change from 0 to 1.

C2000 v5.04 driverlib x39c device. CCS v12.8

How to stop the register bits changing back to 1 (Analog) after GPIO toggle function is called?   Why does XDS110 ignore debug break points after it updated v32 firmware they only worked during the very first debug secession. Then no other debug secessions break points work. Even after closing, resetting MCU or set new break points, XDS110 still runs up to STOP skipping over all set break points. The debug settings are to restore existing break points on reentry.  

  • +1
    Guru 55913 points

    Issue mostly resolved was not GPIO the eSTOP rather ADCISR ADCC3 was needed not ADCC2. There are 3 ISR's for ADCC and migrating booster headers from x49c to x39c plus 3 different PWM drives, 3x CMPSSx MUX was a challenge.