• AVR Freaks

Hot!ATTINY817 MCC Pin Module Pull Ups Arbitrarily Turned Off

Author
floatingpoint
Super Member
  • Total Posts : 207
  • Reward points : 0
  • Joined: 2008/12/01 15:52:03
  • Location: below Equator
  • Status: offline
2020/07/27 23:33:57 (permalink)
0

ATTINY817 MCC Pin Module Pull Ups Arbitrarily Turned Off

ATTINY 817
Win10
MPLABX V5.35
MCC V3.95
Setting Pax or PCx inputs with pull-ups on pin module table works first time.
Subsequent changes using MCC to a different peripheral generates code.
This new code has respective PAx and PCx pin pull-ups turned off despite no change to pin module table.
Curiously it doesn't appear to be an issue with port B...
Edit  - Just found some Port B pull-ups have been turned off as well.
 
To keep all pull-ups correctly set I need to toggle each pull up button prior to code re-generation for any reason.
Is this a known issue?
Sure does throw the cat amongst the pigeons when trying to test a different peripheral/ function.
 
FP
 
post edited by floatingpoint - 2020/07/28 14:16:06
#1

4 Replies Related Threads

    du00000001
    Just Some Member
    • Total Posts : 3946
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: ATTINY817 MCC Pin Module Pull Ups Arbitrarily Turned Off 2020/07/28 03:20:20 (permalink)
    2 (1)
    Might be worth to file a support case.
     
    See  https://microchipsupport....e/How-to-submit-a-case

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #2
    floatingpoint
    Super Member
    • Total Posts : 207
    • Reward points : 0
    • Joined: 2008/12/01 15:52:03
    • Location: below Equator
    • Status: offline
    Re: ATTINY817 MCC Pin Module Pull Ups Arbitrarily Turned Off 2020/07/28 14:04:20 (permalink)
    0
    Thanks, I did log with support.
     
    While I'm on my soapbox.
    Is there a reason that the widely used convention of alphabetical order is not used by MCC for "pin_manager.c" code generation?
    Doing a git diff on 2 successive "pin_manager.c" files results in unusable output.
     
    Alphabetical order is good enough for the data sheet and most other publications and references.
     
    FP
    post edited by floatingpoint - 2020/07/28 14:30:37
    #3
    du00000001
    Just Some Member
    • Total Posts : 3946
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: ATTINY817 MCC Pin Module Pull Ups Arbitrarily Turned Off 2020/07/28 18:56:14 (permalink)
    0
    It's certainly not only the order in pin_manager.c
    From my observations, I assume the whole code generation follows the order of an internal "file". This order seems to be affected by every change, most likely new/changed elements are appended while the previous versiins might be just marked as invalid (and maybe eliminated when dumping the configuration).
    No sorting at all.

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #4
    floatingpoint
    Super Member
    • Total Posts : 207
    • Reward points : 0
    • Joined: 2008/12/01 15:52:03
    • Location: below Equator
    • Status: offline
    Re: ATTINY817 MCC Pin Module Pull Ups Arbitrarily Turned Off 2020/08/14 15:11:33 (permalink)
    0
    Just a wrap up for anyone experiencing this.
    Support can reproduce pull-ups arbitrarily being turned off using AVR library V1.x So beware that changing anything with MCC and AVR libraries V1.x when pull-ups are set may reset the pull-ups even though you haven't modified any pin mapping or tables.
    You need to toggle pull-up radio button off then on to re-assert pull-up prior to generating new MCC code.
     
    They were not able to reproduce it using AVR libraries V2.x
     
    A further word of caution, if you have a project already using AVR library V1.x as I do, upgrading the AVR library to V2.x has the unwanted effect of deleting all of your assigned MCC modules and settings that go with them. (Back to the data sheet if you go down this path) Support advise that this is intended to 'clean' the project prior to using V2.x library....
     
    FP
    #5
    Jump to:
    © 2020 APG vNext Commercial Version 4.5