Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MSP432 pin mapping is wrong for A9 #9

Closed
robertinant opened this issue Aug 29, 2016 · 7 comments
Closed

MSP432 pin mapping is wrong for A9 #9

robertinant opened this issue Aug 29, 2016 · 7 comments

Comments

@robertinant
Copy link
Member

From @fmilburn3 on May 5, 2016 18:48

See this thread: http://forum.43oh.com/topic/9614-msp-432-analog-pin-9-mapped-to-analog-pin-8/

A9 is mapped to pin 27 instead of pin 26 on the MSP432.

Copied from original issue: energia/Energia#879

@robertinant
Copy link
Member Author

From @rei-vilo on May 5, 2016 19:8

Is it

  • the pins map

image

  • or the link between MCU pins and LaunchPad pins defined in /Applications/Energia.app/Contents/Resources/Java/hardware/emt/ti/runtime/wiring/msp432/variants/MSP_EXP432P401R/pins_energia.h?

@robertinant
Copy link
Member Author

From @fmilburn3 on May 5, 2016 20:25

The problem is in pins_energia.h - in the following line:

static const uint8_t A9 = 27;

It should read:

static const uint8_t A9 = 26; // change this from 27 to 26

@robertinant
Copy link
Member Author

From @rei-vilo on May 5, 2016 20:36

I can't pull the fix because this specific file comes form emt @ a350116 and I don't have access to it.

On branch issue_879
Your branch is up-to-date with 'origin/issue_879'.
Changes not staged for commit:
modified: emt (modified content)

no changes added to commit
(1)

@robertinant
Copy link
Member Author

@robertinant
Copy link
Member Author

From @rei-vilo on May 5, 2016 20:52

See Fix for A9 on MSP432 #1 and pull-request Fix for A9 on MSP432 #2.

Only @robertinant can commit it.

@robertinant
Copy link
Member Author

From @rei-vilo on May 5, 2016 20:53

@fmilburn3 Thank you so much for noticing the bugs and providing the details!

@robertinant
Copy link
Member Author

This has been fixed and will be made available in the next release due this week

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant