AM6412: Producing a pinout (for symbol creation) for the AM6412 device.

Hello Alex,

I am not sure I understand your question. We suggest using the sysconfig tool as you are figuring out the pinmuxing of your system.

Regards,

Nick

Hello,

Thanks for the reply.

What I mean is that in order to produce a schematic symbol (with the a specific functionality , which will comes from the sysconfig) , one should use both the datasheet and the csv sysconfig tool...as the latter makes reference only to the pin muxed signals assigned...and not GND , Power supplies etc....(these are coming from the datasheet)

Is this correct ? I am asking this because I havent found any other way.

Thanks

Alex

Alex

A combination of both the datasheet and the SysConfig pinmux csv file would currently be the best way to to provide the necessary custom data for the schematic symbol.   

I think this could be a good enhancement to the tool, add an output file that could be used as a source for symbol generation. For this process, you would need ball name, signal name, ball number, direction.  Do you need any other data?

Hello,

Indeed , producing an extra file will help with the pin-out for the symbol preparation.

The parameters you suggested will do fine...see the example below...

Ball Number (V18)

Ball Name (This should be the function selected by the tool...e.g GPMC0_AD13)

Direction

Of course , one should ensure that there is no conflict before producing the output file

In any case , for now , I will proceed in using the datasheet and the csv Mux file... For example...

Pin AA2 = PRG0_PRU0_GPO4 will be changed to Pin AA2 = GPMC0_A1 (What has been selected from the sysconfig tool)

Thanks

Alex

The tricky part here , is that the sysconfig tool will only select AM64 beta....rather than the AM6412....

This makes the tool prone to possible errors , because some features are not present to all devices...

This is smt worries me at this stage.

Thanks

Alex

Hello Alex, 

Thank you for the note.

Please expect a delay due to the US holiday.

Regards,

Sreenivasa

Alex

The AM64x SysConfig pinmux does not differentiate between the variations of a device. Most of the deltas are internal.  

The beta tag will be removed, probably later this year.  the tag has no impact on the tool or the device.

--Paul

Hello,

Is there any update on this ?

Thanks

Alex

Hello Alex,

Thank you for following on this.

Please refer below reply from Paul

The beta tag will be removed, probably later this year.  the tag has no impact on the tool or the device.

Can you pls help me understand what update you are looking for..

Regards,

Sreenivasa

Hello,

Sorry...my bad....I was referring to what PaulM...replied...back...almost a week ago...

////

Alex

A combination of both the datasheet and the SysConfig pinmux csv file would currently be the best way to to provide the necessary custom data for the schematic symbol.   

I think this could be a good enhancement to the tool, add an output file that could be used as a source for symbol generation. For this process, you would need ball name, signal name, ball number, direction.  Do you need any other data?

////

Thanks

Alex