Welcome to the Infineon Developer Community

Hi,  I am having the FX3 development kit that's supposed to work with the aptina MT9M114 sensor(Image sensor).  we are planning to change aptina  MT9J003 sensor. but I am struggling to change the register parameter.

datasheet doesn't have direct register address. kindly help me to develop the image sensor. 

some registers I changed but that's are correct  or not I don't know. that are below 

Sensor. H

/* I2C Slave address for the image sensor MT9J003. */
#define SENSOR_ADDR_WR 0x20 /* Slave address used to write sensor registers. */
#define SENSOR_ADDR_RD 0x21 /* Slave address used to read from sensor registers. */

Sensor .c

SensorI2cBusTest (
void)
{
/* The sensor ID register can be read here to verify sensor connectivity. */
uint8_t buf[2];

/* Reading sensor ID */

if (SensorRead2B (SENSOR_ADDR_RD, 0x00, 0x00, buf) == CY_U3P_SUCCESS)
{
//if ((buf[0] == 0x24) && (buf[1] == 0x81)) //MT9M114
if ((buf[0] == 0x2C) && (buf[1] == 0x01)) //MT9J003
{
return CY_U3P_SUCCESS;
}
}

Regards

Vinohari (+91 8861223731 )

Hi,

I am looking use PD-EPR for 140W support in a sink application. Is there any plan to update the CYPD3177 to support EPR?

Thanks in advance.

I am working on a project for array readout. I am using CY8CKIT-059.

There are 8 analog inputs that I have to read  sequentially using the ADC and AMUX.

I was wondering if there is any way I can  connect all the other inputs to ground while only one of the analog inputs is connected to the ADC. 

Thanks in advance

Balu

Hi, I may be missing simple here and am hoping that is all it is. I setup this logic circuit in order to create a simple state machine (I tried with the LUT as well and encountered the same issue). The way it is supposed to work is if the button is pressed the LED turns on, if the button is pressed again nothing happens. If it is pressed again the LED turns off, then the cycle repeats. The issue I am encountering is that the LED always follows the clock pulse and always turns on whenever the button is pressed.

I attempted switching the clock input for the flip-flops with the button, however the same issue persisted. The clock (tied to the Clk_pin) was made from two cascading watchdog timers for 1 Hz. I changed this to an on board clock at 367 Hz (minimum frequency division for CY8CKIT-044 Pioneer kit) and the issue still persisted. 

I have attached the code I made for the 1 Hz clock I created with the schematic design and timer setup.

------------------------------------------

void Clk()
{

    ClkPin_Write(~ClkPin_Read());

}

int main()
{

/* Enable the global interrupt */
CyGlobalIntEnable;


CySysWdtSetInterruptCallback(CY_SYS_WDT_COUNTER1,Clk);
CySysWdtSetCascade(CY_SYS_WDT_CASCADE_01);

CySysWdtSetMatch(0,512);
CySysWdtSetMatch(1,64); //So our total divide is 512*64

for(;;)
    {
          CySysPmDeepSleep();
     }
}

Dear All members

we are making the 1000+1000w , 2 CHANNEL CLASS S AMplifier to run speckaer of 4ohm load. This is running ok,,,we are stuck one point

1) In case Mosfet ar short the DC voltage will reach to speakers and this can blow the speakers.

How to protect this situation.

In the Power supply line to amplifier (+ / - 70VDC) we have fuse .....can we have better solution to protect the speaker from having DC voltage in case Mosfet are Short

Hello, 

I'm trying to do some performance measurements on functions and I'm getting results that I cannot explain. Most likely I am overlooking something or do not have something configured correctly so looking for any suggestions. 

Using the TC375 lite kit, I have Core 1 dedicated for this testing. The start of the function looks like this: 

void core1_main(void)
{
    IfxCpu_enableInterrupts();
    /* !!WATCHDOG2 IS DISABLED HERE!!
     * Enable the watchdog and service it periodically if it is required
     */
    IfxScuWdt_disableCpuWatchdog(IfxScuWdt_getCpuWatchdogPassword());
    IfxScuWdt_disableSafetyWatchdog(IfxScuWdt_getSafetyWatchdogPassword());
    IfxStm_enableOcdsSuspend(&MODULE_STM1);
    /* Wait for CPU sync event */
    IfxCpu_emitEvent(&g_cpuSyncEvent);
    IfxCpu_waitEvent(&g_cpuSyncEvent, 1);
    fstm_1 = IfxScuCcu_getStmFrequency();

    //setupCSV();
    collectMetrics();
    //test1();
    //closeCSV();
    while(1)
    {
    }
}

collectMetrics performs two checks, PER0 is a marco for the function being tested. 

void collectMetrics()
{
   getCTimeMetrics(PER0, &maxCTimePER0, &minCTimePER0, &timeCPER0);
   getIfxMetrics(PER0, &instructionCountPER0, &clockCountPER0);
}

The getCTimeMetrics, uses STM1 to get timing and calculate the delta that the function takes to run. 

void getCTimeMetrics(void (*func)(), double *maxTime, double *minTime, double *timeArray)
{
    unsigned long lower;
    unsigned long upper;
    unsigned long long start;
    unsigned long long end;
    unsigned long long delta;
    for(int i = 0; i < 10; i++)
    {
        lower = ((uint32)MODULE_STM1.TIM0.U);
        upper = ((uint32)MODULE_STM1.CAP.U);
        start = (unsigned long long)((unsigned long long)(upper << 32) | (unsigned long long)lower);

        func();

        lower = ((uint32)MODULE_STM1.TIM0.U);
        upper = ((uint32)MODULE_STM1.CAP.U);
        end = (unsigned long long)((unsigned long long)(upper << 32) | (unsigned long long)lower);
        delta = end - start;
        timeArray[i] = (double)(((double)delta)/(double)CLOCKS_PER_SEC);
    }
    *maxTime = timeArray[0]; /* place holder for now */
    *minTime = timeArray[0];

}

The other function uses the cpu performance functions to get the instruction count and clock count. 

void getIfxMetrics(void (*func)(), uint32 *instructionCount, uint32 *clockCount)
{
    IfxCpu_resetAndStartCounters(IfxCpu_CounterMode_normal);
    func();
    IfxCpu_stopCounters();
    *instructionCount = IfxCpu_getInstructionCounter();
    *clockCount = IfxCpu_getPerformanceCounter(CPU_CCNT);
}

We tested the function measuring it with Gliwa and on a 200MHz part it ran in a range of 230ns to 270ns. I would expect being a 300MHz part, it would be quicker on the TC375. However, the results I am getting from the two functions are, in my initial thoughts, way to different. 

I'm getting 52 clock counts which would scale to about 173 ns with a 300MHz clock. However, the STM1 calculations are reporting around 290ns. I figured there would be some differences, but I cannot justify why there is 120ns difference. All code flash and static RAM for these functions is in core 1 (pflash1 and dsram1).  If it was being interrupted I would assume I would see the same results on either function. 

Does anyone have any thoughts to why I am seeing such a large difference? Does this make sense? I feel I am overlooking or missing something, but I cannot see it. 

Thanks in advance for any suggestions. 

Hello all,

I have created the project using the CYBLE 416045-2 where the ADC continuously samples data and as soon as 240 bytes of data is acquired it is sending it through notification packet over the BLE (Project is attached herewith)

The connection is established properly, and I am able to send data continuously. I am trying to measure current during this entire process. I have attached my multi-meter with a jumper on the J8 jumper on the board as marked by yellow on the picture attached.  The J2 jumper (marked by blue) decides the voltage level on the board. With 3.3 V I am observing current of 117.3mA however when I open the J2 jumper (board running on 1.8V) the current I am observing is around 1.2mA however in this case I am not able to find the BLE connection of the board on the Cy smart app or even on the BLE dongle. 

Can anyone guide me is this the correct way to measure current for this board? If so, what am I doing wrong such that the current is going to 117.3mA in 3.3V case because it is WAY TOO MUCH above the board specification. 

Also, if there is any wrong on the programming side could you guide me on how to reduce current for this case. I want to run the board on minimum possible power and minimum possible current cause it needs to run for days on a single cell of battery.

Thanking you,

Anik Sengupta