NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

Talk:Pin Mux Utility for ARM MPU Processors

From Texas Instruments Wiki
Jump to: navigation, search
For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article Pin Mux Utility for ARM MPU Processors here.

Comments on Pin Mux Utility for ARM MPU Processors


Ranye said ...

I really appreciate this utility - it saves A LOT of time trying to get the pins setup correctly. I would like to make a request, can you add a column for user comments after the mode 7 column? I would like this comment appended to the comment you are already adding in the header. Adding this column will help me keep track of board specific settings of the pins.

Thanks!!

--Ranye 11:43, 10 September 2010 (CDT)

DrDrizzle said ...

Is the source code for the PinMux utility itself available somewhere?

--DrDrizzle 13:42, 12 May 2012 (CDT)

Rmaruschock said ...

I agree with Ranye. Since GPIO pins typically get a specific function, it would be nice to have a comment column or to be able to have alternate text to GPIO[#] in the utility so that the headers do not need to be edited after they are created to match what the GPIO signals are actually used for.

--Rmaruschock 14:57, 29 May 2012 (CDT)

Simonkbrown said ...

Ok, it's a great utility, but when drawing up the circuit board having done pin muxing, it would be really nice to be able to PRINT the result. The header files are completely useless to work out which mode you had which pins configured in, because PINCTRL237 in MD2 doesn't mean much to the average user.

--Simonkbrown 17:50, 13 August 2012 (CDT)

Pondhockeyguy said ...

It should also be noted that with a simple macro redefine, the files generated by the PinMux utility can directly used as StarterWare platform files.

1) Create pin mux design 2) Import mux.h and pinmux.h files into the platform directory your code is using. 3) Insert the following macro redefine into a new header file called by your code

//Macro redefine to allow starterware to directly use mux.h and pinmux.h files in the TI starterware platform build files

  1. ifdef MUX_VAL //Redefine MUX_VAL defined by mux.h file (as generated by PINMUX utility

// for desired hardware configuration) to map to starterware calls

  1. undef MUX_VAL
  2. define MUX_VAL(OFFSET,VALUE)\
   HWREG( SOC_CONTROL_REGS + (OFFSET)) = (VALUE);
  1. endif

--Pondhockeyguy 10:47, 22 January 2013 (CST)