Hi, 

When I see the datasheet of PSoC. normally. it shows that UDB is 4 or 8.  what is this UDB4 means? and how we define capability of UDB for usage? 

Sang-Min. 

Hello guys!

I have the board CYW954907AEVAL1F and I had an electrical accident the last week. It seems that all was OK but the USB IC (FT2232H) was not. My PC didn't recognize the usual COM port and I was unable to use it for download or debug via WICED STUDIO. After several tests, I realised that the EEPROM associated to FT2232H was broken.

I have replaced it with a new one and the same part  number and now the board is recognized on PC, but there are now two COM PORTS and I can't use WICED Studio to download nor Debug any program.

I have downloaded the FT Prog software from FTDI and, after studying this chip, it could be used as JTAG bridge, but after some test, I can't use the board with Wiced Studio for debugging.

Please, could any one tell me how I can reprogram the FT2232H chip implemented on CYW954907AEVAL1F to use with WICED Studio?

Many thanks in advance!

BR, 

Luis Lopez

Hello  

I'm going through the "README.md" on the GitHub repo and I'm confused on what to enter for the #define for the "MQTT CLIENT CERTIFICATION MACROS" in mqtt_client_config.h?

I have generated the certification files. but not sure what "..........base64 data..........\n"  is?

Are these required?

Any help would be appreciated

Regards

Steve K

To whom it may concerned ,

a CCG2 is emplyed on our USB4 Gen3 cable product which undergoes the compliance test w/ 3 items failed — 

1)Ra is out of 800 Ohm ~ 1.2K Ohm ( 3 pcs  tested and 1/3 ok w/ Vconn @423 mV ,and 2 out of 3 NG w/ Vconn = 402 mV )

2) PD3 modes - checking SVIDs ( The UUT shall return a number of SVIDs in between 1 and 1, actual 2 (TEST.PD.VDM.CBL.1#3)

3)Checking Headers (Message ID 0): Manufacturer String shall be null terminated (COMMON.CHECK.PD.10#1 x 1)

Kindly advise the countermeasure of the above 3 issues.

f.y.i. 1）NG test report 2）SVID on VIF 3）SVIDs setting on CCG2 are on the attached photos。

Thank you and best Regards,

Alan Huang 

Hi,

I'm using PSoC 4 board, I'm also using the WDT0 and WDT1 as the system timers as they work in the sleep mode, So I had to use the WDT2 as the system watchdog timer.

The WDT2 generates an interrupt when it fires, So I reset the system in the interrupt.

So, I disable the WDT2 when I'm going to sleep mode, and re-enable it after I wake up.

I found that the system sometimes could not enable the WDT2 and stuck in this excessive loop.

        if(0u != (counterMask & CY_SYS_WDT_COUNTER2_MASK))
        {
            while (0u == CySysWdtGetEnabledStatus(CY_SYS_WDT_COUNTER2))
            {
                /* Wait for changes to come into effect */
            }
        }

I also found this comment

" * Enabling or disabling WDT requires 3 LFCLK cycles to come into effect.
* Therefore, the WDT enable state must not be changed more than once in
* that period."

So, I controlled the calls of CySysWdtEnable and CySysWdtDisable, and I made sure that they were not called within 3 LFCLK clocks, But this also did not solve the issue.

I also use a GPIO pin to measure the time between calling these functions(CySysWdtEnable, CySysWdtDisable), I found the minimum time is taken was 180us and the LFClK frequency was 32,768 kHz, So the 3 clocks should be 91.55us, So 180us should not makes any troubles.

So, If there are any solutions or guides to solve/avoid this issue will be very helpful.

Best Regards,

Khalil Azouz

Hi!

My plan is to implement the following startup sequence from cold reset:

1. CM0p executes and starts CM4 (basically default functionality)
2. Bootloader application 0 starts. This has the responsibility to select which of applications 1 or 2 to execute

Is there a way, using the DFU SDK, to persistently mark an application as next/current, Linux style? With factory defaults it would contain app 0 and at least one of app 1 and 2. Powering it up the first time in post production it would boot either app 1 or 2. At a later point in time this app installs another app in the free slot. A switch is performed to the new app. How can I persist this value so that the new application is executed on subsequent cold resets?

Thanks!
Markus

Dear Sir,

I got a Wifi test running on the development board CY8CPROTO-062-4343W. It runs ok and can connect and send/receive data. The code was originally exported from the ModusToolbox.
Currently a board is available with the same WiFi chip LBEE5KL1DX and a STM32F427 processor.
What is the easiest way to port the cypress library to a STM32F427 ?

Kind Regards.

Hi. Over the past couple days I’ve been suffering from an issue where my PSOC creator crashes within seconds of typing code.

Upon further investigation, windows event viewer said it was Libclang.dll and the internet said that I could disable semantic parsing to stop the crashing.

that worked except now I might as well be using notepad to code. This is a recent issue. Is there any way to fix this?

Hi,

I am using modustoolbox with PSoC6. I am using the latest pdl libraries. I am not getting any warning or error when I am compiling code, but there is some message in IDE showing "ambiguous". Please have a look at the screenshot attached. 

Below is the message:

Could you suggest to me what is the problem?

Thanks

Hi.

I am new with Psoc products and I create a simple project that read voltage from a pin (P0.5) with 10 bit ADC. The micro is CY8C4045LQI-S412.

main.c

int main(void)
{
CyGlobalIntEnable; /* Enable global interrupts. */
ADC_1_Start();
while(ADC_1_IsBusy()!=ADC_1_STATUS_IDLE);
ADC_1_ISR_Start();
ADC_1_StartConvert(0);

/* Place your initialization/startup code here (e.g. MyInst_Start()) */

for(;;)
{
/* Place your application code here. */
}
}

ADC_1_ISR.c

CY_ISR(ADC_1_ISR_Interrupt)
{ uint16 voltage;
#ifdef ADC_1_ISR_INTERRUPT_INTERRUPT_CALLBACK
ADC_1_ISR_Interrupt_InterruptCallback();
#endif /* ADC_1_ISR_INTERRUPT_INTERRUPT_CALLBACK */

/* Place your Interrupt code here. */
/* `#START ADC_1_ISR_Interrupt` */
while(ADC_1_IsBusy()!=ADC_1_STATUS_IDLE);
voltage=ADC_1_GetResult_mVolts(0);
ADC_1_ISR_ClearPending();
/* `#END` */
}

The ADC status remain in "converting" (0x40) in the while loop. And also... without while loop check, after clearpending the interrupt routine is invoked continuously.

Whitout interrupt, if I use ADC_1_ReadResult_mVolts or ADC_1_StartConvert + ADC_1_IsBusy + ADC_1_GetResult_mVolts, the voltage is read correctly.

What is the problem in the code above?

Thanks a lot.

Best regards