Welcome to the Infineon Developer Community

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

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, 

• In my application, some values should be written to GPIF, then the GPIF switches to read and transfer what was read to USB.
• I used this example (C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\firmware\boot_fw\gpiftousb) to build my application, and changed the cyfxgpif2config.h to the one generated from GPIF II Designer (shown below)
• Once this file is switched, the USB streaming fails with error 997
• is there a reason for that?

/*
 * Project Name: AD7381-4 Interface to USB3.cyfx
 * Time : 11/19/2022 18:51:09
 * Device Type: FX3
 * Project Type: GPIF2
 *
 *
 *
 *
 * This is a generated file and should not be modified
 * This file need to be included only once in the firmware
 * This file is generated by Gpif2 designer tool version - 1.0.1198.2
 * 
 */

#ifndef _INCLUDED__
#define _INCLUDED__
#include "cyu3types.h"
//#include "cyu3gpif.h"

/* Summary
   Number of states in the state machine
 */
#define CY_NUMBER_OF_STATES 4

/* Summary
   Mapping of user defined state names to state indices
 */
#define START 0
#define CONFIG_ADC 1
#define ACTIVE_READ 2
#define IDLE 3


/* Summary
   Initial value of early outputs from the state machine.
 */
#define ALPHA_START 0x13


/* Summary
   Transition function values used in the state machine.
 */
uint16_t CyFxGpifTransition[]  = {
    0x0000, 0xFFFF
};

/* Summary
   Table containing the transition information for various states. 
   This table has to be stored in the WAVEFORM Registers.
   This array consists of non-replicated waveform descriptors and acts as a 
   waveform table. 
 */
CyU3PGpifWaveData CyFxGpifWavedata[]  = {
    {{0x1E739C01,0x04000000,0x86000800},{0x00000000,0x00000000,0x00000000}},
    {{0x1E739C03,0x00000500,0x80400000},{0x00000000,0x00000000,0x00000000}},
    {{0x1E739C02,0x20000000,0xC7800800},{0x00000000,0x00000000,0x00000000}}
};

/* Summary
   Table that maps state indices to the descriptor table indices.
 */
uint8_t CyFxGpifWavedataPosition[]  = {
    0,1,1,2
};

/* Summary
   GPIF II configuration register values.
 */
uint32_t CyFxGpifRegValue[]  = {
    0x800083B0,  /*  CY_U3P_PIB_GPIF_CONFIG */
    0x00000003,  /*  CY_U3P_PIB_GPIF_BUS_CONFIG */
    0x00000000,  /*  CY_U3P_PIB_GPIF_BUS_CONFIG2 */
    0x00000052,  /*  CY_U3P_PIB_GPIF_AD_CONFIG */
    0x00000000,  /*  CY_U3P_PIB_GPIF_STATUS */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INTR */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INTR_MASK */
    0x00000082,  /*  CY_U3P_PIB_GPIF_SERIAL_IN_CONFIG */
    0x00000782,  /*  CY_U3P_PIB_GPIF_SERIAL_OUT_CONFIG */
    0x00000001,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_DIRECTION */
    0x0000FFFF,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_DEFAULT */
    0x00000001,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_POLARITY */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_TOGGLE */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_BUS_SELECT */
    0x00000006,  /*  CY_U3P_PIB_GPIF_CTRL_COUNT_CONFIG */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_COUNT_RESET */
    0x0000FFFF,  /*  CY_U3P_PIB_GPIF_CTRL_COUNT_LIMIT */
    0x0000010A,  /*  CY_U3P_PIB_GPIF_ADDR_COUNT_CONFIG */
    0x00000000,  /*  CY_U3P_PIB_GPIF_ADDR_COUNT_RESET */
    0x0000FFFF,  /*  CY_U3P_PIB_GPIF_ADDR_COUNT_LIMIT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_STATE_COUNT_CONFIG */
    0x0000FFFF,  /*  CY_U3P_PIB_GPIF_STATE_COUNT_LIMIT */
    0x0000010A,  /*  CY_U3P_PIB_GPIF_DATA_COUNT_CONFIG */
    0x00000000,  /*  CY_U3P_PIB_GPIF_DATA_COUNT_RESET */
    0x0000FFFF,  /*  CY_U3P_PIB_GPIF_DATA_COUNT_LIMIT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_COMP_VALUE */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CTRL_COMP_MASK */
    0x00000000,  /*  CY_U3P_PIB_GPIF_DATA_COMP_VALUE */
    0x00000000,  /*  CY_U3P_PIB_GPIF_DATA_COMP_MASK */
    0x00000000,  /*  CY_U3P_PIB_GPIF_ADDR_COMP_VALUE */
    0x00000000,  /*  CY_U3P_PIB_GPIF_ADDR_COMP_MASK */
    0x00000000,  /*  CY_U3P_PIB_GPIF_DATA_CTRL */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INGRESS_DATA */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INGRESS_DATA */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INGRESS_DATA */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INGRESS_DATA */
    0x00000000,  /*  CY_U3P_PIB_GPIF_EGRESS_DATA */
    0x00000000,  /*  CY_U3P_PIB_GPIF_EGRESS_DATA */
    0x00000000,  /*  CY_U3P_PIB_GPIF_EGRESS_DATA */
    0x00000000,  /*  CY_U3P_PIB_GPIF_EGRESS_DATA */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INGRESS_ADDRESS */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INGRESS_ADDRESS */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INGRESS_ADDRESS */
    0x00000000,  /*  CY_U3P_PIB_GPIF_INGRESS_ADDRESS */
    0x00000000,  /*  CY_U3P_PIB_GPIF_EGRESS_ADDRESS */
    0x00000000,  /*  CY_U3P_PIB_GPIF_EGRESS_ADDRESS */
    0x00000000,  /*  CY_U3P_PIB_GPIF_EGRESS_ADDRESS */
    0x00000000,  /*  CY_U3P_PIB_GPIF_EGRESS_ADDRESS */
    0x80010400,  /*  CY_U3P_PIB_GPIF_THREAD_CONFIG */
    0x80010401,  /*  CY_U3P_PIB_GPIF_THREAD_CONFIG */
    0x80010402,  /*  CY_U3P_PIB_GPIF_THREAD_CONFIG */
    0x80010403,  /*  CY_U3P_PIB_GPIF_THREAD_CONFIG */
    0x00000000,  /*  CY_U3P_PIB_GPIF_LAMBDA_STAT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_ALPHA_STAT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_BETA_STAT */
    0x00130000,  /*  CY_U3P_PIB_GPIF_WAVEFORM_CTRL_STAT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_WAVEFORM_SWITCH */
    0x00000000,  /*  CY_U3P_PIB_GPIF_WAVEFORM_SWITCH_TIMEOUT */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CRC_CONFIG */
    0x00000000,  /*  CY_U3P_PIB_GPIF_CRC_DATA */
    0xFFFFFFC1  /*  CY_U3P_PIB_GPIF_BETA_DEASSERT */
};

/* Summary
   This structure holds all the configuration inputs for the GPIF II. 
 */
const CyU3PGpifConfig_t CyFxGpifConfig  = {
    (uint16_t)(sizeof(CyFxGpifWavedataPosition)/sizeof(uint8_t)),
    CyFxGpifWavedata,
    CyFxGpifWavedataPosition,
    (uint16_t)(sizeof(CyFxGpifTransition)/sizeof(uint16_t)),
    CyFxGpifTransition,
    (uint16_t)(sizeof(CyFxGpifRegValue)/sizeof(uint32_t)),
    CyFxGpifRegValue
};

#endif   /* _INCLUDED__ */

Hello, world!

I am seeing inconsistent behavior between two identical statements while debugging an application using PSoC Creator 4.4 on the M4 (Pioneer kit CYC6347BZI-BLD53).  In a nutshell, when I set a breakpoint and inspect a variable in the debugger after a mathematical operation, I do not see the correct result.  

int adxl_read_reg_multiple(adxl_spi_handle *spi, unsigned char reg,
                                  unsigned short count, unsigned char *val)
{
    reg = (reg << 1) | ADXL_SPI_RNW;  // ADXL_SPI_RNW = 1

    unsigned char r1 = 0;   
    r1 = (r1 << 1) | ADXL_SPI_RNW;
    
    return spi_write_then_read(spi, &reg, 1, val, count);
}

This function is called with the reg argument = 0.  Setting a breakpoint at the first statement, the debugger shows reg = 0 (as expected). Step over the statement, and the debugger still shows reg = 0  -- when the new value clearly should be 1!  Step over the same statement for r1, and the debugger shows r1 = 1 -- but reg = 0 for the same operation.  They should both be 1.

Somewhere in the chain between the compiler, M4, and debugger something is not right. I looked in startup_psoc6_01_cm4.S and the default stack size is 4K., so I don't think I'm running out of stack for a shallow call chain.

This call sequence is taken from the ADXL372 code from Analog Devices. The wrong register value ends up being sent to the chip as a result of this problem (a 0 instead of a 1). If I can figure out what's happening in this test case, hopefully the driver will work. I've removed the actual peripheral code, which isn't necessary to reproduce the issue. 

If anyone has any idea what's going on, I'd like to hear it. 

Respectfully,
Peter

Where can I find the CAD files for KIT_1EDB_AUX_SIC and KIT_1EDB_AUX_GAN. Gerbers will do, source files would be great (Altium, Eagle, etc package). Thanks!

https://www.infineon.com/cms/en/product/evaluation-boards/kit_1edb_aux_sic/

https://www.infineon.com/cms/en/product/evaluation-boards/kit_1edb_aux_gan/