Configure OSD32MP15x for 1.8V I/O operation

Forums Devices OSD32MP15x Configure OSD32MP15x for 1.8V I/O operation

Viewing 4 reply threads
  • Author
    Posts
    • #12919
      Farid AzharFarid Azhar
      Participant

        Hi,

        We are trying to enable 1.8V on our custom board based on OSD32MP157F SiP.

        We are not using MicroSD card at sdmmc1. Only using eMMC at sdmmc2 and WiFi module LBEE5HY1MW at sdmmc3.

        We’ve made all the required changes in hardware, PMIC  NVM registers and device tree but its not working and appears to be stuck at u-boot.

        We’ve made following hardware changes (with respect to OSD32MP1 RED board)

        • Connected BYPASS_REG1V8 to VDD_INTRNL.
        • Connected VDDA1V8_REG to VDD_INTRNL.
        • Left the strapping option pin of wireless module LBEE5HY1MW open.
        • Programmed the PMIC NVM registers to generate 1.8V at VBUCK_VOUT3 and VBUCK_VOUT4
        • Programmed the PMIC NVM registers to generate 3.3V at PMIC_LDO5

        We’ve made following kernel and tfa devcie tree changes. U-Boot device tree is same as Kernel device tree.

        Kernel device tree changes 

        • vdd:buck3 @ 1.8V
        • v3v3:buck4 @ 1.8V
        • v3v3_eth:ldo5 @ 3.3V

        TFA device tree changes 

        • vdd: buck3 @ 1.8V
        • v3v3: buck4 @ 1.8V
        • vdda: ldo5 @ 3.3V

        We have verified the correct output voltages are there.

        Power-up sequence stuck at uboot prompt STM32MP> after generating gollowing messages…

        invalid MAC address in OTP 00:00:00:00:00:00

        Net:   No ethernet found.

        Hit any key to stop autoboot:  0

        STM32MP>

        Would appreciate any help resolving this issue.

        /Farid

        • This topic was modified 1 year, 11 months ago by Farid AzharFarid Azhar.
      • #12921
        Farid AzharFarid Azhar
        Participant

          Board has started booting up in kernel but failing to initialize WiFi module.

          Its generating following error and $ ifconfig is not showing up wlan0 interface.

          [    3.204544] mmc0: error -22 whilst initialising SDIO card

          • This reply was modified 1 year, 11 months ago by Farid AzharFarid Azhar.
        • #12957
          Farid AzharFarid Azhar
          Participant

            few more mmc logs ..

            $ dmesg | grep -i mmc

            [    3.146380] mmci-pl18x 48004000.sdmmc: allocated mmc-pwrseq

            [    3.151679] mmci-pl18x 48004000.sdmmc: mmc0: PL180 manf 53 rev1 at 0x48004000 irq 48,0 (pio)

            [    3.187294] mmci-pl18x 58007000.sdmmc: mmc1: PL180 manf 53 rev2 at 0x58007000 irq 54,0 (pio)

            [    3.201548] mmci-pl18x 48004000.sdmmc: no support for card’s volts

            [    3.206280] mmc0: error -22 whilst initialising SDIO card

            [    3.261074] mmci-pl18x 48004000.sdmmc: no support for card’s volts

            [    3.267396] mmc0: error -22 whilst initialising SDIO card

            [    3.327512] mmc1: new HS200 MMC card at address 0001

            [    3.332902] mmcblk1: mmc1:0001 X29128 117 GiB

            [    3.337005] mmcblk1boot0: mmc1:0001 X29128 partition 1 4.00 MiB

            [    3.343798] mmcblk1boot1: mmc1:0001 X29128 partition 2 4.00 MiB

            [    3.348819] mmcblk1rpmb: mmc1:0001 X29128 partition 3 4.00 MiB, chardev (243:0)

            [    3.359377] mmci-pl18x 48004000.sdmmc: no support for card’s volts

            [    3.364471] mmc0: error -22 whilst initialising SDIO card

            [    3.381567]  mmcblk1: p1 p2 p3 p4 p5 p6

            [    3.424181] mmci-pl18x 48004000.sdmmc: no support for card’s volts

            [    3.428925] mmc0: error -22 whilst initialising SDIO card

             

          • #12959
            Neeraj Kumar Reddy DantuNeeraj Dantu
            Moderator

              Hey Farid,

              The kernel messages indicate an issue with voltage selection settings in the device tree. In the sdmmc3 node, an IO VCC supply may be needed. See example here: https://wiki.st.com/stm32mpu/wiki/SDMMC_device_tree_configuration. The property needed could be vqmmc-supply.

              I am assuming you have VIO for the WiFi module set to 1.8V and the IOs of the MMC interface are pulled to 1.8V and not 3.3V.

              If you have some time, please post some info about how you were able to resolve your earlier boot issue.

              Thanks and Best,

              Neeraj

            • #12965
              Farid AzharFarid Azhar
              Participant

                Hi Neeraj,

                Thanks for your response. We found the problem and fixed it.

                The WiFi module’s VBAT supply needs 3.3V to operate but in our device tree it was powered by 1.8V from buck4 that’s why it was failing to initialize.

                We changed the VBAT supply to 3.3V (ldo5) and WiFi module initialize and works OK.

                We don’t need vqmmc-supply for WiFi module, leaving the strapping option pin (GPIO_7) unconnected sets it for 1.8V.

                Regarding the earlier boot issue, we didn’t change anything in software. Just clean the area on board around strapping option pin (GPIO_7) may be it was shorting, not sure, but board starts booting with eMMC working at 1.8V.

                Thanks again for your help.

                /Farid

                 

            Viewing 4 reply threads
            • You must be logged in to reply to this topic.