Welcome to the Infineon Developer Community

I use CY7C65213.

I have questions when the driver install to system

Is it possible to set the virtual COM port number when the driver install to system?

    (ex:Are there optional command or parameter file etc to set the COM port number when the driver install to system?)

Is it possible to install driver without connecting device to the system?

Would you please inform the procedure of silent install that don’t need keyboard/mouse operaton?

Dear  Infineon：
      due to  in some application we need to keep the ILO frequency , We note datesheet  describle that API can improve the ILO accuracy, We see the code of CE210292_WatchDogTimer, but we don't down how to do it ;

     we design the code ,   we don't know where  is mistake of code , can you help to advice it . TKS;

uint32 iloMatchCounts=0x00;

#define WAKEUP_PERIOD_IN_MS 500u
#define DESIRED_DELAY 500000u
#define ILO_MATCH_COUNTS ((WAKEUP_PERIOD_IN_MS * CY_SYS_CLK_ILO_DESIRED_FREQ_HZ)/ 1000)

uint32 iloMatchCounts = ILO_MATCH_COUNTS;

//开始测量
CySysClkIloStartMeasurement();

CySysWdtWriteMatch(CySysWdtReadMatch() + iloMatchCounts);
//补偿ILO的值;
if(CYRET_SUCCESS == CySysClkIloCompensate(DESIRED_DELAY, &tempIloCounts))
{
iloMatchCounts = (uint32)tempIloCounts;
}

// 写值到WDT>>这个需要吗？
CySysWdtWriteMatch(CySysWdtReadMatch() + iloMatchCounts);

//读取WDTCount
count1 = CySysWdtReadCount();
CY_delay();
count2 = CySysWdtReadCount();

//算误差;
count0 = Count2-cunt1;

CySysClkIloStopMeasurement();

Hi, all

      checked from previous discussion saying that "using Nor Flash with file system need to erase all before write or create a file", Is that still true for emFile system?

     my project need to write log to a file on a Nor Flash, and keep the log files until it is erased. If I must erase Nor flash before I update the log, it is a big problem. 

   Thanks.

Victor 

We are using Aurix evaluation board.

Board name -> Triboard TC3x4L TH V1.0

part number of MCU -> SAK-TC364DP-64F300W

Need the sample code to bring up the board.

Kindly provide it immediately.

I have an EVAL-M1-101T-T038 and an EVAL-M1-IM323. I have not used any Infineon products before. I have watched several videos including How to get started with iMOTION™ 2.0 by Infineon4Engineers. I have also read the user's manual.

I downloaded the latest MCEWizard and MCEDesigner (both v 2.3.0.1). I setup the motor parameters in MCEWizard and saved the file. When I attempt to open an irc file in MCEDesigner I get Error: Could not open file (x86)\Infineon\iMotion2.0\MCEDesigner_v2.3.0.1\IMC101T_v1.03.03.irc. I read in the forum that if this occurs you should uninstall both software packages and install an earlier version. I did this and installed version 2.2. I got the same error. I uninstalled v2.2 and reinstalled v2.3. To make sure that I didn't have a corrupted IMC101t**.irc file, I downloaded the irc file for the IMC101T-V1.02_20_iMotion2Go and got the same error. I have a USB cable connected to the EVAL boards and they are powered. I am running Windows 7 sp1.

I am working on a HyperRAM controller in a MACHXO3 FPGA for this device.....

S27KS0642GABHI020

How is everyone handling the read cycle clock alignment? Variation over PVT is significant.

From the data sheet RWDS and DQout track each other tightly but they vary relative to the clock by a lot

1ns < tCKD < 5ns (clock to DQ valid)

0ns < tCKDI < 4.2ns (clock to DQ invalid)

My target clock is 125MHz (8ms)

At 125MHz the data valid window is....

3.0ns <  tDV < 3.2ns

but the window center varies a LOT.

2.5ns < tCENTER < 6.6ns (delay from the clock edge)

For this to track over PVT is to use RWDS (edge aligned with the data) as the clock but RWDS is not  free-running for a dynamic phase-lock.

A fixed delay from RWDS is possible but a known fixed clock period is required if guaranteed center alignment is desired.

What are your recommendations?

I have been tasked with testing CY8C4245 chips against various parameters on their OEM datasheet for authenticity, those parameters which include implementing and testing an analog comparator. Utilizing PSOC 101 videos and other online information I have already implemented various other tests which include I2C and other DC measurements of the GPIO pins with great success. Unfortunately after initial set up of my analog comparator I had noticed it was not acting as I had initially expected. I believe I have narrowed down my issues to C code specific to the comparator. I am aiming to use two hardware input pins P1[4], P1[5] to trigger the output P0[0] of the comparator so I can retrieve the “input offset voltage”. After various trials and errors I believe I need supporting C code to help with this. Is there any reference or example code showing the implementation of a fully functional comparator utilizing analog inputs that is available? I will in the near future be looking to test additional parameters relating to the comparator as well such as “Input Common Mode”. Any assistance or guidance in successfully implementing these tests is greatly appreciated.