Neeraj Dantu

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 562 total)
  • Author
    Posts
  • in reply to: i2c error with rc_calibrate_mag #14659
    Neeraj Dantu
    Moderator

      The updated release of OSD3358-SM-RED software(v10.3) removed the sensors from userspace to the kernel space. So, you should be able to access the sensors in /sys/bus/iio/devices

       

      If you do want to utilize the userspace library, we suggest you use the v9.1 image. Both images are available here: https://octavosystems.com/octavo_products/osd3358-sm-red/#Software

       

      Best,

      Neeraj

      in reply to: Linux Kirkstone 5.15 #14637
      Neeraj Dantu
      Moderator

        Gil,

        The log you attached above indicates that the kernel is running into an error as soon as it takes control from u-boot. Increasing the log level can tell what exactly is going wrong. I do not believe that there is a dependency between U-Boot and kernel versions except for the boot command being passed on to the kernel from u-boot, but the boot process also involves other components: https://wiki.st.com/stm32mpu/wiki/Boot_chain_overview#STM32MP15_boot_chain. Please note that ST has also changed the boot image layout between Dunfell and Kirkstone(https://wiki.st.com/stm32mpu/wiki/STM32CubeProgrammer_flashlayout).

        My recommendation would be to use Krikstone versions of everything for the 15.67 kernel.

        Best,

        Neeraj

        • This reply was modified 7 months, 2 weeks ago by Neeraj Dantu.
        in reply to: Linux Kirkstone 5.15 #14583
        Neeraj Dantu
        Moderator

          Gil,

          Please change “&exti_pwr” to “&exti” as it looks like all the interrupts are being handled by the exti driver. This should fix the error you are encountering.

          Best,

          Neeraj

          in reply to: Issues getting HDMI image on Debian Image #14579
          Neeraj Dantu
          Moderator

            Ed,

            We are aware of this issue. The ALSA setup is not configured correctly in the Debian image. Software team is looking into it.

            Best,

            Neeraj

            in reply to: Linux Kirkstone 5.15 #14557
            Neeraj Dantu
            Moderator

              Gil,

              The patches that Octavo applies are for BRK an RED board. If your board is based on these boards, you will need the patches. If not, the 2 patches you need are the DDR parameters(for u-boot: stm32mp15-osd32mp1-ddr3-1x4Gb.dtsi or stm32mp15-osd32mp1-ddr3-2x4Gb.dtsi) for the specific DDR in use and https://github.com/octavosystems/meta-octavo-osd32mp1/blob/dunfell/recipes-bsp/u-boot/files/0009-Fix-device-tree-for-800MHz-speedgrade-MP1-to-work-wi.patch to add support for “F” variant devices to run on 650MHz.

              For the custom board device tree, I recommend taking a look at BRK device tree to understand what you need to port to your custom device tree. For example, OSD32MP1 uses STPMIC1 and so, STPMIC1 related configuration in the device tree is needed for any OSD32MP1 based board.

              All the Octavo patch files do not modify kernel source code. They add device tree source files for the supported boards. So, there should not be any issues with using .24 patches with .67 kernel version.

              Best,

              Neeraj

              in reply to: Flashing eMMC #14546
              Neeraj Dantu
              Moderator

                maynarde,

                Yes, you should be able to modify uEnv.txt to flash the eMMC from SD card.

                Best,

                Neeraj

                in reply to: Linux Kirkstone 5.15 #14545
                Neeraj Dantu
                Moderator

                  Gil,

                  You are correct, it looks like 1 of the patches from ST failed to apply because the file it was modifying was too different. The patch that is failing is from ST. You will need to resolve the error by reviewing the code being modified by the patch and making sure the modification applied by the patch is still valid and will function correctly.

                  An easier way probably would be to pull the kernel source from ST’s repository here: https://github.com/STMicroelectronics/linux/tree/v5.15-stm32mp-r2 (This code has all the ST patches already applied).

                  If you need granular control of the kernel source code, I suggest you look at https://wiki.st.com/stm32mpu-ecosystem-v4/wiki/OpenEmbedded_-_devtool to export the kernel code into its own workspace and make modifications/resolve conflicts in the source code.

                  Best,

                  Neeraj

                  in reply to: Linux Kirkstone 5.15 #14527
                  Neeraj Dantu
                  Moderator

                    Gil,

                    You should be able to use the kirkstone patches with 5.15.67. There are not any kernel level modifications that would affect the compilation.

                    Best,

                    Neeraj

                    in reply to: Ethernet PHY with OSD32MP1-BRK #14348
                    Neeraj Dantu
                    Moderator

                      Ray,

                      Since the only option for MII_COL is either PA3 or PH3, it won’t be possible to add 10/100 Ethernet to the BRK. However, RGMII configuration is possible.

                      Best,

                      Neeraj

                       

                      Adding the RGMII configuration pins:

                      PD24 — ETH1_MDIO

                      PC24 — ETH1_MDC

                      PD22 — ETH1_RX_DV

                      PC20 — ETH1_RX_CLK

                      PC21 — ETH1_RXD0

                      PC19 — ETH1_RXD1

                      PD21 — ETH1_RDX2

                      PC11 — ETH1_RXD3

                      PD10 — ETH1_TX_EN

                      PC06 — ETH1_TX_CLK

                      PC07 — ETH1_TXD0

                      PD08 — ETH1_TXD1

                      PD14 — ETH1_TXD2

                      PD07 — ETH1_TXD3

                       

                      • This reply was modified 9 months, 2 weeks ago by Neeraj Dantu.
                      in reply to: QSPI not detected in U-Boot #14294
                      Neeraj Dantu
                      Moderator

                        FLeblanc,

                        For ES parts, QSPI boot is not supported as it is a NAND SPI that Xilinx does not support. That is why you are seeing “unrecognized JEDEC id bytes”. Production parts have QSPI that is supported in Xilinx ecosystem. Please check the datasheet for the version you need as there is a 1.8V part(-xFA) and 3.3V QSPI part(-xFB).

                        Best,

                        Neeraj

                        in reply to: SD card fails for Kernel (error -110), but works in uboot #14293
                        Neeraj Dantu
                        Moderator

                          Thomas,

                          Can you look at the power consumption of your custom board compared to PocketBeagle? My suspicion is that something getting initialized during kernel boot is drawing too much power from IO may be because of a conflict with the pin definition with Pocketbeagle.

                          Can you probe the levels of CLK/CMD and DATA when kernel is booting to see what IO levels they are?

                          Best,

                          Neeraj

                          in reply to: eMMC Data sheet/Wear leveling #14290
                          Neeraj Dantu
                          Moderator

                            Ryan,

                            Please contact sales(at)octavosystems.com for additional information on this.

                            Best,

                            Neeraj

                            in reply to: eMMC Data sheet/Wear leveling #14271
                            Neeraj Dantu
                            Moderator

                              Ryan,

                              The eMMC inside OSD335x C-SiP implements wear-leveling. Specifically, we ensure that the eMMC is compliant to eMMC JEDEC v4.3 or higher.

                              Best,

                              Neeraj

                              in reply to: SD card fails for Kernel (error -110), but works in uboot #14270
                              Neeraj Dantu
                              Moderator

                                Thomas,

                                The data lines need to be pulled up to 3.3V on the MMC interface like in the Pocketbeagle for the interface to work. Do you have the pull-ups? It looks like the Pocketbeagle device tree enables the internal pull-ups on these pins: https://openbeagle.org/beagleboard/BeagleBoard-DeviceTrees/-/blob/v5.10.x-ti-unified/src/arm/am335x-pocketbeagle.dts#L238.

                                Can you also check voltage for VDDSHVx(SYS_VDD3_3P3V)?

                                Best,

                                Neeraj

                                in reply to: SD card fails for Kernel (error -110), but works in uboot #14246
                                Neeraj Dantu
                                Moderator

                                  Thomas,

                                  Looking at the boot log:

                                  [    1.818009] omap_gpio 44e07000.gpio: Could not set line 6 debounce to 200000 microseconds (-22)

                                  [    1.826827] omap_hsmmc 48060000.mmc: Got CD GPIO

                                  [    1.832087] omap_hsmmc 48060000.mmc: Linked as a consumer to regulator.1

                                   

                                  It looks like the driver is running into an error setting up the card detect GPIO. Here is the GPIO bank corresponding to the driver error: https://github.com/beagleboard/devicetree-source/blob/master/arch/arm/boot/dts/am33xx.dtsi#L155. You can deduce from the datasheet(https://www.ti.com/lit/ds/symlink/am3356.pdf) that SPI0_CS1 is GPIO0_6.

                                  You mentioned that the voltage on card detect pin is not 3.3V. Is there any other circuit on this pin that could effect it?

                                  If you have more than 1 board, please try other boards in case this is a 1 off error.

                                  Best,

                                  Neeraj

                                Viewing 15 posts - 31 through 45 (of 562 total)