element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Single-Board Computers
  • Products
  • Dev Tools
  • Single-Board Computers
  • More
  • Cancel
Single-Board Computers
Forum Enable the SPI port on MaaxBoard?
  • Blog
  • Forum
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Single-Board Computers requires membership for participation - click to join
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Suggested Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 58 subscribers
  • Views 2418 views
  • Users 0 members are here
  • spi
  • maaxboard
Related

Enable the SPI port on MaaxBoard?

rundemo
rundemo over 4 years ago

The J10 (40 Pin) expansion pin header on the MaaXBoard has the ESPI port (pin 19,21,23,24), However after modify the dtb file to enable the ESPI1, then program the /dev/spidev.0.0 to read SPI device but the spi port seems not work. Check the signal waveform and didn't see any output on the SPI clock (pin 23) or CS (pin 24).  The below is the modification I did on the device tree, do I need make other changes on device tree (for example pinctl) to make ESPI work?

ecspi@30820000 {

        compatible = "fsl,imx8mq-ecspi", "fsl,imx51-ecspi";

        reg = <0x00000000 0x30820000 0x00000000 0x00010000>;

        interrupts = <0x00000000 0x0000001f 0x00000004>;

        clocks = <0x00000004 0x000000c1 0x00000004 0x000000c1>;

        clock-names = "ipg", "per";

        status = "okay";

        #address-cells = <0x00000001>;

        #size-cells = <0x00000000>;

        channel@0 {

            #address-cells = <0x00000001>;

            #size-cells = <0x00000000>;

            #compatible = "spidev";

            compatible = "rohm,dh2228fv";

            reg = <0x00000000>;

            spi-max-frequency = <0x016e3600>;

        };




  • Sign in to reply
  • Cancel

Top Replies

  • jafoste4
    jafoste4 over 4 years ago +1
    Hi, What image are you running? Yocto or Debian? Also when did you last install the Out of Box Image? I just wanted to confirm you downloaded it recently. Thx, Josh
  • rundemo
    rundemo over 4 years ago in reply to jafoste4 +1
    Josh, I am using the debian image ( 91200026-MaaXBoard-LinuxShipmentImage-Debian-V1.1.1r10.rar.zip ): The below is the OS and Debian information: Should I try the latest version Debian image on the reference…
  • jafoste4
    jafoste4 over 4 years ago in reply to rundemo +1
    Hi, Please follow the below example to modify the DTS in https://github.com/Avnet/linux-imx/blob/maaxboard_4.14.78_1.0.0_ga/arch/arm64/boot/dts/freescale/maaxboard-extended-gpio.dtsi &ecspi1{ fsl,spi-num…
  • jafoste4
    0 jafoste4 over 4 years ago

    Hi,

    What image are you running? Yocto or Debian?

     

    Also when did you last install the Out of Box Image? I just wanted to confirm you downloaded it recently.

     

    Thx,
    Josh

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • rundemo
    0 rundemo over 4 years ago in reply to jafoste4

    Josh,
    I am using the debian image ( 91200026-MaaXBoard-LinuxShipmentImage-Debian-V1.1.1r10.rar.zip ):
    The below is the OS and Debian information:

    Should I try the latest version Debian image on the reference design download?


    image

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • jafoste4
    0 jafoste4 over 4 years ago in reply to rundemo

    Hi,

     

    Please follow the below example to modify the DTS in https://github.com/Avnet/linux-imx/blob/maaxboard_4.14.78_1.0.0_ga/arch/arm64/boot/dts/freescale/maaxboard-extended-gpio.dtsi

     

     

    &ecspi1{

    fsl,spi-num-chipselects = < 1 >;

    cs-gpios = <&gpio5 13 0 > ;

    pinctrl-names = "default";

    pinctrl-0 = <&pinctrl_ecspi1 >;

    status = "okay";

    #address-cells=<1>;

    #size-cells=<0>;

    spidev@0x00{

    #address-cellss=<1>;

    #size-cells=<1>;

    compatible = "spidev", "semtech,sx1301";

    spi-max-frequency = <20000000>;

    reg = <0>;

    };

    };

     

     

    Make sure to have a CS pin defined and pinctl set.

     

    -Josh

     

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • gonewtinwind
    0 gonewtinwind over 4 years ago in reply to rundemo

    hi all

    jafoste4

     

    this file is wrong, I fixed before whwn i used a spi rtc board, the ecsp1_ss0 is gpio5.io9 not io13.

     

    I told avent technical supporter before

     

    https://github.com/Avnet/linux-imx/blob/maaxboard_4.14.78_1.0.0_ga/arch/arm64/boot/dts/freescale/maaxboard-extended-gpio.dtsi

     

     

    --------------------

    read here for reference:

     

    https://community.nxp.com/t5/i-MX-Processors/how-to-make-spi-interface-rtc-function-work-for-imx8mq-maaxboard/m-p/116701…

     

     

    the issue is in the file you gave to me  the spi cs pin is wrong

    it should change to cs-gpios = <&gpio5 9 0 > ; from  cs-gpios = <&gpio5 13 0 > ;

     

    I checked the imx8mq processor hardware datasheet

     

    the ecsp1_ss0 is gpio5.io9 not io13.

     

    the gpio5.io13 is ecsp2_ss0 , wrong at here.

     

    correct:

     

    &ecspi1{

        fsl,spi-num-chipselects = < 1 >;

       cs-gpios = <&gpio5 9 0 > ;

        pinctrl-names = "default";

        pinctrl-0 = <&pinctrl_ecspi1 >;

        status = "okay";

        #address-cells=<1>;

        #size-cells=<0>;

        rtc@0x00{

            #address-cellss=<1>;

            #size-cells=<1>;

            compatible = "rtc-m41t93";

            spi-max-frequency = <5000000>;

            reg = <0>;

        };

    };

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • gonewtinwind
    0 gonewtinwind over 4 years ago in reply to gonewtinwind

    hi jafoste4 josh

     

     

    in linux 4.14.8 (yocto sumo)   my spi rtc works well as my modified

    maaxboard-extended-gpio.dtsi    ecsp1_ss0 is gpio5.io9 not io13.

     

    but in linux 5.4.24(yocto branch zeus)  my spi rtc Do NOT work after iI modified the same file . driver rtc-m41t93.c are all most same.

     

    why? do you change or use rtc in kernel config ?

     

     

    Thank u

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • gonewtinwind
    0 gonewtinwind over 4 years ago in reply to gonewtinwind

    dmesg | grep rtc                                             

    [    1.722660] rtc-m41t93 spi0.0: registered as rtc0                           

    [    1.728312] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc1          

    [    3.204174] rtc-m41t93 spi0.0: hctosys: unable to read the hardware clock 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube