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 & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • 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
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
MaaXBoard Hardware Design MaaxBoard-RT: HAT - SPI plus QSPI as HAT
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 1 reply
  • Subscribers 333 subscribers
  • Views 476 views
  • Users 0 members are here
  • pins
  • qspi
  • gpio
  • MaaXBoard-RT
  • Maaxboard RT
  • SPI slave
  • DualSPIder
  • spi master
  • pinmux
  • maaxboard
  • Pin Mux
Related

MaaxBoard-RT: HAT - SPI plus QSPI as HAT

tjaekel
tjaekel over 2 years ago

FYI,

I am going to create a breakout board (HAT), a PCB, in order to have SPI and QSPI interfaces on headers for this MaaxBoard-RT board (using J1 and J15).
The board should have these "features":

  • "DualSPI":
    SPI2 is master (Tx only), SPI4 is slave (Rx only) (uni-directional use), using a "delayed" SCLK' signal (compensate "round trip delay")
    SPI4 slave (Rx) will not use a PCS (nCS) HW signal (SW based enable)
    main requirement to have SPI with "delay compensation" for external devices connected (2x on same SPI bus)
  • optional to use LPSPI2 as bi-directional master/slave
  • LPSPI1:
    optional: a full bi-directional master/slave (in addition to all other SPIs and QSPI)
  • EEPROM:
    Use I2C6 for an I2C flash device (persistent storage of SYSCFG, man pages, optional "plug-in" code, "device tree"... - like on Raspberry Pi)
  • LPUART2/SPDIF_IN and _OUT, I2C3:
    provide as header pins, e.g. for user UART, SPDIF
  • I2C5:
    optional I2C, but shared with onboard I2C DAC (and with 2K2 pull-up already on MaaxBoard-RT)
  • I2S Master:
    provide the PCM signals as Master Out for an external DAC (in addition to onboard DAC)
  • PDM:
    one stereo channel for external MICs (as addition/alternative to onboard MICs)
  • ACMP signals: keep the Analog Comparator signals available
  • QSPI on header as: SW GPIO or FLEXIO2 QSPI
    SW GPIO QSPI should pin-compatible with SPI interface (FLEXIO2 would not)
    my main requirement to have QSPI for an external device
  • QSPI as FLEXIO:
    a QSPI flash on HAT board (for testing, for additional code/data, in parallel with header, two nCS signals for onboard QSPI and header QSPI)
  • free pins used as GPIO
  • RESET signals as GPIO out, INT signals as GPIO in, for external device connected

Here is the PinMux Table (how I want to use the MaaxBoard-RT header pins):

MaaxBoard-RT HAT header pins (pinmux)

Figure 1: MaaxBoard-RT HAT header pins and pinmux functions

Schematics for it might follow...
You could use this table also as reference for the pins and what might be possible with those (pinmux).

  • Sign in to reply
  • Cancel
  • tjaekel
    tjaekel over 2 years ago

    Here now how I want to use the MaaxBoard-RT pins and wire:

    QSPI wiring

    Figure 2: MaaxBoard-RT QSPI HAT wiring

    Comments:

    I want to use a CPLD, e.g. as level shifter and to deal with the direction (WR vs. WR+RD), for the additional HW logic.

    When I use FLEXIO2 and it is a QSPI RD transaction: the FLEXIO2 must be reconfigured to do a RD (after the WR with the prefix),
    change the direction on FLEXIO2.
    If the F_nCSx signal is generated also by the FLEXIO2 - it will be de-asserted between WR + RD. Therefore, I want to force via GPIO signal F_AND
    to keep this F_nCSx signal low between WR + RD.
    Not sure if I can handle the F_nCSx signals in SW: I want to make sure that this signal is valid after FLEXIO2 starts, not too early with floating QSPI signals.

    Instead of using a bi-directional level shifter, I want to have the option to use uni-directional drivers, e.g. in a CPLD.
    The F_DIR signal should change the direction.

    The CPLD (and its logic) is optional.

    The QSPI headers will have a 3V3 pin, so that the level shifter logic (and F_DIR) can be part of a breakout unit ("in the cable").

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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