Mistake in am335x-osd3358-sm-red.dts related to MPU9250

Forums Reference, Evaluation, and Development Boards OSD3358-SM-RED Mistake in am335x-osd3358-sm-red.dts related to MPU9250

Viewing 2 reply threads
  • Author
    Posts
    • #9190
      Dave Mcospan
      Participant

        I think I found a small error in the dts file for the OSD3358-SM-RED board.

        The entry for the MPU9250 incorrectly declares the MPU6050 in the compatible string where it is


        compatible = “invesense,mpu6050”

        and it should be


        compatible = “invesense,mpu9250”

        This is what is used in the beaglebone blue.

        I was working on another board and was looking for references to the MPU9250 and found yours so, unfortunately, I don’t have a ‘red’ board to test it out but I hope to help your team.

        Thanks,

        Dave

      • #9233
        Eshtaartha Basu
        Moderator

          Hello cospan,

          Thank you for letting us know.

          At the time of RED Debian release, the MPU driver didn’t function as expected with the string compatible = “invesense,mpu9250”. Hence, we decided to use the string compatible = “invesense,mpu6050”. However, the MPU driver may have been updated now and we will consider making suitable updates to our device tree in the next release.

        • #9236
          Dave Mcospan
          Participant

            That’s interesting, I ran into an issue when I brought up my board too.

            The issue was related to threaded interrupts and that I was using an i2c interrupt controller/GPIO expander. I wrote about it here:

            https://www.raspberrypi.org/forums/viewtopic.php?f=107&t=253429

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