TMDXIDK437X: Motor control example

Hello Yuval,

The AM437x IDK board pinmux file can be found under pdk_am57xx_1_0_16/packages/ti/board/src/idkAM437x/idkAM437x.pinmux

Regards,

Nick

Thanks

after I edit the pinmux I generate a set of files.

what should I do with them ? replace existing files and ccs910->clean build? 

note that if i introduce a compiler error to the file idkAM437x_pinmux.c in this location and do clean all and build I do not get errors ?!?  

this folder does not seems to contain dkAM437x.pinmux

(assuming it should be pdk_am43xx_1_0_16 and not pdk_am57xx_1_0_16)

it has the following files

idkAM437x.c

idkAM437x_ethernet_config.c

idkAM437x_info.c

idkAM437x_lld_init.c

idkAM437x_pinmux.c

src_files_idkAM437x.mk

and the folders

device

include

Hi Yuval,

This E2E thread contains some tips for editing the PINMUX on an AM437x board:

e2e.ti.com/.../797120

Within that thread, a design document on editing the PINMUX for the AM335x and AM437x board which will prove useful can also be found:

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/5432.AM335x_5F00_AMIC110_5F00_Board_5F00_Porting_5F00_using_5F00_PRSDK.pdf

Once you've look through those, please let me know if you have any further questions.

Thanks,

Max

Hi Max,

your answer helped me a lot.

Thank you very much

the only thing I now miss is the source  *.pinmux file for the idk am437x 

in addition to previous message :

If I take one of the files in below folder and use the pinmux tool to create the *.c and *.h , the files are not the same as the original *. c and *.h

Hi Yuval,

In looking at the section within the above PDF titled "Post  Processing steps" you should have a new pinmux.h and pinmux_data.c file.

If you replace the existing files with those new ones, and then follow the steps in section "Rebuilding board Library in Processor SDK RTOS", you should be able to rebuild the board library with a new pinmux configuration.

Thanks,

Max

Hi Max,

Thanks for answering

I know how to generate pin mux  C and H files , and how to compile the PDK..

what I am looking for the the *.pinmux file that is read by the PINMUX tool and that the C and H files are a result of that *.pinmux file.

I tried to verify that one of the *.pinmux files in the PDK folder is the one that used to build the IDK pinmux files.

I expected that if I re-generate C and H files from existing *.pinmux file they will match the existing C and H pinmux files.

as I wrote , none of the *.pinmux files I found in the PDK folder is the "father" of the C and H pinmux files that are associated with the IDK (Assuming the changes do not originate the different pinmux tool versions)

I'd expected that if I open the idkevm_config.pinmux and generate C and H file from it, the new files will be the same as am433_idkevm.h and am433_idkevm_pinmux_data.c.

but when I do that , they aren't

can you please confirm that am433_idkevm.h and am433_idkevm_pinmux_data.c are a result of idkevm_config.pinmux ?

if not , can you help me find the correct *.pinmux file ?

Yuval,

Switch to the SysConfig tool please and start a new empty project for AM437x. From there, use the tool to add the eHRPWM3 SYNCO signal. In the output the code diff is highlighted for you. That can be used to edit the existing c. and h. files rather than trying to replace the full file. 

Make sure the pins in the code output match the pins in the schematic (AB18, AC25).

Regards,
Ahmad

Hi Ahmad,

Thanks for your reply.

1) if I add SYNCO3 by means of file diff - don't I need to disable the camera pins ( since I dont start with  *.pinmux , I do not know the state of these pins and we need to avoid  conflict) ? Maybe you can confirm their status ? what about EXT_HW_TRIG? is it enabled or not ?  should I assume epwm1b is not configured (i.e. input) so that there is no contention?

2) about R375 : I need to create this 0 Ohm short. right ? This pin , in additional to the optional connection to EXT_HW_TRIG goes to other places associated with the camera . should I disconnect CAM0_DATA1 by removing R325 ? or its not needed (assuing in (1) we removed the amera pins ? 

Hi Yuval,

To address an earlier point of yours and help answer your first question:

“as I wrote , none of the *.pinmux files I found in the PDK folder is the "father" of the C and H pinmux files that are associated with the IDK (Assuming the changes do not originate the different pinmux tool versions)”

You are correct, this is true due to updates to the pinmux tool. You should run the .pinmux through the latest version of the pinmux tool, Then when you go through the resulting output am43xx_idkevm_pinmux_data.c file you can search for pins of interest and see if they're being configured or not.

To answer the second question: 

Those pins are going to headers, so if you don't have anything attached to those headers, the operation of the board will not be affected.

Thanks,

Max