I'm having some issues trying to get the *most* out of my dsPIC33EP512MU810, and the SPI bus which is connected to a Riverdi display (7" capacitive touch) with the FT813 EVE chip.
Is there any reason that I cannot run the MCU at 70 MIPS (140 MHz), and not run the FT813 at a speed at or near 30 MHz? I can only seem to get the display to run if I use my MCU at a speed of 80 MHz.
Looking at the SPI clock with a logic analyzer, it is running at 10 MHz, which is 1/3 of the speed that the FT813 can operate. I have played with the settings for the MCU clock,
as well as for the SPI clock. My development board is the EasyPIC Fusion V7. I've ran through the clock setup calculations, which seem to work fine, but not with the FT813 added to the mix. (Banging head!)
MCU and SPI CLK setup with FT813, dsPIC33EP512MU810
-
- Posts: 2
- Joined: 31 Jan 2021 20:48
- filip.grujcic
- Posts: 822
- Joined: 14 May 2018 08:34
Re: MCU and SPI CLK setup with FT813, dsPIC33EP512MU810
Hello,
Could you configure your project for 140MHz (meaning change the config bits and PLL settings properly, not just the frequency in the MCU frequency textbox), zip it and attach it here for inspection?
Regards,
Could you configure your project for 140MHz (meaning change the config bits and PLL settings properly, not just the frequency in the MCU frequency textbox), zip it and attach it here for inspection?
Regards,
Filip Grujcic
-
- Posts: 2
- Joined: 31 Jan 2021 20:48
Re: MCU and SPI CLK setup with FT813, dsPIC33EP512MU810
Thank you Filip, let me make the setting changes and I will get back to you here with the code. Also, if you could assist with another item. I want to use the SD card for the resource files. However, I'm unable to get the Micro-SD card reader and the Riverdi 7 inch display to work together on the same SPI bus (SPI3). The development board is EasyPIC Fusion V7 and the dsPIC33EPMU810 MCU board. I've tried many settings to get the display and SD card to work together. When I select external resource file, the program compiles, but the Riverdi won't come up. First, however, we can address the first issue about clock speed.