This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP-AM263: Pin-MUX-configuration by SYSCONFIG of GPIO101/Pin17 to use with PRU

Part Number: LP-AM263
Other Parts Discussed in Thread: SYSCONFIG

Hello,

 

I'm using the evalboard AM263x-LP in combination with SDK 8.6.00.34 and Sysconfig-tool 1.15.

I want to configure GPIO101 to use as PR0_PRU0_GPIO13. For this purpose I made following GPIO-configuration in the sysconfig-file:

 

 

To use the GPIO101 as PR0_PRU0_GPIO13 from PRU0-unit, I additionally have to reconfigure the mux mode register from 7 to 0.

 

 

Is there any possibility to do this additionally mux mode register reconfiguration/setting in the Sysconfig-tool?


At the moment, sysconfig-tool produces only code for GPIO101-mode.

 

Here is a snippet from the generated file ti_pinmux_config.c. A manual change from 7 to zero is no help, because the values are rewritten by sysconfig-code-generation by every project build.

To solve this problem, I do a second mux-reconfiguration with my own values. But is there any possibility to configure this mux-setting also from sysconfig-tool?


 

Best regards,


Jo Scho

  • Hi,

    First, to add a PRU GPIO, you should add the PRU instance and select the IO configuration there.  You should not try to select the PRU GPIO Mux Mode from the GPIO instance.

    However, that said, there is currently a bug with the latest AM263 SDK and Sysconfig that the PRU is not populating correctly in sysconfig.  We have filed a ticket to get this resolved.

    For now, your solution of a second configuration step with your own values is probably the best solution.

    Thanks,
    Mike

  • Hi Mike,
    thanks for your answer.
    Only still one question for correct understanding.

    However, that said, there is currently a bug with the latest AM263 SDK and Sysconfig that the PRU is not populating correctly in sysconfig.  We have filed a ticket to get this resolved.

    With "not populating" you mean this behaviour? In my PRU-instance I can even there configure anything.

     

    Best regards,
    Jo Scho

  • With "not populating" you mean this behaviour? In my PRU-instance I can even there configure anything.

     

    Exactly.  If you compare to adding a PRU (ICSS) instance in AM243, for example, you get multiple fields to start actually configuring the PRU ICSS Module:

    Thanks,
    Mike

  • @Jo Scho: What is your second configuration step to override Sysconfig?