AnsweredAssumed Answered

Changes in UART2 pad setting for u-boot

Question asked by piyush ashtikar on May 8, 2015
Latest reply on May 12, 2015 by Yuri Muhin

We are planning to switch from LTIB Platform to Yocto to build images for our custom board based on sabrelite,

using u-boot-boundary.

Uart debug console in our board is UART2,same as that in sabrelite.
However, Uart signals are mapped to PAD_GPIO7 and PAD_GPIO8 instead of default EIM_D26 & EIM_D27.

Now, we have done this precisely in LTIB and know the exact working procedure according to LTIB documentation.

But in Yocto we are not able to see debug console output,regarding this i have a doubt.



We build core-image-base and tried u-boot-boundary and did setting like this in
mx6qabrelite.c
iomux_v3_cfg_t const uart2_pads[] = {
    //MX6_PAD_EIM_D26__UART2_TXD | MUX_PAD_CTRL(UART_PAD_CTRL),
    //MX6_PAD_EIM_D27__UART2_RXD | MUX_PAD_CTRL(UART_PAD_CTRL),
    MX6_PAD_GPIO_7__UART2_TXD | MUX_PAD_CTRL(UART_PAD_CTRL),
    MX6_PAD_GPIO_8__UART2_RXD | MUX_PAD_CTRL(UART_PAD_CTRL),
};


Do we have to do any other setting for uboot so that we get output on debug uart 2?

Outcomes