PinMux Utility for DM816x outputs errors

Tim:

The purpose of the DAT file is to save your work (the current state of the GUI).  When this file is read into the tool

the state of the GUI is restored (File -> Load -> Design).

The output file is correct.  It is interpreted this way:

Pad = This line defines one pad of the die

1 CYG AL1 - = There is 1 pkg type (CYG).  The top ball location is AL1.  There is no top ball.

safe_mode = The mode 0 signal name for the ball.

4 NotSelected Selected NotSelected Reserved = States of the 4 mux mode cells.  Mode 1 is selected.

1 2 = 1 parameter value follows.  Value is 2 which corresponds to pullup disabled.

Regards,

Michael T

PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question.  Thanks!

Michael,

I still seems broken to me. 

In the GUI I have VOUT[1]_CLK selected for PAD AT7, but the .dat file s

Pad 1 CYG AT7 - safe_mode 4 NotSelected Selected NotSelected Reserved 1 2

However, in the GUI I have VIN[0]A_CLK select for PAD AR14 and I get the expected:

Pad 1 CYG AR14 - VIN[0]A_CLK 4 Selected Reserved Reserved Reserved 1 0

So it works in one case but not the other.

Tim.

Tim:

The DAT file is not really meant to be a file for the user to use as his "results" from using the tool.

It is just in a format that allows the state of the GUI to be saved and restored.

Pad 1 CYG AT7 - safe_mode 4 NotSelected Selected NotSelected Reserved 1 2

Is actually correct.

safe_mode = Mode 0 signal name

NotSelected Selected NotSelected Reserved are the states of the 4 GUI cells.

Which means the mode 1 is selected = VOUT[1]_CLK

As long as you can do File -> Save -> Design and File -> Load -> Design

and the GUI gets restored correctly, it is working correctly.

Regards,

Michael T

PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question.  Thanks!

Tim:

Now I understand your point.  The purpose of the first part of the output is to identify which device ball is represented

by the text on this line.  So it shows the ball ids for every package and it shows the "Mode 0 signal name" which is

safe_mode for this ball.  It does not mean safe_mode is selected by the GUI.

Pad 1 CYG AT7 - safe_mode

This way the lines in the DAT file can be in any order.  The tool reads each line and uses the ball ids and Mode 0 Signal Name to

associate the data with the correct device ball.

Regards,

Michael T

Michael,

Thanks for the information.

It looks like the .dat file is not going to be as useful as I thought.

What I need is some way to correlate the ball name (e.g. AT7) with the PinCtrl number, the mode selected and the Name of the pin in that mode.

I'd settle for just a table with the PinCtrl number with the Ball Name in a txt file (or .csv) or something like that.

I can't find anything in the documentation like this.

That would be helpful.

Thanks,

tim.

Tim:

Have you looked at the files generated by File -> Save -> Source -> Linux?

CSV output is something we may add to the tool.

Any other requirements that you would like to see in CSV file?

Regards,

Michael T

Michael,

I looked at the pinmux.h file and it is useful (particularly for software, obviously), but I need something else for the .csv file.

What I'd really like is a text file of some sort that has ALL of the balls (including power and ground and dedicated pins--not just the programmable ones).

Ideally this file would have the Ball/Pin #, PINCTRL # (n/a for dedicated pins), selected Mode, selected Name (even for dedicated pins). The names would ideally match the name in the datasheet pdf so someone could easily find the information about that pin.

This would be really useful for generating the schematic, because the designer would know what each pin is called and for programmable ones he would know how it is to be used. 

If the file was output as .CSV, I could read it into excel and make additional columns with notes on them for layout for example.  This would be VERY helpful.  As it is now, I have to go to table 4-8 of SPR614, choose the mode I want, get the PINCTRL#, then go to the individual terminal function tables (e.g. Table 3-17, 3-15) and find the PINCNTRL number and find out which Ball # it is associated with (or go to the drawing that shows the ball arrangement).  This is all very tedious and prone to mistakes.

The Pin Mux utility does some of the work for me, but there isn't really one place with all the information in it in a form easy to consume.

If there is an easier way to get all of this in one place, please let me know.

Thanks,

Tim.