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.

TDA4VM: Pinmux configuration in McU1_0

Part Number: TDA4VM
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

We have a GPIO pin that is being controlled by MCU1_0 firmware. I noticed that the pin can change the output state only after  QNX has booted. My investigation leads me to the conclusion that it is because the pinmux settings file as generated by sysconfig tool is loaded by QNX. Hence  the pin only gets configured as output after QNX boots. However, this is not desired behaviour. We want the pin to be configured as soon as MCU1_0 comes up. Can you please guide me if there are APIs  that  I can use in my MCU1_0 firmware to configure pinmux settings in the firmware itself?

Regards

Deepankar Maithani

  • Hi Deepankar,

    To my knowledge the QNX BSP, or other QNX software offerings on TDA4M will not modify pinmux settings in bulk.   The QNX BSP drivers may modify GPIO pinmux settings that are required for the driver to function.  

    There are two possible boot flows used on MCU1_0 PL (uboot) or SBL, which is being used in your setup?

    Thanks,

    kb

  • We are using uboot

  • In U-Boot which is the exact pin that needs to be configured as GPIO? Which module makes use of that?

    Reference Example:

            vdd_sd_dv_alt_pins_default: vdd-sd-dv-alt-default-pins {
                    pinctrl-single,pins = <
                            J721E_IOPAD(0x1d8, PIN_INPUT, 7) /* (W4) SPI1_CS1.GPIO0_117 */
                    >;
            };
    
    Usage:
    
     vdd_sd_dv_alt: gpio-regulator-TLV71033 {
                    compatible = "regulator-gpio";
                    pinctrl-names = "default";
                    pinctrl-0 = <&vdd_sd_dv_alt_pins_default>;
    
    

    File: arch/arm/dts/k3-j721e-common-proc-board.dts

    - Keerthy