No response from NHD-5.0-800480FT-CTXL-CTP

Comments

6 comments

  • Steve Easton

    MISO -> NHD Pin 4 -> STM32 Pin PC2

    MOSI -> NHD Pin 5 -> STM32 Pin PC3

    SCK -> NHD Pin 3 -> STM32 Pin PB10

    nCS -> NHD Pin 6 -> STM32 Pin PB12 (GPIO Output)

    nINT -> NHD Pin 7 -> STM32 Pin PB11 (GPIO Ext. Interrupt Input)

    nPD -> NHD Pin 8 -> STM32 Pin PB13 (GPIO Output)

     

    I imagine the NHD FTDI chip is running side nINT is driven high. When I don't have power to the NHD the nINT pin low.

    0
  • Engineering Support
    Community moderator

    Hi Steve,

    I wanted to get some clarifications on what you are trying to achieve. Are you trying to read the identification of the display?

    0
  • Steve Easton

    I'm trying to read the display ID on boot. I dug around and perhaps the STM32F429I-DISC board may be interfering with communication somehow. The Discovery eval board has a lot of devices connected to the MCU. There are displays and other onboard devices. The PC2 pin is connected to other devices.

    I'm going to try a NUCLEO board in a day or two to see if there is a conflict. The NUCLEO board is a bare-bones type of evaluation board.

    0
  • Steve Easton

    I wired in a NUCLEO board and see the same results.

    0
  • Steve Easton

    Here is a Zoomed in capture of the MOSI signals 

    0
  • Steve Easton

    I realized that MSBit of the read request should be 0 for a read request, but I'm still receiving 0x00 responses.

     

    0

Please sign in to leave a comment.