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

Hi all, 

I was trying design system with PSoC6 in Deep Sleep. Used CY8C6347 chip.
Timing diagram as per picture below. Used Wake-up from Deep Sleep from External pin as well as from MCWDT.

After some tests FW Developer came up with issue that entering Deep Sleep is not happening at constant time. "Sometimes it takes up to 500ms". So this is not possible to implement.
Can someone check if entering to Deep Sleep is constant time and if not what is max time to enter?

Hello, I have a straight question.

Should HCI UART CTS be connected with an external pulldown resistor when HCI UART is unused or can it be left floating?

I'm asking this because I have a strange interaction with HCI and PUART in my application related to HCI UART CTS state: if HCI UART CTS is pulled high then PUART does not receive data or receives corrupted data, while if HCI UART CTS is low then everything works as expected.

PUART port is configured with

// Avoid conflict between PUART_RX and CLK_REQ bonding
#define cr_pad_fcn_ctl_adr4 0x003201b8
#define REG32(x) (*(volatile unsigned*)(x))
unsigned val = REG32(cr_pad_fcn_ctl_adr4) & ~(0x0000F000);
REG32(cr_pad_fcn_ctl_adr4) = val | (7 << 12);

...

wiced_hal_puart_init();

wiced_hal_puart_select_uart_pads(WICED_P04, WICED_P31, 0, 0);

...

After reading some thread on PUART I also tried moving the following code from ISR to a periodic timer but with no effect.

while (wiced_hal_puart_rx_fifo_not_empty())
{
 if (wiced_hal_puart_read(&byte))
 {
  cbuf_put((void *)p_priv->p_init->p_rx, byte);  // This puts data in a local buffer read by application
 }
}

Since it seems to depend on HCI then I also tried with both

wiced_set_debug_uart(WICED_ROUTE_DEBUG_NONE)

and

wiced_set_debug_uart(WICED_ROUTE_DEBUG_TO_HCI_UART)

to disable HCI but none of the seems to work and the behavior is the same.

I'm struggling with this strange problem and we have 1000 pcs in production that need to use the PUART port.

BR

I am working on a project and trying to interface the CY8CPROTO-063-BLE board with an external I2C CapSense buttons and slider. Should I use the built in CapSense module, or just I2C? Attached below is the module I am attempting to interface with. 

https://www.mikroe.com/capsense-click

Hello everybody,

I have some problems to communicate with a 2D hall sensor from Infineon via I2C.

First some background information:

CY8CKIT-42 PSoC 4 Pioneer Kit

PSoC Creator 4.4

TLE493D-A2B6 (https://www.infineon.com/dgdl/Infineon-TLE493D-W2B6-UM-v01_01-UserManual-v01_11-EN.pdf?fileId=5546d46261ff5777016229accba436e2)

I wrote myself two functions which allow me to read or write a register.

The TLE493D has a 2-byte read command and a 1-byte read command. So I try to write the register first and change it to 1-byte read command mode.

When I try to write a register, it works, but when I try to read a register, I always get a NACK after I send the register address of the sensor. I don't know what the problem is.

I tried the read function with a MPU6050 sensor and it worked. I could read the register.

Why can't I read the registers properly?

I have added some pics and the project in the attachment.

Best Regards and Thank You

Michael

Hello.

Is there any sample code or application note that realizes Secure Boot and DFU at the same time?

I would like to know how to realize two functions at the same time, not individually.

Best Regards.

Yutaka Matsubara

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 have a workspace that has 2 "Design projects" and one "Library project".

The "Library project" is that one that contains the shared code. And from I'd like to call `CySysTickStart()` from it.

That functioned is declared in "CyLib.h", but I cannot include it from my "Library Project".

Question: How do I include CyLib.h (or for the matter, any other Cy* file  / cmsys* file) from a Library Project?

(Note: Those files seems that they get auto-generated by the "Design Project").

Hello

currently high school student in Terminal STI2D in france, i need in the frame of my classes, control a servo motor with a PSoC Card. Despite a many research in web, I can't find any information.

could you help me. Please.

Cordially

Gabin BROCHARD

According to the documentation ("Designing with the EZ-USB FX3 Slave FIFO Interface"), the propagation delay for the (watermark/ready) flags from the rising edge of the clock is max. 8 ns (tcflg) without specifying a minimum. So one has to assume it can be anywhere between 0 and 8 ns, right? But if correct that would mean that with a 100MHz GPIF-clock which has a period of 10 ns, one only has a 2 ns window to correctly sample the flag values. When eg. interfacing with a FPGA this means it's a "challenge" or it least not very easy to get the timing constraints right to make this reliably work.

Am I correct? And if so: what are the recommendations to do this the proper way?