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.

TPS65982: Application customization tool version 2.15 has GPIO Event issues with 2.15 based projects

Expert 1015 points
Part Number: TPS65982

The GPIO Event map register in version 2.15 (I have rc2 - the latest I could get) has a problem with the GPIO event settings when a 2.15 pjt is loaded.

Under the GPIO Event Map group (register 0x5c), there is a Mapped Event pulldown. This allows you to select an event that will happen for that GPIO, either an output or an input.

In version 2.15 you cannot set the MappedEvent to 'DISABLED' once it has been changed. It will always change to 'Output Enabled Without Event', another different option. I can get back to Disable if I load a 2.14 project into the 2.15 tool. I'm not sure what is happening here.
The HostInterface manual doesn't explain this register, so I can't find out what the bits should be for Disabled, but I suspect they are supposed to be 0s, and they aren't.

I downloaded the AppConfig tool again and reinstalled it, but it still has this problem.

  • Hi WST,

    I wanted to let you know that I was able to recreate your issue. I am currently looking into this. Like you suspected the bits for 'Disabled'  SHOULD be 0s and the bits for 'Output Enabled Without Event' SHOULD be equal to 1d. I will look to the FW/app tool to confirm this. I will also try to fix the issue that you are experiencing so that you are able to successfully implement the  'Disabled' option in the Mapped Event drop-down window.

    Thanks 

  • Hi WST,

    Sorry for late reply, this issue is being fixed and will be released in the next latest FW. Were you able to do a work around for seeing 'DISABLED'?

    Thanks
  • Jeff,
    Yes, as a temporary measure I went back to 2.10 based images that don't have this problem.
    However, I found a workaround with the 2.15 images.
    It looks like the 'Load App Config Set 1' I was using as a mapped event for GPIO#0 can only be mapped to one GPIO.
    So, any GPIO that was 'stuck' at 'Output Enable without Event' I could map to 'L-A-C-Set1' temporarily. Then when I mapped GPIO#0 back to 'L-A-C-Set1' the other previously mapped event would reset to Disabled. In this way, I could set any GPIO back to Disabled.
    Thanks,
    WST