MSVC codes not working

[nelson_lobo]

I've been trying to start my BT815 setup provided by panasys http://www.panadisplay.com/ftdi-intelligent-display/7-tft-lcd-with-ctp-with-bt815-paf70uwfnwc01.html

I tried running the MSVC codes provided in your sample codes section. I'm currently using Visual Studio 2019 Community edition.
The code seems to build without any errors. It does prompt me to Retarget Projects Windows SDK to 10.0 and Platform toolset to v1.42

Once that's done when I try running in the debug mode.
With my breakpoint set at "line#1019 BootConfig(phost);"  the CMD prompt pops up with
Init FT4222 as master device failed!
FT4222_SPI_SetDrivingStrength failed!
Init FT4222 as GPIO interface failed!


How do I fix this issue?
PS: I did try this : http://www.ftdicommunity.com/index.php?topic=130.0
I copied the exe generated in the debug folder to the LibFT4222-v1.43 folder containting 1)LibFT4222.dll 2)LibFT4222.lib :

I get this :
FT4222_SPIMaster_SingleWrite failed, SizeTransfered is 0 with status 10
Gpu_Hal_FT4222_Rd failed

Please check attachments for more information.

Regards,
Nelson Lobo

[BRT Community]

Hello,

Please make sure to use the samples below which include BT81x support and to select the device in the platform.h file.
EVE_Samples_v1.1.0_RC_28062019.zip

We recommend to copy the LibFT4222H lib and dll files from our libFT4222H library into the same location as your exe in your EVE sample app directory to ensure that the sample app can find the library.
https://www.ftdichip.com/Support/SoftwareExamples/FT4222H.htm

Best Regards, BRT Community

[Rudolph]

I do have both a PAF70 and a PAF90 and support for the PAF90 in my code library and the display parameters are the same as for example the ME813A.

[nelson_lobo]

Hi,
I have followed your instructions and did the needful.
The IDE prompted me the same again to Retarget Project Windows SDK to 10.0 and Platform Toolset to 1.42

I ran App_Gauges in debug mode, replaced the .dll and .lib files in Bin/Msvc folder and also in the Debug folder which is created after compilation. But the outcome was the same as above.

Regards,
Nelson Lobo

[BRT Community]

Hello,

It looks like the SPI master init is failing, which is causing the subsequent calls to return a FT4222_IS_NOT_SPI_MODE error.
Replacing the FT4222 Lib/DLL files in the project normally resolves this issue.

Are you by any chance using a USB 3.0 port on a windows 7 machine?

Best Regards,
BRT Community

[nelson_lobo]

I am currently using a Windows 10 system with USB2.0
I have a demo code and checked the same which displays the "Bridgetek Bridging Technology" logo crystal clear. But the problem is that the supplier has only provided the exe files and not the source codes.

I have also tried running the same using Arduino with few sample codes and they seem to start but with multiple horizontal lines creating a flicker. On the other hand when it is controlled using the FT4222H it works perfectly fine with the static demo code. I have attached the code here.

Display Image: https://drive.google.com/file/d/1zquH-eJwlfyXwzkqmHYU-hDhbQOK8ZwW/view?usp=sharing

Regards,
Nelson Lobo

[BRT Community]

Hello,

Could you just clarify which folders you are placing the DDL/lib files in?

If you use the 4222 DLL and lib file included in your 'BT81X Demo.rar' project within the sample applications does this resolve the issue?

Best Regards,
BRT Community

[nelson_lobo]

Sorry for the late reply.

Well I have taken files from ../LibFT4222-v1.4.3/imports/LibFT4222/lib/LibFT4222.dll,LibFT4222.lib
from here into either the debug or release folders where the exe exist.

I also tried copying the .exe file into separate folder where the above three files co-existed i.e the (1).exe, (2).dll, (3).lib.
Also took care to create the .exe without .dll which was set by default.

My only concern is if the demo code from the supplier works then even the the codes supplied by your team should work.
I hope I'm not making any mistakes. Would appreciate some check-lists on this.

For your knowledge i will share a link to the video as well.
https://youtu.be/X1t0wByW8Pc


Regards,
Nelson Lobo