2 Replies Latest reply on Aug 25, 2017 3:20 PM by milkfish1227_2635671

    SuperSpeed Explorer Kit debug port issue

    milkfish1227_2635671

      Hi,

      I am using SuperSpeed Explorer Kit to develop code communicate with SPI slave device. The issue I have is the debug port, I only can see the debug output in USBBulkSourceSinkLED project, none of other project such as UsbSpiDmaMode debug port works.

       

      I have been tried many sample project from SDK, none of them work too. Since USBBulkSourceSinkLED works, I am assuming the hardware is fine.

       

      I checked the code, it's pretty much the same code to init and DebugPrint() function. Not very sure what's going on.

       

      Any suggestions or anything I am missing here.

       

      Thanks,

      Dick

        • 1. Re: SuperSpeed Explorer Kit debug port issue
          ayarema_2483746

          Initially it is mapped to have the SPI off. So the debug pins go to the UART debug chip. If you want to use the SPI you will need to configure the main settings as follows

          io_cfg.useUart = CyTrue;
          io_cfg.useI2C = CyFalse;
          io_cfg.useI2S = CyFalse;
          io_cfg.useSpi = CyTrue;
          io_cfg.isDQ32Bit = CyFalse;
          io_cfg.lppMode = CY_U3P_IO_MATRIX_LPP_DEFAULT;
          

           

          That will move your UART down to pins GPIO[46] - GPIO[49] and enable SPI on the old UART pins of GPIO[53] -GPIO[57]. This means that the SPI connection will be wired to the UART debug chip, and the new UART Debug output will be wired to nothing. So you wont get anything unless you connect another USB to UART chip like an FTDI Friend to the new UART output.

           

          This will allow you to use the SPI though.

           

          -Andriy

          • 2. Re: SuperSpeed Explorer Kit debug port issue
            milkfish1227_2635671

            Hi Andriy,

            Yes, you are right. I saw the comments in the code.

             

            Thanks,

            Dick