Hello,

Thank you for your question.

Unfortunately we do not have any specific examples for the NXPS32K148, but if you intend on implementing your solution with a low power MCU I would suggest looking at the following application notes which concern building an EVE library. The first application note covers how the low level transfers are structured between and MCU (in this example a PIC) and the EVE IC. The second covers how to create an EVE Library to interface to the MCU. And finally the last one covers some EVE examples for PIC MCUs, :
FT81X Simple PIC Example
FT81X Creating a Simple Library For PIC MCU
FT81X Simple PIC Library Examples

These application notes cover how to configure a display, but please take note of the specific display settings your module utilises.

The principals described in these Applications Notes can be used to implement solutions for a wide variety of MCUs, and give a better understating of how EVE functions on a low level.

We are currently finalising another application note based upon BRT_AN_014 above which expands this to a variety of other MCU platforms, I would advise utilising this library for porting to the NXPS32K148. I have uploaded the draft versions of this application note to WeTansfer (we are currently migrating our FTP site), please see the following link:
https://we.tl/t-75ILJqCMMc

As for HMI creation with these libraries you can use the EVE Screen Editor (ESE) to lay out static screens and create Display Lists but this does not create code for the logic of moving between screens. EVE Asset Builder (EAB) is also available to convert any graphics assets (fonts, images, etc) your require into an EVE readable format. These can be found at the following:
https://brtchip.com/eve-toolchains/

Best Regards,
FTDI Community

Hello,

This is not possible. Is there a reason why you need it?
You should use the instructions (e.g. clock data on x edge) so that you change data on the edge which is not the valid one and in this case would normally not be an issue.   

Which SPI mode does your SPI peripheral use? Note that MPSSE only supports mode 0 and 2.
Mode 1 or 3 is not supported.

You can also try enabling 3-phase clocking.
This will give 3 phases so data is valid on both edges.

See AN_108 Command Processor For MPSSE and MCU Host Bus Emulation Modes for more details.

AN_411_FTx232H MPSSE I2C Master Example in Csharp shows an illustration of 3-phase in section 6.2.2.

Best Regards,
FTDI Community

Hello,

Thank you for your question, I will look into reproducing this behaviour.

Could you just clarify what hardware configuration for the FT4222 you are using? is it the UMFT4222EV-D?


Best Regards,
FTDI Community

Hello,

Could you advise what you see on the MOSI/MISO/CS/SCK lines when you run the code? If you have a logic analyser or a PC-based scope could you capture the lines to see if you are getting the expected waveforms.

Which SPI mode does your SPI peripheral use? Note that MPSSE only supports mode 0 and 2,

Note that you should also check the sizeTransfered value after a read or write to ensure your requested bytes were all transferred.

What was the error which you saw, did you get the expected number of bytes back but they were the wrong values?

One further thing to also check is that you have opened the right channel, depending which channel A or B your SPI device is connected to.

Best Regards, FTDI Community

Hello,
 
AN_394 User Guide for FT260 and AN_395 User Guide for LibFT260 should answer your questions.
Code examples are provided with the LibFT260 library.


Regards
FTDI Community

Hello,

Yes that is correct:

Mode	CPOL	CPHA	Notes
0	0	0	Supported
1	0	1	Not Supported
2	1	0	Supported
3	1	1	Not Supported

We are not aware of any issues at higher speeds like 30 MBaud and the device is widely used.

What hardware are you using?

Are you using the D2XX drivers direct or using LibMPSSE library?

Maybe other FTDI Community users will be able to help you further on this issue.

Best Regards,
FTDI Community

Hello,

Thank you for your feedback, I have reported this back to the development team for investigation.

Best Regards,
FTDI Community

Hello Adam   
You should look at section 5.3 (page 22 & 23) of the data sheet for your part.   Baud rate settings etc are dependant on the operating clock frequency of your application.   

Thanks
FTDI Community